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
* [Bug libfortran/48931] Backtrace functionality not async-signal-safe
  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 ` jb at gcc dot gnu.org
  2011-05-15 10:18 ` jb at gcc dot gnu.org
                   ` (3 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: jb at gcc dot gnu.org @ 2011-05-14 16:00 UTC (permalink / raw)
  To: gcc-bugs

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

Janne Blomqvist <jb at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|unassigned at gcc dot       |jb at gcc dot gnu.org
                   |gnu.org                     |

--- Comment #1 from Janne Blomqvist <jb at gcc dot gnu.org> 2011-05-14 15:15:56 UTC ---
Assigning to myself.


^ permalink raw reply	[flat|nested] 6+ messages in thread
* [Bug libfortran/48931] Backtrace functionality not async-signal-safe
  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
                   ` (2 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: jb at gcc dot gnu.org @ 2011-05-15 10:18 UTC (permalink / raw)
  To: gcc-bugs

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

Janne Blomqvist <jb at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                URL|                            |http://gcc.gnu.org/ml/gcc-p
                   |                            |atches/2011-05/msg01058.htm
                   |                            |l

--- Comment #2 from Janne Blomqvist <jb at gcc dot gnu.org> 2011-05-15 09:38:56 UTC ---
Patch: http://gcc.gnu.org/ml/gcc-patches/2011-05/msg01058.html


^ permalink raw reply	[flat|nested] 6+ messages in thread
* [Bug libfortran/48931] Backtrace functionality not async-signal-safe
  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
  4 siblings, 0 replies; 6+ messages in thread
From: jb at gcc dot gnu.org @ 2011-05-22 17:00 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #3 from Janne Blomqvist <jb at gcc dot gnu.org> 2011-05-22 16:38:08 UTC ---
Author: jb
Date: Sun May 22 16:38:05 2011
New Revision: 174030

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=174030
Log:
PR 48931 Make backtrace async-signal-safe, reformat output

Modified:
    trunk/libgfortran/ChangeLog
    trunk/libgfortran/config.h.in
    trunk/libgfortran/configure
    trunk/libgfortran/configure.ac
    trunk/libgfortran/runtime/backtrace.c
    trunk/libgfortran/runtime/main.c


^ permalink raw reply	[flat|nested] 6+ messages in thread
* [Bug libfortran/48931] Backtrace functionality not async-signal-safe
  2011-05-08 19:27 [Bug libfortran/48931] New: Backtrace functionality not async-signal-safe jb at gcc dot gnu.org
                   ` (2 preceding siblings ...)
  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
  4 siblings, 0 replies; 6+ messages in thread
From: jb at gcc dot gnu.org @ 2011-05-22 17:05 UTC (permalink / raw)
  To: gcc-bugs

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

Janne Blomqvist <jb at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |FIXED

--- Comment #4 from Janne Blomqvist <jb at gcc dot gnu.org> 2011-05-22 16:41:16 UTC ---
Fixed, closing.


^ permalink raw reply	[flat|nested] 6+ messages in thread
* [Bug libfortran/48931] Backtrace functionality not async-signal-safe
  2011-05-08 19:27 [Bug libfortran/48931] New: Backtrace functionality not async-signal-safe jb at gcc dot gnu.org
                   ` (3 preceding siblings ...)
  2011-05-22 17:05 ` jb at gcc dot gnu.org
@ 2011-05-29 20:21 ` jb at gcc dot gnu.org
  4 siblings, 0 replies; 6+ messages in thread
From: jb at gcc dot gnu.org @ 2011-05-29 20:21 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #5 from Janne Blomqvist <jb at gcc dot gnu.org> 2011-05-29 20:13:56 UTC ---
Author: jb
Date: Sun May 29 20:13:52 2011
New Revision: 174415

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=174415
Log:
PR 48931 Use async-signal-safe execve instead of execvp

Modified:
    trunk/libgfortran/ChangeLog
    trunk/libgfortran/libgfortran.h
    trunk/libgfortran/runtime/backtrace.c
    trunk/libgfortran/runtime/compile_options.c
    trunk/libgfortran/runtime/main.c


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