[Kdenlive-devel] backtrace

[Rolf Dubitzky]

Hi,

I implemented a runtime backtrace, so if you run piave at least with '-v' or 
with '-d' then you'll get something like this in case of a seg fault. I don't 
know how to get the sourcecode linenumbers (help anybody??), but at least you 
can see the method that crashed, in this case "Frame::makeVBuf". I hope that 
will be helpfull in some cases where users don't want to bother with gdb and 
still send bugreports.

Cheers, Rolf

piave_base.cc:227 WARNING: PIAVE caught a segmentation violation
--- backtrace ------ start ----
/scratch/users/dubitzky/src/piave/libpiave/.libs/libpiave.so.0(printBackTrace__Q25PIAVE6Global+0x29) 
[0x4002c975]
/scratch/users/dubitzky/src/piave/libpiave/.libs/libpiave.so.0(fatalSignalHandler__Q25PIAVE6Globali+0xa6) 
[0x4002cabe]
/lib/libpthread.so.0 [0x40379307]
/lib/libc.so.6 [0x406b3ef8]
/usr/lib/libstdc++-libc6.2-2.so.3(__ls__7ostreamPCc+0xd0) [0x401faef0]
/scratch/users/dubitzky/src/piave/libpiave/.libs/libpiave.so.0(makeVBuf__Q25PIAVE5FrameRCQ25PIAVE6PixFmtPUc+0x2b) 
[0x40033df3]
/scratch/users/dubitzky/src/piave/libpiave/.libs/libpiave.so.0(putFrame__Q25PIAVE12OutSDLStreamRQ25PIAVE5Frame+0x137) 
[0x4003f36f]
/scratch/users/dubitzky/src/piave/libpiave/.libs/libpiave.so.0(veml_seek__Q25PIAVE14KdenLiveServerPCQ25PIAVE8VEMLCmnd+0x15e) 
[0x40056052]
/scratch/users/dubitzky/src/piave/libpiave/.libs/libpiave.so.0(processCommands__Q25PIAVE14KdenLiveServer+0x138) 
[0x400546bc]
/scratch/users/dubitzky/src/piave/libpiave/.libs/libpiave.so.0(_process_commands__Q25PIAVE14KdenLiveServerPv+0x10) 
[0x40052a70]
/lib/libpthread.so.0 [0x40375f77]
/lib/libc.so.6(__clone+0x3a) [0x40767eba]
--- backtrace ------ stop -----


***************************************************************
 Rolf Dubitzky  
 e-mail: Rolf.Dubitzky at Physik.TU-Dresden.de
 s-mail see http://hep.phy.tu-dresden.de/~dubitzky/
***************************************************************