Topic: gdb backtrace easy way
|
Tibor Topic Opener
Joined:
2009-03-23, 23:24 UTC+1.0
Posts: 1377  One Elder of Players Location: Slovakia |
Posted at:
2017-10-07, 22:51 UTC+2.0
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, 22:52 UTC+2.0
Top
Quote
|
GunChleoc
Joined:
2013-10-07, 15:56 UTC+2.0
Posts: 3317 One Elder of Players Location: RenderedRect |
Posted at:
2017-10-09, 21:03 UTC+2.0
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
Joined:
2009-03-23, 23:24 UTC+1.0
Posts: 1377 One Elder of Players Location: Slovakia |
Posted at:
2017-10-09, 21:41 UTC+2.0
I was thinking about this... I added there item 6, please review it....
Top
Quote
|
|
GunChleoc
Joined:
2013-10-07, 15:56 UTC+2.0
Posts: 3317 One Elder of Players Location: RenderedRect |
Posted at:
2017-10-14, 17:54 UTC+2.0
Thanks! Proofreading done Busy indexing nil values
Top
Quote
|
kaputtnik
Joined:
2013-02-18, 20:48 UTC+1.0
Posts: 2683 OS: Archlinux Version: current master One Elder of Players Location: Germany |
Posted at:
2017-10-16, 23:39 UTC+2.0
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.
Top
Quote
|
|
Tibor Topic Opener
Joined:
2009-03-23, 23:24 UTC+1.0
Posts: 1377 One Elder of Players Location: Slovakia |
Posted at:
2017-10-17, 07:40 UTC+2.0
Good point. I updated the wiki accordingly.
Top
Quote
|
