2 Nov
2005
2 Nov
'05
3:25 p.m.
On Wednesday 02 November 2005 14:10, Udo A. Steinberg wrote: Try disassembling the offending program (Task E) using objdump -DC <binary> and find out what's at EIP 0x1303a78. I bet it's a DIV instruction and the operand is 0.
On Wednesday 02 November 2005 14:48, Frank Mehnert wrote: Please use ute<SPACE>1303a78<SPACE>
Yes, the faulting assembler instruction in the coresponding task (the "run" module) at 0x1303a78 is in fact IDIV.
Marko