You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Crashing prints a stack trace, but (on MacOS at least) it appear the stack trace does not match the cause of the issue. This appears to be related to the build script as even a non-swingame code compiled with that script fails to provide the correct stack trace.
Values from the stack trace should be able to be used with gbd to get line information.
Script to get line info follows. It requires the user to paste in the stack trace:
sed -e 's/^ \$/info line *0x/' > trace.gdb
gdb $EXE_PATH -batch -x trace.gdb
The text was updated successfully, but these errors were encountered:
Crashing prints a stack trace, but (on MacOS at least) it appear the stack trace does not match the cause of the issue. This appears to be related to the build script as even a non-swingame code compiled with that script fails to provide the correct stack trace.
Values from the stack trace should be able to be used with gbd to get line information.
Script to get line info follows. It requires the user to paste in the stack trace:
The text was updated successfully, but these errors were encountered: