You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Ghidra uses pattern files e.g. Ghidra/Processors/x86/data/patterns/x86gcc_patterns.xml to aid autoanalysis - in particular, when searching for functions and code.
Some binaries will have different patterns (typically due to the use of an unusual compiler). It is undesirable to replace/modify the (usually sensible) default pattern file directly, as all other binaries on the same architecture will use it.
Describe the solution you'd like
An easy way to edit the pattern file in use for a given binary. One way this could work is to make a copy of the default xml (and maybe even the SLEIGH files?) into the workspace folder, together with an easy way from the UI/API to find these files.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Ghidra uses pattern files e.g.
Ghidra/Processors/x86/data/patterns/x86gcc_patterns.xml
to aid autoanalysis - in particular, when searching for functions and code.Some binaries will have different patterns (typically due to the use of an unusual compiler). It is undesirable to replace/modify the (usually sensible) default pattern file directly, as all other binaries on the same architecture will use it.
Describe the solution you'd like
An easy way to edit the pattern file in use for a given binary. One way this could work is to make a copy of the default xml (and maybe even the SLEIGH files?) into the workspace folder, together with an easy way from the UI/API to find these files.
The text was updated successfully, but these errors were encountered: