Decompilation broken for MIPS:BE:32:default
See original GitHub issueDescribe the bug
Decompilation fails with error
Low-level Error: Could not find op at target address:
To Reproduce
- have MIPS:BE:32:default asm
- opcodes clearly gets disassembled
- functions are found, but
- on decompilation it fails with above mentioned message
Screenshots
Environment:
- OS: Win7
- Java Version: 12.0.2
- Ghidra Version: 9.1-BETA
Additional context I have developed a loader for N64 Roms and want to upgrade it for ghidra 9.1 (the code in that repo was already upgraded for 9.1 but the dist was left for 9.0.4)
Issue Analytics
- State:
- Created 4 years ago
- Comments:14 (5 by maintainers)
Top Results From Across the Web
Is Ghidra's decompilation of ARMv7 strb.w instruction broken?
Now, I have two questions: The decompiled function suggests that this memset function will not set the given address (addr) to the specified ......
Read more >Decompile .NET code while debugging - Visual Studio ...
Generate and embed source code from .NET assemblies while debugging in Visual Studio. Extract and view the embedded source code.
Read more >decompiler broken? : r/SynapseX - Reddit
Does the decompiler fr still not work properly or is it broken again. I'm getting empty output on small scripts and modules even...
Read more >dotPeek: Free .NET Decompiler & Assembly Browser by ...
dotPeek is a free tool based on ReSharper. It can reliably decompile any .NET assembly into C# or IL code.
Read more >eclipse - Java decompiler plugin not working - Stack Overflow
For Eclipse 2018-09 , the problem was related to " class without source ". I had resolved this issue by going to:.
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
Agreed. The overlay issue is a regression related to system call override changes, it is being diagnosed and will be fixed before release.
Fixed by bf4a17b67dff93b6a2555ceb4eed9ba85d019e05