From: Jonathan B. <jbr...@ea...> - 2004-08-16 18:20:41
|
On Mon, 2004-08-16 at 14:02, Lew Riley wrote: > Jonathan Brandmeyer wrote: > > > Uh-oh. Yea, it sounds familiar. I'm assuming that you have a laptop. > > Do you by chance have a Pentium M processor in it (not a Pentium 3-M or > > Pentium 4-M)? > > Yep. I've got a Dell Latitude D600 with a Pentium M processor. > > > Please run one of the VPython programs that crashes in GDB (the GNU > > Debugger) by following these instructions, and send me the console > > output from the entire session. I'm hoping that setting MESA_DEBUG=1 in > > the environment will produce something useful, but it might not. > > > > OK. Here's the initial output and bactrace from gdb: Close. Can you repeat the process, only before you give GDB the "run" command, give it this one: `(gdb) handle SIGFPE nostop` and then complete the process as normal. The mesa code is supposed to cause SIGFPE, and then catch it. Since GDB caught the signal, the catch wasn't tested (and I think that is where the problem is). The extra command above tells GDB not to catch that signal. It will print out a message telling you that it was sent, though. Thanks, -Jonathan |