--- Comment #5 from pinskia at gcc dot gnu dot org 2006-04-20 16:15 ---
And this is the wrong place for help with signals anyways, please first ask in
a solaris specific mailing list or news group.
--
pinskia at gcc dot gnu dot org changed:
What|Removed
--- Comment #4 from rguenth at gcc dot gnu dot org 2006-04-20 10:49 ---
I would suggest using SIGUSR1 for testing, malloc and free are not affected by
signal interruption. So if they are, this is internal to the Solaris libc or
the kernel. At a first guess I would suggest updating the
--- Comment #3 from ademin at gmail dot com 2006-04-20 10:12 ---
(In reply to comment #2)
> This is more likely a problem with your kernel/libc than with libstdc++ or
> gcc.
> Also on linux i386 signal 19 is SIGSTOP, for which sigset returns SIG_HOLD.
>
Now I tried it with signal 17.
--- Comment #2 from rguenth at gcc dot gnu dot org 2006-04-20 09:54 ---
This is more likely a problem with your kernel/libc than with libstdc++ or gcc.
Also on linux i386 signal 19 is SIGSTOP, for which sigset returns SIG_HOLD.
--
rguenth at gcc dot gnu dot org changed:
--- Comment #1 from ademin at gmail dot com 2006-04-20 09:38 ---
Created an attachment (id=11302)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11302&action=view)
.ii file of test case program
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27223
