This is the mail archive of the gcc-bugs@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]

[Bug middle-end/17044] [3.5 Regression] libgcc2.c:169: internal compiler error: Segmentation fault


------- Additional Comments From law at redhat dot com  2004-08-24 19:48 -------
Subject: Re:  [3.5 Regression] libgcc2.c:169:
	internal compiler error: Segmentation fault

On Tue, 2004-08-17 at 11:38, dave at hiauly1 dot hia dot nrc dot ca
wrote:
> ------- Additional Comments From dave at hiauly1 dot hia dot nrc dot ca  2004-08-17 17:38 -------
> Subject: Re:  [3.5 Regression] libgcc2.c:169: internal c
> 
> > John -- if this is a problem building libgcc2.i with the stage1
> > compiler, can you send me a backtrace at the failure point (again,
> > I'm without access to my HPs for at least a week).
> 
> The exception occurs in the following call to free:
> 
> Breakpoint 13, 0x400000000031e350 in thread_block (bb=0x800003fffeacd8c0)
>     at ../../gcc/gcc/tree-ssa-threadupdate.c:381
> 381           free (rd);
> (gdb) bt
> #0  0x400000000031e350 in thread_block (bb=0x800003fffeacd8c0)
>     at ../../gcc/gcc/tree-ssa-threadupdate.c:381
OK.  That means there's got to be a memory management error of some
kind.  I wonder if we're freeing GC'd memory or something stupid like
that.



Jeff



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17044


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