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

2009-08-30 Thread Tom Tromey
> "Oliver" == Oliver Kellogg writes: Oliver> As mentioned, I'm still struggling with leftovers being carried Oliver> over from compilation 1 to N-1 into compilation N of a compile Oliver> job. gcc_free'ing things (in combination with "configure Oliver> --enable-checking=gc,gcac") helps me tr

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

2009-08-30 Thread Oliver Kellogg
On Fri, 2009-08-28 at 06:58 -0700, Ian Lance Taylor wrote: > oliver.kell...@t-online.de (Oliver Kellogg) writes: > > > In multi source compile mode, I ggc_free() the data in dwarf2out.c after > > code generation for a file is done. (I found that I need this because > > otherwise the assembly code

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

2009-08-28 Thread Ian Lance Taylor
oliver.kell...@t-online.de (Oliver Kellogg) writes: > In multi source compile mode, I ggc_free() the data in dwarf2out.c after > code generation for a file is done. (I found that I need this because > otherwise the assembly code generated for file_2 to file_N of a compile > job will carry leftover

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

2009-08-27 Thread Oliver Kellogg
It turned out to be the following: In multi source compile mode, I ggc_free() the data in dwarf2out.c after code generation for a file is done. (I found that I need this because otherwise the assembly code generated for file_2 to file_N of a compile job will carry leftovers from the code generated

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

2009-08-15 Thread Andrew Haley
Oliver Kellogg wrote: > On Fri, 2009-08-14 at 10:41 +0100, Andrew Haley wrote: >>> I am stuck here, i.e. I don't know how to find the code >>> that is >>> at fault. >>> Is there some way to trace a pointer entered in >>> G.free_object_list >>> back to its origin in the code? >> The usual way to fin

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

2009-08-15 Thread Oliver Kellogg
On Fri, 2009-08-14 at 10:41 +0100, Andrew Haley wrote: > > > > I am stuck here, i.e. I don't know how to find the code > > that is > > at fault. > > Is there some way to trace a pointer entered in > > G.free_object_list > > back to its origin in the code? > > The usual way to find this is to use a

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

2009-08-14 Thread Tom Tromey
> "Andrew" == Andrew Haley 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

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

2009-08-14 Thread Andrew Haley
okell...@freenet.de wrote: > Working on the GNAT multi-source compile feature > > (see http://gcc.gnu.org/ml/gcc/2009-04/msg00380.html), > > I am running into crashes in ggc_collect() on compiling > > the 2nd file in the compile job. > > > > Following the advice given in > http://gcc.gnu.org/

Trace crash in gargabe collector to the code at fault?

2009-08-14 Thread okellogg
Working on the GNAT multi-source compile feature (see http://gcc.gnu.org/ml/gcc/2009-04/msg00380.html), I am running into crashes in ggc_collect() on compiling the 2nd file in the compile job. Following the advice given in http://gcc.gnu.org/ml/gcc/2004-04/msg00901.html , I configured GCC wit