Edit Page
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 72: | Line 72: | ||
If you get a message like: |
If you get a message like: |
||
in copy_chars_to_string16() [gui_string.c::196]: assertion 'pString != ((void *)0)' failed |
in copy_chars_to_string16() [gui_string.c::196]: assertion 'pString != ((void *)0)' failed |
||
β | and you can reproduce it, you can start your client or the server with the ''-F'' parameter to raise a signal on assertion failure; by default it will cause a |
+ | and you can reproduce it, you can start your client or the server with the ''-F'' parameter to raise a signal on assertion failure; by default it will cause a crash with a backtrace, which will probably be useful to diagnose the issue. If you've [[#Getting a core file|enabled coredumps]], a core file will be produced by default, which will allow you to get [[#Backtrace on Unix|a more detailed backtrace]]. |
If you are running with gdb, ''-F SIGINT'' (usually 2) is especially useful to interrupt the process, as you can resume with the ''continue'' gdb command. |
If you are running with gdb, ''-F SIGINT'' (usually 2) is especially useful to interrupt the process, as you can resume with the ''continue'' gdb command. |
||
β | |||
β | If you don't want to crash on assertions, but can rebuild Freeciv, then configuring it with <tt>--enable-debug</tt> at build time will cause it to output a simple backtrace on the console when these sort of messages happen, although it is not as detailed as a gdb backtrace would be. |
||
[[Category:Game Development]] |
[[Category:Game Development]] |