Hi,
I try to figure out some segfaults but before I want to write any bug reports, I want to narrow it down more. Now, it always says "core dumped", but the system.log of Ubuntu isn't telling too much. Does FG dump another file and if so, where?
J.
I want to write any bug reports, I want to narrow it down more. Now, it always says "core dumped", but the system.log of Ubuntu isn't telling too much. Does FG dump another file and if so, where?
Hooray wrote:you need to run a binary with embedded debugging symbols to come up with a useful stack trace: http://wiki.flightgear.org/Building_usi ... bug_Builds
Hooray wrote:chrisb wrote in Mon Mar 17, 2014 2:16 am:Are there any debug tools I can use, the main problem I have is that I cant trigger the crash as it seems to be totally random I also cant decipher the crash report
You would need a so called "debugger" and a binary with debugging symbols linked into it, which would give you a so called "backtrace".chrisb wrote in Mon Mar 17, 2014 2:16 am:Does an FGFS version exist that has debug turned on?
I think the build server binaries ("nightlies") should have debugging symbols linked in, but you'll still need to use a debugger (i.e. MSVC++) to actually make use of those.chrisb wrote in Mon Mar 17, 2014 2:16 am:How do I compile FG on windows?
http://wiki.flightgear.org/Superbuild
If that doesn't work for you, use these instructions instead:
http://wiki.flightgear.org/Building_usi ... _-_Windows
Hooray wrote:http://forum.flightgear.org/viewtopic.php?p=202695#p202695
viewtopic.php?f=25&t=22288&p=202494&hilit=backtrace+gdb#p202494
viewtopic.php?f=25&t=21970&p=199630&hilit=backtrace+gdb#p199630
Users browsing this forum: No registered users and 13 guests