Open devingDev opened 1 week ago
Unfortunetly, when a DB corruption occurs there is no way to identify the cause or correct the DB state. It is also difficult to identify the point in time when the corruption occured. You could try to examine your log files for stacktraces caused by severe errors such as out-of-memory exceptions which can have unpredictable consequences.
Describe the bug I was renaming some symbols, parameters and function signatures, then i check-in and reopened the code browser but it gave me this error message each time. I even deleted the last "commit" and checked out and it still gives me this error. Restarting ghidra does not help either. Code browser is also just empty then.
Screenshots
Environment (please complete the following information):
Build Date: 2024-Jul-09 1157 EDT Ghidra Version: 11.1.2 Java Home: C:\Program Files\Eclipse Adoptium\jdk-21.0.3.9-hotspot JVM Version: Eclipse Adoptium 21.0.3 OS: Windows 10 10.0 amd64
Additional context We are using a shared project, so I'm not sure where this went wrong.
I'm not sure what other info I can give or you need but I will try my best to do so.