Topic: gdb backtrace easy way
Tibor Topic Opener |
Posted at: 2017-10-07, 21:51
Hi, This is to share with you an easy way how to get backtrace in case of crash on Linux, without deeper understanding how gdb tool works. Just use command like this:
So the entire command can look like:
So this will start the game, just play as usual and if game crashes, the file gdb.log will contain all console output including gdb backtrace at the end of file. Than you can provide it as a part of bug report. Edited: 2017-10-07, 21:52
Top Quote |
GunChleoc |
Posted at: 2017-10-09, 20:03
I think we should have this on https://wl.widelands.org/wiki/How%20to%20Write%20a%20Good%20Bug%20Report/ Busy indexing nil values Top Quote |
Tibor Topic Opener |
Posted at: 2017-10-09, 20:41
I was thinking about this... I added there item 6, please review it.... Top Quote |
GunChleoc |
Posted at: 2017-10-14, 16:54
Thanks! Proofreading done Busy indexing nil values Top Quote |
kaputtnik |
Posted at: 2017-10-16, 22:39
I want to suggest to add a ' LC_ALL=C' at the beginning of the command, to overwrite current localization:
Otherwise on my system the output may contain unrecognized characters. Fight simulator for Widelands: |
Tibor Topic Opener |
Posted at: 2017-10-17, 06:40
Good point. I updated the wiki accordingly. Top Quote |