This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Trace crash in gargabe collector to the code at fault?

From: Tom Tromey <tromey at redhat dot com>
To: Andrew Haley <aph at redhat dot com>
Cc: okellogg at freenet dot de, gcc at gcc dot gnu dot org
Date: Fri, 14 Aug 2009 11:40:33 -0600
Subject: Re: Trace crash in gargabe collector to the code at fault?
References: <400e1c6303a9c2d634341fa3e69ce5ae@email.freenet.de> <4A85312D.1070609@redhat.com>
Reply-to: tromey at redhat dot com

>>>>> "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

References:
- Trace crash in gargabe collector to the code at fault?
  - From: okellogg
- Re: Trace crash in gargabe collector to the code at fault?
  - From: Andrew Haley

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]