From: Ed Barker <barkeref@sigcomp.com>
To: pthreads-win32@sourceware.cygnus.com
Subject: problems debugging
Date: Thu, 21 Dec 2000 12:24:00 -0000 [thread overview]
Message-ID: <3.0.6.32.20001221152527.0098c7b0@mail.sigcomp.com> (raw)
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
next reply other threads:[~2000-12-21 12:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-21 12:24 Ed Barker [this message]
2000-12-21 13:03 Bossom, John
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3.0.6.32.20001221152527.0098c7b0@mail.sigcomp.com \
--to=barkeref@sigcomp.com \
--cc=pthreads-win32@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).