public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libfortran/48931] New: Backtrace functionality not async-signal-safe
@ 2011-05-08 19:27 jb at gcc dot gnu.org
  2011-05-14 16:00 ` [Bug libfortran/48931] " jb at gcc dot gnu.org
                   ` (4 more replies)
  0 siblings, 5 replies; 6+ messages in thread
From: jb at gcc dot gnu.org @ 2011-05-08 19:27 UTC (permalink / raw)
  To: gcc-bugs

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48931

           Summary: Backtrace functionality not async-signal-safe
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: minor
          Priority: P3
         Component: libfortran
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: jb@gcc.gnu.org


When -fbacktrace is enabled, gfortran enables a signal handler for the common
failure signals, and tries to print a backtrace in the handler. On Linux
platforms this is accomplished with the glibc backtrace() and
backtrace_symbols() functions. However, backtrace_symbols() uses malloc() to
allocate memory and is hence not safe to use within a signal handler. 

It might be possible to instead use backtrace_symbols_fd() and output either
directly to STDERR_FILENO, or to a pipe.


^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2011-05-29 20:14 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-05-08 19:27 [Bug libfortran/48931] New: Backtrace functionality not async-signal-safe jb at gcc dot gnu.org
2011-05-14 16:00 ` [Bug libfortran/48931] " jb at gcc dot gnu.org
2011-05-15 10:18 ` jb at gcc dot gnu.org
2011-05-22 17:00 ` jb at gcc dot gnu.org
2011-05-22 17:05 ` jb at gcc dot gnu.org
2011-05-29 20:21 ` jb at gcc dot gnu.org

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).