Open
Conversation
Owner
|
Iirc there's a problem when using :: where ghidra doesn't automatically namespace it into classes properly from a script like it does if you rename it manually in the ide |
Owner
Owner
|
Hm.. annoyingly it seems ghidras type libraries don't support namespaces |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Currently looking into a PS3 binary with debug symbols and was playing around with various tools.
Noticed the Ghidra demangler was breaking things. It produced a lot of '.' resolutions when there should not be any dots, and duplicate placeholder data types in the data type manager created by the demangler -> turned it off and wanted to add my NIDs to the base list.
I used a "particular" reference command line tool which spat out these demangled forms, if you are interested.