[Bug libfortran/29649] Force core dump on runtime library errors

2007-01-18 Thread burnus at gcc dot gnu dot org
--- Comment #14 from burnus at gcc dot gnu dot org 2007-01-18 12:54 --- Subject: Bug 29649 Author: burnus Date: Thu Jan 18 12:54:11 2007 New Revision: 120897 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=120897 Log: 2007-01-18 Francois-Xavier Coudert [EMAIL PROTECTED]

[Bug libfortran/29649] Force core dump on runtime library errors

2007-01-18 Thread burnus at gcc dot gnu dot org
--- Comment #15 from burnus at gcc dot gnu dot org 2007-01-18 12:56 --- Fixed in the trunk. Creating a backtrace is now PR 30498. -- burnus at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/29649] Force core dump on runtime library errors

2007-01-11 Thread fxcoudert at gcc dot gnu dot org
-- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added AssignedTo|unassigned at gcc dot gnu |burnus at gcc dot gnu dot |dot org

[Bug libfortran/29649] Force core dump on runtime library errors

2007-01-05 Thread fxcoudert at gcc dot gnu dot org
--- Comment #12 from fxcoudert at gcc dot gnu dot org 2007-01-05 14:03 --- (In reply to comment #11) A draft patch was posted (quite a while ago) by FX: http://gcc.gnu.org/ml/fortran/2006-11/msg00634.html I'd add that it's easy to separate the coredump part of the patch (handling of

[Bug libfortran/29649] Force core dump on runtime library errors

2007-01-05 Thread patchapp at dberlin dot org
--- Comment #13 from patchapp at dberlin dot org 2007-01-05 21:25 --- Subject: Bug number PR29649 A patch for this bug has been added to the patch tracker. The mailing list url for the patch is http://gcc.gnu.org/ml/gcc-patches/2007-01/msg00431.html --

[Bug libfortran/29649] Force core dump on runtime library errors

2007-01-02 Thread fxcoudert at gcc dot gnu dot org
-- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added AssignedTo|fxcoudert at gcc dot gnu dot|unassigned at gcc dot gnu |org

[Bug libfortran/29649] Force core dump on runtime library errors

2007-01-02 Thread burnus at gcc dot gnu dot org
--- Comment #11 from burnus at gcc dot gnu dot org 2007-01-02 15:10 --- (Just to make sure it is not forgotten:) A draft patch was posted (quite a while ago) by FX: http://gcc.gnu.org/ml/fortran/2006-11/msg00634.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29649

[Bug libfortran/29649] Force core dump on runtime library errors

2006-11-19 Thread fxcoudert at gcc dot gnu dot org
--- Comment #10 from fxcoudert at gcc dot gnu dot org 2006-11-19 14:58 --- Working on this -- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/29649] Force core dump on runtime library errors

2006-11-02 Thread pinskia at gcc dot gnu dot org
--- Comment #8 from pinskia at gcc dot gnu dot org 2006-11-02 23:42 --- PR 5773 is about addr2line in gcj. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/29649] Force core dump on runtime library errors

2006-11-02 Thread fxcoudert at gcc dot gnu dot org
--- Comment #9 from fxcoudert at gcc dot gnu dot org 2006-11-02 23:52 --- We can fork+exec addr2line, but we can't link libbfd because it's GPL. It was mentionned on IRC tonight that Daniel Berlin has a library that extracts line and file information from DWARF2 info. It's internal to

[Bug libfortran/29649] Force core dump on runtime library errors

2006-10-31 Thread fxcoudert at gcc dot gnu dot org
--- Comment #4 from fxcoudert at gcc dot gnu dot org 2006-10-31 16:01 --- (In reply to comment #3) coredumping is easy, simply call abort() or kill(0,SIGSEGV) The usual signal to request a core dump is SIGQUIT. However, I'm more a fan of either coredumping Same opinion here.

[Bug libfortran/29649] Force core dump on runtime library errors

2006-10-31 Thread burnus at gcc dot gnu dot org
--- Comment #3 from burnus at gcc dot gnu dot org 2006-10-31 15:54 --- Nice idea. coredumping is easy, simply call abort() or kill(0,SIGSEGV) and make sure that ulimit -c (csh: limit core) shows a big enough number. This is actually what NAG f95 does and has the advantage that one can

[Bug libfortran/29649] Force core dump on runtime library errors

2006-10-31 Thread fxcoudert at gcc dot gnu dot org
--- Comment #5 from fxcoudert at gcc dot gnu dot org 2006-10-31 16:02 --- Created an attachment (id=12519) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12519action=view) Example of how to use unwind for backtrace purposes The patch I was quoting in my previous comment; here, it

[Bug libfortran/29649] Force core dump on runtime library errors

2006-10-31 Thread burnus at gcc dot gnu dot org
--- Comment #6 from burnus at gcc dot gnu dot org 2006-10-31 18:37 --- Using unwind is the way to go for a more serious solution. Looks nice as a starting point. (My biggest problem with developing this would be to find out whether it works on strange machines like Sparc, Windows etc.)

Re: [Bug libfortran/29649] Force core dump on runtime library errors

2006-10-31 Thread Andrew Pinski
- 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

[Bug libfortran/29649] Force core dump on runtime library errors

2006-10-31 Thread pinskia at physics dot uc dot edu
--- 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

[Bug libfortran/29649] Force core dump on runtime library errors

2006-10-30 Thread fxcoudert at gcc dot gnu dot org
--- Comment #1 from fxcoudert at gcc dot gnu dot org 2006-10-30 12:24 --- I think it's better to file it with the library. -- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/29649] Force core dump on runtime library errors

2006-10-30 Thread P dot Schaffnit at access dot rwth-aachen dot de
--- Comment #2 from P dot Schaffnit at access dot rwth-aachen dot de 2006-10-30 12:29 --- I think a '-traceback' would be a very nice enhancement! (as you could then have the likes of 'ERRTRA' from Lahey or 'TRACEBACKQQ' from Compaq, I forgot how it translates with Intel...) -- P