[Bug libgcc/57405] Using printf in signal handler with alternate stack generates a SIGSEGV

["jkf at research dot att.com" <gcc-bugzilla at gcc dot gnu dot org>]

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

--- Comment #2 from jkf <jkf at research dot att.com> ---
Andrew,
According to POSIX the write function is allowed inside a signal handler. Since
eventually printf ends in a write(), I'm assuming it is valid. If printf()
isn't valid than please supply a list of valid libc functions from inside
signal handlers. 

Jeff Fellin

-----Original Message-----
From: pinskia at gcc dot gnu.org [mailto:gcc-bugzilla@gcc.gnu.org] 
Sent: Friday, May 24, 2013 16:54
To: FELLIN, JEFFREY K (JEFF)
Subject: [Bug libgcc/57405] Using printf in signal handler with alternate stack
generates a SIGSEGV

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|unknown                     |4.4.7

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Is calling
printf a valid thing to do inside this signal handler?

Also can you try a newer compiler 4.4.7 is no longer supported.  Since you are
using a redhat supplied GCC, you really should reporting it to them.

--
You are receiving this mail because:
You reported the bug.