Bug#447036: gnumach: panic: fp_intr: already caught intr

2007-10-17 Thread Samuel Thibault
Samuel Thibault, le Thu 18 Oct 2007 00:32:49 +0100, a écrit : > Uh, odd: with qemu, the program just fails. Natively, it loops getting > SIGFPEs and not making progress. With Xen, I was getting another panic > which was because Xen doesn't provide the interrupt, it's now fixed and > behaves like

Bug#447036: gnumach: panic: fp_intr: already caught intr

2007-10-17 Thread Samuel Thibault
Hi, Uh, odd: with qemu, the program just fails. Natively, it loops getting SIGFPEs and not making progress. With Xen, I was getting another panic which was because Xen doesn't provide the interrupt, it's now fixed and behaves like native. The mileage probably vary according to the CPU... Could

Bug#447036: gnumach: panic: fp_intr: already caught intr

2007-10-17 Thread Michael Banck
On Wed, Oct 17, 2007 at 06:14:15PM +0200, Michael Banck wrote: > static void fpe_sig_handler(int sig) > { > erl_fp_exception = 1; > } > > static void do_init(void) > { > signal(SIGFPE, fpe_sig_handler); > unmask_fpe(); > } Hrm, maybe I forgot to mention that the original code has some

Bug#447036: gnumach: panic: fp_intr: already caught intr

2007-10-17 Thread Michael Banck
Package: gnumach Version: 2:1.3.99.dfsg.cvs20070809-1 I get the following panic during configure of erlang ("checking for unreliable floating point execptions"): panic: fp_intr: already caught intr Kernel Breakpoint trap, eip 0x117d07 Stopped at 0x117d06: int $3 The trace is: 0x117d06 Debugger