Re: PROBLEM: Caught SIGFPE exceptions aren't reset

2007-08-29 Thread Chuck Ebbert
On 08/25/2007 01:31 PM, Clark Cooper wrote: >> Your handler can do this by masking >> exceptions, changing the operands of the failed FP instruction, >> or by changing the PC so that the failed instruction is skipped >> (your handler may want to emulate the instruction in this case). > > Given th

Re: PROBLEM: Caught SIGFPE exceptions aren't reset

2007-08-25 Thread Clark Cooper
Thank you for your prompt answer. You wrote: > Your handler can do this by masking > exceptions, changing the operands of the failed FP instruction, > or by changing the PC so that the failed instruction is skipped > (your handler may want to emulate the instruction in this case). Given the cur

Re: PROBLEM: Caught SIGFPE exceptions aren't reset

2007-08-25 Thread Mikael Pettersson
Clark Cooper writes: > [1] Caught SIGFPE exceptions aren't reset > > [2] > On an i386, you can set a handler for a SIGFPE signal, and after > enabling FP > exceptions with feenableexceptions(), an FP exception will cause > your handler > to be called. However after the handle

PROBLEM: Caught SIGFPE exceptions aren't reset

2007-08-24 Thread Clark Cooper
[1] Caught SIGFPE exceptions aren't reset [2] On an i386, you can set a handler for a SIGFPE signal, and after enabling FP exceptions with feenableexceptions(), an FP exception will cause your handler to be called. However after the handler returns, it is called again with the sam