Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot open projects #69

Open
Kneesnap opened this issue May 21, 2023 · 8 comments
Open

Cannot open projects #69

Kneesnap opened this issue May 21, 2023 · 8 comments

Comments

@Kneesnap
Copy link

I have a project which contains between 50-100 executables. Most of the executables are different versions of a particular PSX game, the others are Windows builds, related tools, etc.
Unfortunately, ghidra had a hard crash a little while ago. I thought everything was fine since most of the projects I had seemed perfectly fine. Unfortunately it took a while to realize that none of the PSX executables load anymore.

Here's what happens when I try to open it in Ghidra.
Example

This is strange because I have the plugin installed and enabled just fine. In fact, if I add a new PSX executable to the project, it still works perfectly!

However, I notice that the new ones seem to have their processor listed as "MIPS" instead of "PSX". I'm not sure I understand why that is.

I am using Ghidra 10.1.1, with ghidra_10.1.1_PUBLIC_20220123_ghidra_psx_ldr.zip (outdated since that's what I started this project with). Unfortunately, I need to recover these projects since some of them are incredibly well documented in terms of structs, functions, etc. What are my options for recovering from this?

@nicolasnoble
Copy link
Collaborator

The PSX:LE:32:default processor language should be provided by the plugin, so it'd really mean it's not installed properly.

You could always kludge by changing the following file in your Ghidra installation: Ghidra/Processors/MIPS/data/languages/mips.ldefs. The MIPS:LE:32:default definition on top can either be copied or renamed to PSX:LE:32:default. I'd highly advise to backup your databases first however prior to opening it with this kludge.

You'll lose some of the specific opcodes from the GTE.

@Kneesnap
Copy link
Author

Hmm, how would I fix the broken installation? I'd hope to fix it that way.

@lab313ru
Copy link
Owner

You can try to change your project language in properties.

@Kneesnap
Copy link
Author

You can try to change your project language in properties.

I did try that, but it would error that it couldn't open the project (Presumably because of the LanguageNotFoundException)

@nicolasnoble
Copy link
Collaborator

You can try to change your project language in properties.

You can't, as ghidra will search for the PSX:LE:32:default one which doesn't exist, and throws an exception. It's a bit bad.

@nicolasnoble
Copy link
Collaborator

Hmm, how would I fix the broken installation? I'd hope to fix it that way.

Maybe try uninstalling / reinstalling the extension ?

@lab313ru
Copy link
Owner

You can send me one of your projects in a private way ([email protected]), I'll try to do something.

@Kneesnap
Copy link
Author

Kneesnap commented May 22, 2023 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants