Skip to content

Handle string values in the gdb registers output#37

Open
IddoPuff wants to merge 9 commits intoanfedotoff:masterfrom
IddoPuff:bug/handle-invalid-register-value
Open

Handle string values in the gdb registers output#37
IddoPuff wants to merge 9 commits intoanfedotoff:masterfrom
IddoPuff:bug/handle-invalid-register-value

Conversation

@IddoPuff
Copy link
Copy Markdown

previously causing crash, now ignoring specific register

Fixes #36

previously causing crash, now ignoring specific register
Comment thread src/registers.rs
Comment thread src/registers.rs Outdated
@anfedotoff
Copy link
Copy Markdown
Owner

anfedotoff commented Apr 13, 2026

Can you, please:

  1. Fix test_stacktrace_structs, it's seems to me, that offset of the compiled binary has changed. You can just compile localy to know the value and than just hardcode it in test .
  2. Squash+rebase some commits. Commit for clippy fixes, you actual fix for library, and tests fix.

@IddoPuff
Copy link
Copy Markdown
Author

OK, I think that the stacktrace_structs and memory test are very flimsy since the addresses will change each compilation, and the stack trace can contain different functions in different versions of gcc. I will think of a more reliable test

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Invalid register values in modern GDB

2 participants