This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug backtrace/14492] broken with -fPIE -pie
- From: "jan.kratochvil at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Sun, 19 Aug 2012 05:06:22 +0000
- Subject: [Bug backtrace/14492] broken with -fPIE -pie
- Auto-submitted: auto-generated
- References: <bug-14492-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=14492
Jan Kratochvil <jan.kratochvil at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
--- Comment #6 from Jan Kratochvil <jan.kratochvil at redhat dot com> 2012-08-19 05:06:22 UTC ---
So gdb-7.4.1 also cannot find symbol for frame #0, it is not a regression.
Matching 'mappings' entry is:
0x3fff7f4e000 0x3fff7fce000 0x80000 0x0
This confirms my suspection it is a JIT-generated code.
'crack-language' should provide a GDB JIT module to use via:
(gdb) jit-reader-load some-future-jit-module-from-crack-language.so
'crack-language' is aware it does not support debugging:
# Crack has only minimal support for debugging in 0.6. If your program
# seg-faults or aborts, you can at least get a sparse stack-trace by running it
# in JIT mode under a fairly recent version of GDB (7.0 or later).
OK to make it RESOLVED-INVALID? This is 'crack-language' Bug, not GDB's.
(BTW I would be interested why happened the 0x0 entries in 'info proc mappings'
as this code has changes 7.4->7.5.)
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.