Hi guys,

We develop a x86 device that runs Windows CE 6.

A couple weeks ago we started to use AppVerif on many of our applications.
We found a lot of handle not closed and some heap leak.

Now we suspect that some of our services are causing a memory leak. We would
like to use the same application to see where those leaks are. The problem is
that we can;t find a way to stop serviced.exe. How can we stop it?

Does stopping all services will stop serviced.exe?

I would also like to know if someone noticed that all the C Runtime
functions are not monitored by AppVerif? A call to fopen without a fclose
will not be visible in the appverif log. How can I verify these functions for
leaks?

Thanks.

Re: Question about AppVerif by Silver

Silver
Wed Mar 19 14:17:18 PDT 2008

Why do you want to stop services.exe? start then Stop and unload all of the
services you are interested in then examine the logs.

See this article:
http://msdn2.microsoft.com/en-us/library/bb154415.aspx

You do not need to stop services.exe


Geoff
--


Re: Question about AppVerif by Vinz

Vinz
Thu Mar 20 05:12:00 PDT 2008

The reason we want to stop serviced.exe is beacause some services (like
httpd) loads dlls and do not unload them immmediatly. Even if you unload the
service the dlls stays loaded in serviced.exe.

We already have seen some interesting things by unloading the service
individually. We expect to find other things by stoping services.

Re: Question about AppVerif by Silver

Silver
Thu Mar 20 09:16:57 PDT 2008

Tell services.exe to unload the service use "DeregisterService".

Geoff
--

Re: Question about AppVerif by Arnie

Arnie
Tue Mar 25 09:25:36 PDT 2008

Optionally I thought there was a command in the shell.exe to start/stop
specific services running under services.exe.

Type "shell -c" then "?" to get a list of supported commands.

-jeff

"Silver" <moc.liamtoh@gnirrevliseht> wrote in message
news:%23XDYZXqiIHA.2084@TK2MSFTNGP02.phx.gbl...
> Tell services.exe to unload the service use "DeregisterService".
>
> Geoff
> --