Well, I’ve tried running it from gdb and it worked fine. All attempts to
recreate the problem is not working. And when I used valgrind, it didn’t
work. It exited the valgrind even at the start of the program. When I
looked at the backtrace of valgrind, it returned lots of error like:
Use of uninitialised value of size 4
…
Invalid read of size 4
…
Syscall param ioctl(arg) contains uninitialised byte(s)
…
Syscall param write(buf) points to uninitialised byte(s)
…
Segmentation fault
The funny thing is, even when it cannot be run from valgrind, I can run it
from the terminal console (until the SDL Parachute deployed).
clemens kirchgatterer said:> On 2/21/07, @benang_at_cs.its.ac <@benang_at_cs.its.ac> wrote:
Hi, recently my application encountered an unusual bug. The bug seemed
random so I can’t recreate it (only if I was lucky enough). The bug
appears every now and then when I clicked the mouse. It displayed :
“Fatal signal: Segmentation Fault (SDL Parachute Deployed)”.The application itself was initiated inside of .xinitrc because I wanted
it to be started automatically everytime I logged in. So after the error
appears, I opened an xterm console and restarted the application. And
the
problem didn’t appear (yet!).The question is:
- What caused the SDL Parachute error?
- Why was it appear random ?
Can anybody help me? Many-many thanks in advance.
you have a memory corruption bug in your program. SDL caches the
segfault signal and tells with the error message. use a debugger and
valgrind to correct your program.best regards …
clemens
SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org
Fare thee well,
Bawenang R. P. P.
ERROR: Brain not found. Please insert a new brain!
?Do nothing which is of no use.? - Miyamoto Musashi.
“I live for my dream. And my dream is to live my life to the fullest.”