Re: Debugging (VS2005) an app with threads above default priority
- From: "Paul G. Tobey [eMVP]" <p space tobey no spam AT no instrument no spam DOT com>
- Date: Wed, 30 Jan 2008 10:58:02 -0700
VS2005 only uses CoreConn, so that shouldn't be a problem. Platman, if
that's what you're thinking of, was even easier to use over Ethernet only,
but that would only impact pre-VS2005 things.
Paul T.
"Tony Hedge" <tonyatbenthicsciencesdotcodotuk> wrote in message
news:%23POaSj2YIHA.4272@xxxxxxxxxxxxxxxxxxxxxxx
Paul
Thanks for the response. Glad to hear it probably isn't just me. The
threads all *ought* to spend most of their time blocked - the ones which
wait on a CommEvent though, I guess I'm relying on the guys who wrote the
device driver to be really blocking rather than spinning somewhere inside
a driver thread. And I'm old enough that I should know better than to rely
on a third-party driver to handle comms properly!
And thanks for the suggestions re ditching ActiveSync - I'll have a look
at the archives as you suggest. I did try going through ethernet only, but
though I could get the CoreConn stuff working, I had trouble with some of
the old PlatCon tools. I think there are some vendor-implementation
connectivity issues with this target board, so I've tended to push the
problem back to them. I'll try it again with a bit more determination.
Thanks again for all your help, much appreciated.
Tony
Paul G. Tobey [eMVP] wrote:
Yes, it's pretty tough to debug a multi-threaded program. There's
probably something about your high-priority threads that is worse than
average (maybe you never block in them or something), but I've been only
slightly successful trying to debug threads other than the main thread.
Your easiest option is to use debug messages or some other form of
logging to indicate what the thread is doing.
You could always drop ActiveSync as your debug transport, if you want to
take it out of the equation. There have previously been a number of
threads on debugging with VS2005 and without ActiveSync. Take a search
of the archives with GoogleGroups.
Paul T.
"Tony Hedge" <tonyatbenthicsciencesdotcodotuk> wrote in message
news:uYWzdR0YIHA.208@xxxxxxxxxxxxxxxxxxxxxxx
I'm trying to debug an app under VS2005 (native code, CE5.0).
As long as all my threads are at default priority (251), everything is
fine. But I have some CommEvent handling threads I would like to try to
run at a higher priority than the threads that "consume" the messages
they handle.
When I raise these to priority 248, debugging gets tricky. eg when I try
to "Stop Debugging" in VS, nothing much happens until the connection to
the device is lost, then its a matter of rebooting the device,
re-establishing connectivity etc.
Is this normal? I'm having lost of connectivity issues with ActiveSync
anyway, so I'm not sure if these are related.
Any thoughts much appreciated!
Tony
.
- Follow-Ups:
- Re: Debugging (VS2005) an app with threads above default priority
- From: Tony Hedge
- Re: Debugging (VS2005) an app with threads above default priority
- References:
- Debugging (VS2005) an app with threads above default priority
- From: Tony Hedge
- Re: Debugging (VS2005) an app with threads above default priority
- From: Paul G. Tobey [eMVP]
- Re: Debugging (VS2005) an app with threads above default priority
- From: Tony Hedge
- Debugging (VS2005) an app with threads above default priority
- Prev by Date: Re: Debugging (VS2005) an app with threads above default priority
- Next by Date: Re: "No .rel file found for module "
- Previous by thread: Re: Debugging (VS2005) an app with threads above default priority
- Next by thread: Re: Debugging (VS2005) an app with threads above default priority
- Index(es):
Relevant Pages
|