Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate issues with Pascal stack trace #18

Open
macite opened this issue Oct 8, 2013 · 0 comments
Open

Investigate issues with Pascal stack trace #18

macite opened this issue Oct 8, 2013 · 0 comments
Labels

Comments

@macite
Copy link
Owner

macite commented Oct 8, 2013

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant