|
From: Jeroen N. W. <jn...@xs...> - 2004-08-25 18:34:59
|
It looks as if I have stumbled across a bug in the way valgrind (CVS) handles signal SIGFPE. To demonstrate this problem, I have created and attached file SIGFPEc.c. The problem: When I run this program stand-alone [output in attached file SIGFPEc.check.txt], it shows that that siginfo->si_addr points somewhere in my executable. But when I run the very same executable under valgrind --tool=memcheck [output in attached file SIGFPEc.valgrind.txt], siginfo->si_addr points somewhere in valgrind's stage2. Note: I use a simplistic way to generate the SIGFPE. When I compile file SIGFPEc.c with gcc -O2, the SIGFPE does not happen, at least on my boxen. Compiling without any -O option does the trick. Please let me know if this is a real bug, and if you need a bug report. Jeroen. |