Re: Detecting Seg faults

[Francesco Orsenigo <xarvh@lombardiacom.it>]

I run:

valgrind xarvh

This outputs a long list of "errors" all concerning libGL, libGLcore, libc, 
libX11 and some references to freeglut.

Then these:

disInstr: unhandled instruction bytes: 0xF 0xF 0x5 0x98
          at 0x1CDAF1C3: ???
==2097== 
==2097== Process terminating with default action of signal 4 (SIGILL)
==2097==  Illegal operand at address 0xB00252C0
==2097==    at 0x1CDAF1C3: ???
==2097==    by 0x1BFDB7CE: (within /usr/lib/libGLcore.so.1.0.6111)
==2097== 
==2097== ERROR SUMMARY: 2204 errors from 103 contexts (suppressed: 43 from 1)
==2097== malloc/free: in use at exit: 6786029 bytes in 517 blocks.
==2097== malloc/free: 796 allocs, 279 frees, 10551157 bytes allocated.
==2097== For a detailed leak analysis,  rerun with: --leak-check=yes
==2097== For counts of detected errors, rerun with: -v
==2099== 
==2099== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 43 from 1)
==2099== malloc/free: in use at exit: 4042 bytes in 17 blocks.
==2099== malloc/free: 47 allocs, 30 frees, 676267 bytes allocated.
==2099== For a detailed leak analysis,  rerun with: --leak-check=yes
==2099== For counts of detected errors, rerun with: -v


The program is killed by SIGILL long before any bad instruction may be given.
Am I failing something?
I tryied "-v" switch, but results are almost the same.


Thanx,
Francesco Orsenigo