From: Tom Tromey <tromey@redhat.com>
To: Andrew Haley <aph@redhat.com>
Cc: okellogg@freenet.de, gcc@gcc.gnu.org
Subject: Re: Trace crash in gargabe collector to the code at fault?
Date: Fri, 14 Aug 2009 19:28:00 -0000 [thread overview]
Message-ID: <m3iqgqjnu6.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4A85312D.1070609@redhat.com> (Andrew Haley's message of "Fri\, 14 Aug 2009 10\:41\:01 +0100")
>>>>> "Andrew" == Andrew Haley <aph@redhat.com> writes:
>> I am running into crashes in ggc_collect() on compiling
Andrew> The usual way to find this is to use a gdb watchpoint. Find
Andrew> what object is being freed, put a breakpoing on ggc_alloc_stat
Andrew> at the point the object is created, and then put a watchpoint on
Andrew> the word that is being corrupted.
I've also had decent results by configuring with valgrind support.
Tom
next prev parent reply other threads:[~2009-08-14 17:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-14 13:12 okellogg
2009-08-14 14:05 ` Andrew Haley
2009-08-14 19:28 ` Tom Tromey [this message]
2009-08-15 23:25 ` Oliver Kellogg
2009-08-16 10:51 ` Andrew Haley
2009-08-28 18:04 ` Oliver Kellogg
2009-08-28 21:12 ` Ian Lance Taylor
2009-08-31 4:57 ` Oliver Kellogg
2009-08-31 14:41 ` Tom Tromey
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=m3iqgqjnu6.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=aph@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=okellogg@freenet.de \
/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).