-
Notifications
You must be signed in to change notification settings - Fork 56
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
Possible way around for 7.4+ versions #29
Comments
This works for me, thanks! Not sure what happened between 0.2 and 0.3 but using the older version I was able to get a PDB where the newer one would only produce a JSON. Having the same problem on the latest commit too. |
I present to you the actual solution: In IDA scripting window: import ida_nalt
ida_nalt.set_root_filename('E:\\new\\path\\to\\your\\analysedfile.dll') You may also check current path with: ida_nalt.get_input_file_path() This is the difference between 0.2 and 0.3, currently FakePDB uses But the current behavior causes things to break if you move the executable somewhere else, while IDA still thinks it's at the old location. After changing it, it works again. |
Played around with different versions of fakepdb and could finally make an .pdb file. I'm using IDA PRO 7.7
Steps:
worked like a charm, got pdb,VS recognized functions
The text was updated successfully, but these errors were encountered: