> So now I got very frequent segfaults in my development version of POV-R
ay -
> frequent enough to be reproducible even with the non-optimized debug ve
rsion
> within a few seconds. Time to track them down with valgrind and gdb.
> 
> Hum... so now I know in which *function* it crashes - but what do I hav
e to do
> in order to get the *line number*??
> 
> Digging through assembler code and trying to match it with the C++ sour
ce code
> is a bit cumbersome, so I guess there *must* be an easier way... even L
inux
> jockeys can't be *that* masochistic :)
> 
> I knew I wouldn't like debugging under Linux :S
> 
> 
> 


To debug, you should run povray with gdb. Then you'll be able to add 
breakpoint and/or view the stack-trace on a segfault

another way is to integrate povray sources in a project under KDevelop 
and then run in debug mode .. it will show you the "wrong" code

good luck

Post a reply to this message