From: Brian Dessent <brian@dessent.net>
To: gdb@sources.redhat.com
Subject: Re: gdb on cygwin and debugging assert() or program segmentation faults
Date: Wed, 20 Jul 2005 02:09:00 -0000 [thread overview]
Message-ID: <42DDB33D.434A6CB2@dessent.net> (raw)
In-Reply-To: <loom.20050720T002246-371@post.gmane.org>
Kris Thielemans wrote:
> I need to debug a C++ program that throws up an assert(). On Linux, I'm used to
> be able to run the program in gdb, and when the assert happens, the program
> stops (in the assert function) and I can do a back trace (e.g. info stack).
> On cygwin on the other hand, I just get the assert message, and then gdb
> says "Program exited normally". No backtrace possible.
Set the error_start parameter of the CYGWIN variable to gdb and then run
the program, and you should gdb launched and attached to the process
when it encounters a SEGV or abort(). See the users manual section
about $CYGWIN.
Brian
next prev parent reply other threads:[~2005-07-20 2:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-19 22:40 Kris Thielemans
2005-07-20 2:09 ` Brian Dessent [this message]
2005-07-20 2:37 ` Christopher Faylor
2005-07-20 10:28 ` Dave Korn
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=42DDB33D.434A6CB2@dessent.net \
--to=brian@dessent.net \
--cc=gdb@sources.redhat.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