Plugin doesn't appear in Configure->Experimental Plugins
See original GitHub issueThe extension (v10.0.3) downloaded from release, is added and checked in the list of installed extensions.
In the Code Browser, however, going to Configure -> Experimental, ClassTypeInfoManagerPlugin
isn’t showing up.
Ghidra v10.0.3 PUBLIC on Windows 10
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Installation: Can't find plugin in experimental-configure #21
Ghidra: 9.1.2 OS: Windows10 I have extract archive to folder in Ghidra/Extensions/Ghidra Click the + icon But I can't find ...
Read more >How to Fix FL Studio plugins not showing up - YouTube
How to Fix FL Studio plugins not showing upYou add a new plugin to your system. Open up FL Studio and expect it...
Read more >Using Plugins - QGIS Tutorials and Tips
Open Plugin Manager by Plugins ‣ Manage and Install Plugins…. Click on the Settings tab. You will see an option called Show also...
Read more >Dalamud FAQ | faq
How do I install/enable plugins? How do I enable plugin test builds? What is the command for <insert plugin here>? How do I...
Read more >QGIS 3.2.2 OpenLayers plugin isn't listed to install
You need to check Show also experimental plugin from the Plugin manager -> Settings because OpenLayers Plugin is listed under experimental ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
That worked, Ghidra seems to have extracted it using the archive name, discarding the root folder, instead of extracting as is.
Thank you very much for your help. 👍
Thank you. Yes, that looks very suspicious indeed. I will take a look at the log after work this afternoon.
Umm. I’m not sure if it even matters or why it ended up being named that way but try changing the folder name in Extensions from
ghidra_10.0.3_PUBLIC_20210909_Ghidra-Cpp-Class-Analyzer
toGhidra-Cpp-Class-Analyzer
. If that does fix it I’d like a bug report to be opened in the Ghidra repo especially if it was extracted automatically by the plugin installer ui.