I don't have much experience with threads or debugging of those threads. I'm
using VS 2005 pro.
I'm getting a "TypeLoadException" error soon after I invoke a thread. It is
identifying a Enum member is a class for which there is a "reference to".
Anyway I am trying to step through the process to see the exact instruction
which is causing the process to fail, but for some reason I am not able to
step thru the lines of code which are associated with the invoked thread.
Is there something special I need to do to get the debugger to step me
through these lines of code? Does VS2005 automatically switch to this new
thread which I invoked or is there some process I need to ge through to get
the debugger linked to that thread? I looked in the "Attach Process", but I
don't see my new thread show up there.
Thanks in advance for your assistance!!!!
Thanks in advance for your assistance!!!
Peter Duniho - 21 Mar 2008 20:02 GMT
> [...] Does VS2005 automatically switch to this new
> thread which I invoked or is there some process I need to ge through to
> get
> the debugger linked to that thread? I looked in the "Attach Process",
> but I
> don't see my new thread show up there.
Try opening the "Threads" window, from the Debug/Windows... menu item.
Normally if you hit a breakpoint or exception the debugger would put you
in the correct thread. So either that's not how you're entering the
thread, or something odd is going on. But in the non-Express version of
VS you should be able to directly switch to a specific thread using the
Threads window (there's also a Threads toolbar control you can use).
Pete