This is the mail archive of the
mailing list for the GCC project.
Re: GCC stack backtraces
On 08/29/2012 06:21 PM, Ian Lance Taylor wrote:
The DWARF reader calls malloc and is therefore not async-signal safe.
It also is a problem if the crash in the program is due to overwriting
the malloc heap administration (which easily occurs in Fortran if you
overwrite bounds of allocatable arrays that can't be caught by
bounds-check due to the wrong bounds being used inside a subroutine).
I have had Fortran program tracebacks (as described by Janne) hanging
due to this, which is hard to work around (euphemism).
Toon Moene - e-mail: firstname.lastname@example.org - phone: +31 346 214290
Saturnushof 14, 3738 XG Maartensdijk, The Netherlands
At home: http://moene.org/~toon/; weather: http://moene.org/~hirlam/
Progress of GNU Fortran: http://gcc.gnu.org/wiki/GFortran#news