From: Brendon Costa <bcosta@avdat.com.au>
To: gcc-help@gcc.gnu.org
Subject: Debugging GCC
Date: Tue, 30 Aug 2005 05:00:00 -0000 [thread overview]
Message-ID: <4313E7F6.9010003@avdat.com.au> (raw)
Hi all,
I have been working on a small extension to the C++ front end of GCC
that helps me to document exceptions while compiling code. Anyway my
extension requires me to modify GCC and so I am modifying version 4.0.1.
Through developing this I have come across a single frustration that has
slowed my development down a lot. Basically GCC seems to catch any
SIGSEGV generated and then spit out an Internal Compiler Error. This is
ok, I am still trying to debug some of my code that is producing the
exception, but the problem is that I want to run g++ inside a debugg
(gdb) in order to find out where the SIGSEV is being generated.
Currently I have a lot of very extensive logging procedures that try to
narrow down the problem, but it is still tedious.
Does anyone know a way of invoking g++ inside gdb or compiling g++ so
that g++ will not handle the SIGSEGV signal but would crash instead so
GDB can give me a stack trace of the place where the segmentation fault
occurred?
Thanks,
Brendon.
next reply other threads:[~2005-08-30 5:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-30 5:00 Brendon Costa [this message]
2005-08-30 8:31 ` Andrey Belevantsev
-- strict thread matches above, loose matches on Subject: below --
2004-03-11 11:29 Debugging Gcc Hari
2004-03-12 2:56 ` Ian Lance Taylor
2001-12-20 10:54 debugging gcc ratnadeep joshi
2001-12-21 14:27 ` Andrea 'Fyre Wyzard' Bocci
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=4313E7F6.9010003@avdat.com.au \
--to=bcosta@avdat.com.au \
--cc=gcc-help@gcc.gnu.org \
/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).