Thierry CHARLES <thierry@_no_spam_les-charles.net> wrote:
> 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

I can get a stack trace from the coredump - but it doesn't show line numbers.

I can also get interesting information from valgrind - but it doesn't give me
line numbers either.

> 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

.... and I'm not really eager to set up some KDevelop project:

- Getting an existing project to compile in yet another IDE typically sucks.

- Getting it to compile in an IDE you don't know sucks even more.

- Getting it to compile in an IDE you haven't even installed (ever) sucks like
crazy.

- Getting it to compile in an IDE that, by its name, seems to require a GUI
(KDE) you haven't even installed (ever) promises to be really sucking like
hell.

If I had my way, I'd prefer that sneaky piece of software to crash on my Windows
machine as well, where I have a nice, familiar IDE at hand and a project already
set up for it :S

Post a reply to this message