valgrind --tool=memcheck --workaround-gcc296-bugs=yes --leak-check=yes
-v ./lyx 2>e.log
Question: Are you really using gcc 296? Pretty old, isn't it?
results in a segmentation fault and the attached file e.log.
==29571== Process terminating with default action of signal 11 (SIGSEGV)
==29571== at 0x1B8E967E: _dl_map_object_from_fd (in /lib/ld-2.3.3.so)
==29571== by 0x1B8EACC9: _dl_map_object (in /lib/ld-2.3.3.so)
==29571== by 0x1B8F09CD: openaux (in /lib/ld-2.3.3.so)
==29571== by 0x1B8F0D55: _dl_catch_error (in /lib/ld-2.3.3.so)
Ha! There's hope! Yesterday, LyX crashed with access to an invalid address.
Since I cannot debug on Windows I cannot provide any further information :-(
Do we have any valgrind expert here who can make sense of this or tell me
how I can find out where the segmentation fault happens?
There is an option (I don't remember which) that produces longer backtraces.
Set the chain length to 10+ so that we can see some familiar LyX function.
Eagerly awaiting your results,
Michael
