http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54572
--- Comment #15 from Janne Blomqvist 2012-12-01
19:48:12 UTC ---
(In reply to comment #14)
> Thanks for the additional info.
>
> #1 0x77bb53be in build_address_map (addrs=0x7fffc710,
> data=0x7fffcf1c,
> error_cal
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54572
--- Comment #14 from Ian Lance Taylor 2012-12-01 06:43:07
UTC ---
Thanks for the additional info.
#1 0x77bb53be in build_address_map (addrs=0x7fffc710,
data=0x7fffcf1c,
error_callback=0x77ad51f0 , is_bigendian=
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54572
--- Comment #13 from Janne Blomqvist 2012-11-30
22:03:43 UTC ---
(In reply to comment #10)
> (In reply to comment #6)
> > Created attachment 28779 [details]
> > Patch to use libbacktrace
>
> I have to apply the following patch on your
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54572
--- Comment #12 from Janne Blomqvist 2012-11-30
21:56:29 UTC ---
(In reply to comment #9)
> (In reply to comment #7)
> > Why are there no line numbers in the backtrace from gdb? You said you
> > compiled
> > with -g. Are you sure that
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54572
Tobias Burnus changed:
What|Removed |Added
CC||burnus at gcc dot gnu.org
--- C
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54572
--- Comment #10 from Tobias Burnus 2012-11-27
09:32:55 UTC ---
(In reply to comment #6)
> Created attachment 28779 [details]
> Patch to use libbacktrace
I have to apply the following patch on your patch in order to be able to
compile i
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54572
--- Comment #9 from Janne Blomqvist 2012-11-27 08:58:59
UTC ---
(In reply to comment #7)
> Why are there no line numbers in the backtrace from gdb? You said you
> compiled
> with -g. Are you sure that libbacktrace itself was compiled wi
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54572
--- Comment #8 from Ian Lance Taylor 2012-11-26 23:08:45
UTC ---
The crash within libbacktrace is occurring as it tries to read the debug info.
This is presumably a bug in libbacktrace, but I don't know what the problem is
without more in
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54572
--- Comment #7 from Ian Lance Taylor 2012-11-26 23:02:46
UTC ---
Why are there no line numbers in the backtrace from gdb? You said you compiled
with -g. Are you sure that libbacktrace itself was compiled with -g?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54572
--- Comment #6 from Janne Blomqvist 2012-11-26 16:46:08
UTC ---
Created attachment 28779
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=28779
Patch to use libbacktrace
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54572
Janne Blomqvist changed:
What|Removed |Added
CC||ian at airs dot com
--- Comme
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54572
Janne Blomqvist changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54572
--- Comment #3 from Hans-Peter Nilsson 2012-09-16
23:16:02 UTC ---
(In reply to comment #2)
> (In reply to comment #1)
> > You need unwind frames present for this to work,
> How is this different from the current backtracing implementation in
>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54572
--- Comment #2 from Janne Blomqvist 2012-09-16 08:33:42
UTC ---
(In reply to comment #1)
> You need unwind frames present for this to work, i.e. the space (and to some
> extent optimization-reducing - yes I'm sure) overhead of -funwind-tables.
>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54572
Hans-Peter Nilsson changed:
What|Removed |Added
CC||hp at gcc dot gnu.org
--- Comment #1
15 matches
Mail list logo
