This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libfortran/29649] Force core dump on runtime library errors
- From: "pinskia at physics dot uc dot edu" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 31 Oct 2006 19:10:39 -0000
- Subject: [Bug libfortran/29649] Force core dump on runtime library errors
- References: <bug-29649-9410@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #7 from pinskia at physics dot uc dot edu 2006-10-31 19:10 -------
Subject: Re: Force core dump on runtime library errors
> - Support for coredumps (compile time? Environment variable? The latter
> overwriting the former?)
> [Advantage compile-time option: The core is there, if one needs it. Advantage
> run-time option: One can quickly turn it on, if needed.]
>
> - Traceback support more or less as outlined above (comment 4, comment 3),
> which prints only the Hex address (similar to the unwind.diff, attachment
> 12519) or the backtrace_symbols() example in comment 3). One should mention the
> addr2line program in the manpage/manual.
>
> - Optionally, linking with libbfd and providing symbol-resolved traceback.
Unless you want to make your program GPL, I would go against this. This is why
for libgcj, they have not linked it in yet.
-- Pinski
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29649