-
when i change the struct definition, function decompilation still remembers old definition and using them. reanalyzing function or entire database does not help, i have to reapply the type to update decompilation 2025-09-05.10-35-42_edit.mp4is there a way to somehow refresh all decompilations in the database? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
Just out of curiosity, have you been using the 'propagate forward' feature ('q' by default) on functions? What you're describing sounds like an issue that arises when variables are given types with bare structs rather than a NamedTypeReference, and using the bare struct means that the type in the variable won't be updated when the version in the types list is. (Digging into this would require some interaction with the Python console, it's visually hard to distinguish from screenshots alone, but 'reapplying' the type like you've described would be forcing it back to a NamedTypeReference making all the update propagation stuff work again) |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
Just out of curiosity, have you been using the 'propagate forward' feature ('q' by default) on functions?
What you're describing sounds like an issue that arises when variables are given types with bare structs rather than a NamedTypeReference, and using the bare struct means that the type in the variable won't be updated when the version in the types list is. (Digging into this would require some interaction with the Python console, it's visually hard to distinguish from screenshots alone, but 'reapplying' the type like you've described would be forcing it back to a NamedTypeReference making all the update propagation stuff work again)