CorePluginInit() called twice when the debugger is used as a user plugin
Open
Nobody has claimed this yet.
binaryninja
bug
Impact: Low
- Dominant language
- C++
- Stars
- 331
- Forks
- 33
- PR merge metrics
- No merged PRs in 30d
Description
I get the following warning message when I try to use the debugger plugin as a user plugin. I have already turned off corePlugins.debugger so the debugger that comes with Binary Ninja is not loaded.
Setting: debugger.stopAtSystemEntryPoint already registered!
Setting: debugger.stopAtEntryPoint already registered!
Setting: debugger.stackVariableAnnotations already registered!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the user-plugin configuration with corePlugins.debugger disabled and trace where CorePluginInit() is called. Done means the debugger can load as a user plugin without duplicate-setting warnings for the listed debugger settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- reverse-engineering
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100