public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/54572] Use libbacktrace library
Date: Tue, 27 Nov 2012 10:06:00 -0000 [thread overview]
Message-ID: <bug-54572-4-obSxU1q9Pd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54572-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54572
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |burnus at gcc dot gnu.org
--- Comment #11 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-11-27 10:05:50 UTC ---
After compiling comment 5 with my changes of comment 10, I get:
Backtrace for this error:
0x2b9567c7ca0d _gfortrani_show_backtrace
/projects/tob/gcc-git/gcc/libgfortran/runtime/backtrace.c:92
0x2b9567c7d017 _gfortrani_backtrace_handler
/projects/tob/gcc-git/gcc/libgfortran/runtime/compile_options.c:129
0x2b95687503ef ???
???:0
0x40086b __test_MOD_c
/dev/shm/foo.f90:5
0x400847 __test_MOD_b
/dev/shm/foo.f90:10
0x40081a __test_MOD_a
/dev/shm/foo.f90:15
0x400897 bt
/dev/shm/foo.f90:22
0x40092f main
/dev/shm/foo.f90:20
And before (i.e with addr2line), I got:
Backtrace for this error:
#0 0x2AC1DC8D7AE7
#1 0x2AC1DC8D80F2
#2 0x2AC1DD3A43EF
#3 0x40086B in __test_MOD_c at foo.f90:5
#4 0x400847 in __test_MOD_b at foo.f90:10
#5 0x40081A in __test_MOD_a at foo.f90:15
#6 0x400897 in bt at foo.f90:22
next prev parent reply other threads:[~2012-11-27 10:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 22:26 [Bug fortran/54572] New: " burnus at gcc dot gnu.org
2012-09-15 11:26 ` [Bug fortran/54572] " hp at gcc dot gnu.org
2012-09-16 8:33 ` jb at gcc dot gnu.org
2012-09-16 23:16 ` hp at gcc dot gnu.org
2012-11-25 15:10 ` jb at gcc dot gnu.org
2012-11-26 16:43 ` jb at gcc dot gnu.org
2012-11-26 16:46 ` jb at gcc dot gnu.org
2012-11-26 23:03 ` ian at airs dot com
2012-11-26 23:09 ` ian at airs dot com
2012-11-27 8:59 ` jb at gcc dot gnu.org
2012-11-27 9:33 ` burnus at gcc dot gnu.org
2012-11-27 10:06 ` burnus at gcc dot gnu.org [this message]
2012-11-30 21:56 ` jb at gcc dot gnu.org
2012-11-30 22:03 ` jb at gcc dot gnu.org
2012-12-01 6:43 ` ian at airs dot com
2012-12-01 19:48 ` jb at gcc dot gnu.org
2015-08-14 8:33 ` [Bug libfortran/54572] " fxcoudert at gcc dot gnu.org
2015-08-23 21:51 ` fxcoudert at gcc dot gnu.org
2015-08-23 21:52 ` fxcoudert at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-54572-4-obSxU1q9Pd@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).