This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB 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 backtrace/11908] Debugging PIE works with core dump, but not "live"


------- Additional Comments From devurandom at gmx dot net  2010-08-15 22:41 -------
I also see it only on my hardened box. Maybe you have a tip for how I could get
closer to the cause of this?
What is different between showing the backtrace of a coredump and a running
program? And why does this difference only show when the application is compiled
using PIE?

The backtrace I get is:
Program received signal SIGSEGV, Segmentation fault.
0x400007263aed0a90 in ?? ()
(gdb) bt full
#0  0x400007263aed0a90 in ?? ()
No symbol table info available.
#1  0x400007263aed0ad0 in ?? ()
No symbol table info available.
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(without -nopie)

vs:
Program received signal SIGSEGV, Segmentation fault.
0x4000000000000650 in hallo () at test.c:2
2               *(char*)0 = 0;
(gdb) bt full
#0  0x4000000000000650 in hallo () at test.c:2
No locals.
#1  0x4000000000000690 in main () at test.c:6
No locals.
(with -nopie)

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=11908

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


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