Compile taspring with debug messages.

[nir_hp]

Hi,

I compiled myself my taspring for slamd64,
I noticed that everytime it crashes, it does not plot any debug data in the infolog.txt.

How can I make it plot the reason for crashing? (maybe it is not exactly called debug messages)

Or maybe the infolog.txt isn't the place to look for the reasons for the crash?

[Kloot]

Stacktraces are only generated by Windows builds, since the
Linux executables aren't officially distributed and so can vary
in binary signature (due to compiler version differences, etc)
making the trace addresses meaningless for everyone except
the person who got the crash. The only way to obtain them is
by running a debug build in gdb.