1
0
1
3
1
3
1
Program received signal SIGSEGV, Segmentation fault. 0x00007ffff5e90508 in std::basic_string <char, std::char_traits<char>,
std::allocator<char> >::basic_string (std::string const&) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
paul424 {l Wrote}:Heh , are you any good in Computer Science ?
paul424 {l Wrote}:Ahh you run GDB ... now you would get a detailed stacktrace everytime the game crashes, isn't that nice ?
paul424 {l Wrote}:Sorry for large delays, we have political earthquake in Poland, nobody knows whether to cry of laugh ...
Sorry for large delays, we have political earthquake in Poland, nobody knows whether to cry of laugh ...
"Ah yes, we need to add the cegui parameter we talked about before.
Need to find that back."
Ehem which cegui parameter ?
My first and foremost intention was to have always stacktrace behind our eyes after the game crash, whatever the user or programmer is runnning OD , so there is some info of what went wrong , instead of the >> black box's << cog wheels got stuck ...
MCMic {l Wrote}:@Dm3d: With gdb you can use "bt" or "backtrace" to see the call trace after a crash (but on my computer OD does not give me my keyboard back so I’m stuck…)
Bertram {l Wrote}:Ehem which cegui parameter ?
Found it back:
https://github.com/Bertram25/OpenDungeo ... d5bb1e8751
With this patch, you can still play the game but use gdb freely also. This will ease OD development a lot.
Regards,
Users browsing this forum: No registered users and 1 guest