On Tue, Apr 1, 2008 at 1:50 AM, Christophe Rhodes <[EMAIL PROTECTED]> wrote: > For your information: I believe that this is (was) not a problem with > CMUCL, though the changes you have made to clear the direction flag > close to where you set it will work around most of the problem.
For your information this bug has nothing to do with the Linux kernel and everything to do with a failure to abide by the x86 calling convention. Any foreign call which makes use of a string instruction assuming the direction flag is clear runs the risk of corrupting memory. To reproduce this bug all you need to do is make a foreign call memcpy. You do not need to execute a signal handler and you do not need to be running on a Linux system either.
