Strange compiler behavior
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 16 lines
Quoted 15 lines · John David Anglin
Quoted 14 lines
The limited stack trace is:
Program received signal SIGSEGV, Segmentation fault.
0x000255fcinpop_everything()
(gdb) bt#0 0x000255fc in pop_everything () #1 0x0002f834 in cxx_insert_default_attributes () #2 0x00072688 in cxx_make_type () #3 0x000b7870 in c_common_parse_file () #4 0x0022bb8c in rtx_addr_varies_p () #5 0x00231224 in rtx_addr_varies_p () #6 0x002312e8 in rtx_addr_varies_p () #7 0x401ee6e4 in __libc_start_main () from /lib/libc.so.6 #8 0x00016a58 in ?? ()
Quoted 5 lines
Quoted 1 line
This stack trace looks wierd at the higher numbers.
This is because the binary is stripped so the symbol info for static functions are lost. All those
rtx_address_varies_p()references are probably pointing to static functions.
Still seems strange to me. Are you sure that the start of the unwind region for each frame matches the symbol printed? I guess the symbols are from .dynsym. Isn't main in .dynsym?
Dave
Signature · 7 lines
J. David Anglin [email protected] National Research Council of Canada (613) 990-0752 (FAX: 952-6602) -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]