I try to view the thread in a process for a Windows Mobile 2003 device, and
the utility cepview.exe from embedded virtual tool does not seem to work
with 2003. It gave me the following error when I try to connect:

"cannot file appropriate device side files associated with this tool"

Also I use BugTrap from Windows Mobile Power tool, and it shows a lot more
thread create message than thread exiting message, I was worried about
memeroy leak. I remember seeing that there is not a 1 to 1 relationship
between a read thead and a DOTNET managed thread. This is why I wanted to
view the number of thread in the process.

Please help, thanks!

I don't own a WM2003 device but using eVC and its Remote process viewer I
can see thread info for managed processes on our device; maybe you should
try that.

In CF 1.0 there is a 1-to-1 relationship between managed/native threads. If
you are using threads from the ThreadPool (e.g. via Threading.Timer), you
will not see them exit immediately. Also not that every CF 1.0 app has 3
threads on startup growing to 4 when the finalizer thread kicks in; you will
not see this exit during the app's lifetime.

Cheers
Daniel
--
http://www.danielmoth.com/Blog/


"Zen" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
>I try to view the thread in a process for a Windows Mobile 2003 device, and
> the utility cepview.exe from embedded virtual tool does not seem to work
> with 2003. It gave me the following error when I try to connect:
>
> "cannot file appropriate device side files associated with this tool"
>
> Also I use BugTrap from Windows Mobile Power tool, and it shows a lot more
> thread create message than thread exiting message, I was worried about
> memeroy leak. I remember seeing that there is not a 1 to 1 relationship
> between a read thead and a DOTNET managed thread. This is why I wanted to
> view the number of thread in the process.
>
> Please help, thanks!
>
>

....just noticed the subject of your post (cepview).. the "embedded virtual
tool" comment threw me...
In which case I have no alternatives to offer..maybe someone else will.

Cheers
Daniel
--
http://www.danielmoth.com/Blog/


"Daniel Moth" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
>I don't own a WM2003 device but using eVC and its Remote process viewer I
>can see thread info for managed processes on our device; maybe you should
>try that.
>
> In CF 1.0 there is a 1-to-1 relationship between managed/native threads.
> If you are using threads from the ThreadPool (e.g. via Threading.Timer),
> you will not see them exit immediately. Also not that every CF 1.0 app has
> 3 threads on startup growing to 4 when the finalizer thread kicks in; you
> will not see this exit during the app's lifetime.
>
> Cheers
> Daniel
> --
> http://www.danielmoth.com/Blog/
>
>
> "Zen" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
>>I try to view the thread in a process for a Windows Mobile 2003 device,
>>and
>> the utility cepview.exe from embedded virtual tool does not seem to work
>> with 2003. It gave me the following error when I try to connect:
>>
>> "cannot file appropriate device side files associated with this tool"
>>
>> Also I use BugTrap from Windows Mobile Power tool, and it shows a lot
>> more
>> thread create message than thread exiting message, I was worried about
>> memeroy leak. I remember seeing that there is not a 1 to 1 relationship
>> between a read thead and a DOTNET managed thread. This is why I wanted
>> to
>> view the number of thread in the process.
>>
>> Please help, thanks!
>>
>>
>
>

Daniel, I actually just discovered myself that if I install eVC4, the tools
works better with 2003, at least the process viewer works. but still not
all of them work though. Call profiler, remote performon, kernel tracker
still does not work.

I am seeing many thread hanging around even after the thread function has
exit.

Oh, just find that what I read about that there is not a 1 to 1 relationship
between real thread and managed thread is for regular framework. I think
you are right, as the managed thread goes up, I am seeing the real thread
goes up as well.


"Daniel Moth" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> ...just noticed the subject of your post (cepview).. the "embedded virtual
> tool" comment threw me...
> In which case I have no alternatives to offer..maybe someone else will.
>
> Cheers
> Daniel
> --
> http://www.danielmoth.com/Blog/
>
>
> "Daniel Moth" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
> >I don't own a WM2003 device but using eVC and its Remote process viewer I
> >can see thread info for managed processes on our device; maybe you should
> >try that.
> >
> > In CF 1.0 there is a 1-to-1 relationship between managed/native threads.
> > If you are using threads from the ThreadPool (e.g. via Threading.Timer),
> > you will not see them exit immediately. Also not that every CF 1.0 app
has
> > 3 threads on startup growing to 4 when the finalizer thread kicks in;
you
> > will not see this exit during the app's lifetime.
> >
> > Cheers
> > Daniel
> > --
> > http://www.danielmoth.com/Blog/
> >
> >
> > "Zen" <(E-Mail Removed)> wrote in message
> > news:%(E-Mail Removed)...
> >>I try to view the thread in a process for a Windows Mobile 2003 device,
> >>and
> >> the utility cepview.exe from embedded virtual tool does not seem to
work
> >> with 2003. It gave me the following error when I try to connect:
> >>
> >> "cannot file appropriate device side files associated with this tool"
> >>
> >> Also I use BugTrap from Windows Mobile Power tool, and it shows a lot
> >> more
> >> thread create message than thread exiting message, I was worried about
> >> memeroy leak. I remember seeing that there is not a 1 to 1
relationship
> >> between a read thead and a DOTNET managed thread. This is why I wanted
> >> to
> >> view the number of thread in the process.
> >>
> >> Please help, thanks!
> >>
> >>
> >
> >
>
>

The tools are tied to specific Windows CE versions - eMbedded Visual Tools
3.0 has tools which will work with Pocket PC 2000 / 2002. Since Pocket PC
2003 is based on CE.NET 4.2 you should use the tools shipped with eVC++ 4.0
Service Pack 2.

Peter

--
Peter Foot
Windows Embedded MVP
www.inthehand.com | www.opennetcf.org

"Zen" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Daniel, I actually just discovered myself that if I install eVC4, the
> tools
> works better with 2003, at least the process viewer works. but still not
> all of them work though. Call profiler, remote performon, kernel tracker
> still does not work.
>
> I am seeing many thread hanging around even after the thread function has
> exit.
>
> Oh, just find that what I read about that there is not a 1 to 1
> relationship
> between real thread and managed thread is for regular framework. I think
> you are right, as the managed thread goes up, I am seeing the real thread
> goes up as well.
>
>
> "Daniel Moth" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
>> ...just noticed the subject of your post (cepview).. the "embedded
>> virtual
>> tool" comment threw me...
>> In which case I have no alternatives to offer..maybe someone else will.
>>
>> Cheers
>> Daniel
>> --
>> http://www.danielmoth.com/Blog/
>>
>>
>> "Daniel Moth" <(E-Mail Removed)> wrote in message
>> news:%(E-Mail Removed)...
>> >I don't own a WM2003 device but using eVC and its Remote process viewer
>> >I
>> >can see thread info for managed processes on our device; maybe you
>> >should
>> >try that.
>> >
>> > In CF 1.0 there is a 1-to-1 relationship between managed/native
>> > threads.
>> > If you are using threads from the ThreadPool (e.g. via
>> > Threading.Timer),
>> > you will not see them exit immediately. Also not that every CF 1.0 app
> has
>> > 3 threads on startup growing to 4 when the finalizer thread kicks in;
> you
>> > will not see this exit during the app's lifetime.
>> >
>> > Cheers
>> > Daniel
>> > --
>> > http://www.danielmoth.com/Blog/
>> >
>> >
>> > "Zen" <(E-Mail Removed)> wrote in message
>> > news:%(E-Mail Removed)...
>> >>I try to view the thread in a process for a Windows Mobile 2003 device,
>> >>and
>> >> the utility cepview.exe from embedded virtual tool does not seem to
> work
>> >> with 2003. It gave me the following error when I try to connect:
>> >>
>> >> "cannot file appropriate device side files associated with this tool"
>> >>
>> >> Also I use BugTrap from Windows Mobile Power tool, and it shows a lot
>> >> more
>> >> thread create message than thread exiting message, I was worried about
>> >> memeroy leak. I remember seeing that there is not a 1 to 1
> relationship
>> >> between a read thead and a DOTNET managed thread. This is why I
>> >> wanted
>> >> to
>> >> view the number of thread in the process.
>> >>
>> >> Please help, thanks!
>> >>
>> >>
>> >
>> >
>>
>>
>
>

Or SP3, which allows you to choose which tool set to use (4.0, 4.1 or 4.2)

--
<ctacke/>
www.OpenNETCF.org
Your CF searches start and end here


"Peter Foot [MVP]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> The tools are tied to specific Windows CE versions - eMbedded Visual Tools
> 3.0 has tools which will work with Pocket PC 2000 / 2002. Since Pocket PC
> 2003 is based on CE.NET 4.2 you should use the tools shipped with eVC++
> 4.0 Service Pack 2.
>
> Peter
>
> --
> Peter Foot
> Windows Embedded MVP
> www.inthehand.com | www.opennetcf.org
>
> "Zen" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
>> Daniel, I actually just discovered myself that if I install eVC4, the
>> tools
>> works better with 2003, at least the process viewer works. but still not
>> all of them work though. Call profiler, remote performon, kernel tracker
>> still does not work.
>>
>> I am seeing many thread hanging around even after the thread function has
>> exit.
>>
>> Oh, just find that what I read about that there is not a 1 to 1
>> relationship
>> between real thread and managed thread is for regular framework. I think
>> you are right, as the managed thread goes up, I am seeing the real thread
>> goes up as well.
>>
>>
>> "Daniel Moth" <(E-Mail Removed)> wrote in message
>> news:%(E-Mail Removed)...
>>> ...just noticed the subject of your post (cepview).. the "embedded
>>> virtual
>>> tool" comment threw me...
>>> In which case I have no alternatives to offer..maybe someone else will.
>>>
>>> Cheers
>>> Daniel
>>> --
>>> http://www.danielmoth.com/Blog/
>>>
>>>
>>> "Daniel Moth" <(E-Mail Removed)> wrote in message
>>> news:%(E-Mail Removed)...
>>> >I don't own a WM2003 device but using eVC and its Remote process viewer
>>> >I
>>> >can see thread info for managed processes on our device; maybe you
>>> >should
>>> >try that.
>>> >
>>> > In CF 1.0 there is a 1-to-1 relationship between managed/native
>>> > threads.
>>> > If you are using threads from the ThreadPool (e.g. via
>>> > Threading.Timer),
>>> > you will not see them exit immediately. Also not that every CF 1.0 app
>> has
>>> > 3 threads on startup growing to 4 when the finalizer thread kicks in;
>> you
>>> > will not see this exit during the app's lifetime.
>>> >
>>> > Cheers
>>> > Daniel
>>> > --
>>> > http://www.danielmoth.com/Blog/
>>> >
>>> >
>>> > "Zen" <(E-Mail Removed)> wrote in message
>>> > news:%(E-Mail Removed)...
>>> >>I try to view the thread in a process for a Windows Mobile 2003
>>> >>device,
>>> >>and
>>> >> the utility cepview.exe from embedded virtual tool does not seem to
>> work
>>> >> with 2003. It gave me the following error when I try to connect:
>>> >>
>>> >> "cannot file appropriate device side files associated with this tool"
>>> >>
>>> >> Also I use BugTrap from Windows Mobile Power tool, and it shows a lot
>>> >> more
>>> >> thread create message than thread exiting message, I was worried
>>> >> about
>>> >> memeroy leak. I remember seeing that there is not a 1 to 1
>> relationship
>>> >> between a read thead and a DOTNET managed thread. This is why I
>>> >> wanted
>>> >> to
>>> >> view the number of thread in the process.
>>> >>
>>> >> Please help, thanks!
>>> >>
>>> >>
>>> >
>>> >
>>>
>>>
>>
>>
>
>