-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Impossibility to parse C type #4624
Comments
I figured out that after registering a type the parsing wasn't working anymore but If I add all the types I want to add in the same |
I think this is an angr bug, but I can't reproduce it from the snippets you've posted. Can you post a) the output of |
a)
b) I think this is due to the running environment that is a docker. If I try to run the same things outside of it is working well. I don't really know how the docker env is set up. |
Can you give me the image name (is it just angr:latest?) and the script to run inside the container? |
the image is a custom one provided by one the people I work with. I am not sure I am allowed to share it. The script that is run is very few lines:
trustdymbex is the name of my python program. $TARGET is the binary. |
Description
For a project I have to add new types.
I add a first types like this:
I need to add a second type that look like this:
So a very similar element and for some reason I cannot parse the type. I get the following backtrace:
And If I try to replace the second parsing by the exact same as the first one. I get the same error I don't understand what is going on. Either it's a bug in how things are parsed either I made a mistake.
Steps to reproduce the bug
No response
Environment
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: