This is the mail archive of the pthreads-win32@sources.redhat.com mailing list for the pthreas-win32 project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

RE: problems debugging


Since you are using msvc 6.0, put a breakpoint in your
mainline, run to that point and then pull down the
Debug menu. Select "Exceptions..." Scroll the
exceptions listed all the way down until you see
"C++ exceptions"

Click the "Stop always" radial button.

That will cause the debugger to halt on all thrown
C++ exceptions.  You can do the same with SEH exceptions
(as you will see in that window.)

You will also notice that from the "Debug" menu you
can select "Threads". This will allow you to change
the focus of your debugging session to another thread.

Hope this helps.

-----Original Message-----
From: Ed Barker [mailto:barkeref@sigcomp.com]
Sent: December 21, 2000 3:25 PM
To: pthreads-win32@sourceware.cygnus.com
Subject: problems debugging


Hello all -

I have been using pthreads_win32 for about 2 years now - with great
success.  I am using MSVC version 6.0, and my version of pthreads_win32 was
downloaded as a pre-built DLL.

However, I have always had a problem debugging.  If my program crashes (due
to my own errors) while executing code running in pthread, the IDE output
window procuces a message similar to:

First-chance exception in NHServer.exe: 0xC0000005: Access Violation.
The thread 0x131 has exited with code -1 (0xFFFFFFFF).

Normally, the debugger will stop execution of the program, and show me the
exact line in my code that caused the access violation.  This feature saves
lots of time debugging, and I really miss it when I am using pthreads.

I did read a post on the mailing list that talked about some problems in
this area, but the post seemed to indicate that this issue had been
resolved in the latest version.  I downloaded the newest version (Sep 08)
but I am still getting the same results.  I tried both the C exception and
Structure exception libraries.

Thanks in advance for any insight.

Ed


Ed Barker
Signet Computers Inc.
1901 N Moore St.  Suite 805
Arlington, Va 22209
703-812-8585 (phone)
www.sigcomp.com
barkeref@sigcomp.com

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]