| |||||||||||||
Why is this a problem?Why is this a problem?Posted Mar 8, 2008 0:27 UTC (Sat) by jake (editor, #205)In reply to: Why is this a problem? by vonbrand Parent article: GCC 4.3.0 exposes a kernel bug
> No, it has nothing to do with calling mem<foo> in a signal handler. What I was trying to say is that it would be a memmove() or something like it in the signal handler that would be tripped up by DF being set unexpectedly. jake
(Log in to post comments)
|
|||||||||||||