This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: [Bug libfortran/29649] Force core dump on runtime library errors
- From: Andrew Pinski <pinskia at physics dot uc dot edu>
- To: gcc-bugzilla at gcc dot gnu dot org
- Cc: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 31 Oct 2006 14:13:02 -0500 (EST)
- Subject: Re: [Bug libfortran/29649] 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