This is the mail archive of the gcc-patches@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: GCC build failed for native with your patch on 2003-04-11T06:


"John David Anglin" <dave at hiauly1 dot hia dot nrc dot ca> writes:

> (gdb) bt
> #0  0x13c9c4 in get_func_frame_size (f=0x0) at ../../gcc/gcc/function.c:499
> #1  0x13c9dc in get_frame_size () at ../../gcc/gcc/function.c:507
> #2  0xc02a4 in dbxout_symbol_location (decl=0x7aeb1b60, type=0x7aeb13f0, 
>     suffix=0x0, home=0x7ae5bfb0) at ../../gcc/gcc/dbxout.c:2434
> #3  0xbf450 in dbxout_symbol (decl=0x7aeb1b60, local=2062226416)
>     at ../../gcc/gcc/dbxout.c:2260
>     ...
>
> The segmentation fault occurs because get_frame_size is called when cfun=0.
> The PA define for DEBUGGER_AUTO_OFFSET calls get_frame_size.  The question
> is why are we now trying to output debugging information for a local
> symbol when we don't have a current function?

*groan* This is probably caused by the removal of the separate binding
contour for parameter decls.  This should have been invisible outside
c-decl.c but clearly it wasn't.  Could you please try to debug this
further?  Find out why dbxout.c didn't emit this symbol earlier?

zw
 


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