From: "James Mclaren" <james@q-games.com>
To: <gdb@sources.redhat.com>
Subject: gdb5.x under cygwin, problems
Date: Mon, 17 Jun 2002 18:14:00 -0000 [thread overview]
Message-ID: <002701c21665$f1264400$5a01a8c0@james2k> (raw)
Hi,
We're having problems getting gdb 5.2 (or 5.1 for that matter) to work
correctly under cygwin. We're using gcc 3.1, and have been unable to get
anywhere using the -g option. The debugger will just crash instantly. We've
recently tried using the -gstabs option instead, which seems to get us a
little bit further, but the gdb seems to fall over when calling fns inside a
dll. We get the following error using a version of NVidia's nvparse.dll:
Program received signal SIGSEGV, Segmentation fault.
0x77e5404b in nvparse_dll_iname ()
This error doesn't occur when we run our project from the command line.
Only from within gdb. Does anyone have any suggestions as to how we can get
gdb working properly with gcc 3.1 under cygwin, as we've been without
debugging for a couple of months now, and its starting to get frustrating.
Any help much appreciated.
James Mclaren.
reply other threads:[~2002-06-18 1:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='002701c21665$f1264400$5a01a8c0@james2k' \
--to=james@q-games.com \
--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