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

pdb file not generated #17

Open
lufatatako opened this issue Jun 13, 2021 · 12 comments
Open

pdb file not generated #17

lufatatako opened this issue Jun 13, 2021 · 12 comments
Labels

Comments

@lufatatako
Copy link

I'm using IDA 7.6, to generate pdb of an executable but it is just creating the json only.
I have tried to create using fakepdb.exe also but that also doesn't works

please help with this issue
thanks

@Lectem
Copy link

Lectem commented Jul 3, 2021

Same issue here, but with IDA 7.5.
Is there some kind of logging I could enable to know what goes wrong ?
The only thing in my output is the following

FakePDB/generate pdb:
    * generating JSON: PathToMyDll.dll.json
    * generating PDB: PathToMyDll.pdb
    * symserv EXE id: b''
    * symserv PDB id: b''
    * done

@Lectem
Copy link

Lectem commented Jul 3, 2021

I managed to make it work by specifying the exe path myself.
It seems that the tool expects the exe/dll to still be in the same place as it was when the IDA database was created (see
https://github.com/Mixaill/FakePDB/blob/master/src_plugins/ida/fakepdb/command_pdbgenerate.py#L65), which might not be the case if you share the database with someone (you might even not have the executable file at all).
Is the executable file mandatory to generate a .pdb ?

@Mixaill
Copy link
Owner

Mixaill commented Jul 3, 2021

Yes, currently it is mandatory, will be fixed in the upcoming release

@GflowerG
Copy link

+1

ida 7.6 + v0.3 = not generated.
ida 7.4 + v0.2 = ok.

@sunbeam906
Copy link

sunbeam906 commented Aug 9, 2021

I can confirm the same for DLL files. Uploaded the target here: cshell.zip.

Using IDA 7.5 SP3 with 0.3. If I try the plugin/tool on an executable for which I've properly adjusted the Debug Directory, it works fine. The tool extracts automatically the RSDS info (GUID, Age) and properly writes the .pdb file to disk, matching it to the .exe information.

If I do it for the DLL I attached above, also with Debug Directory adjusted so it's readable by FakePDB, it returns the same result as lufatatako's above:

* symserv EXE id: b''
* symserv PDB id: b''

And no .pdb generated on disk. Just the JSON.

The paths are fine, as IDA shows this:

image

Suggestions? Thanks!

@Mixaill
Copy link
Owner

Mixaill commented Aug 25, 2021

Should be possible with the latest master

fakepdb_6356b3.zip

@GflowerG
Copy link

Should be possible with the latest master

fakepdb_6356b3.zip

I still have only json file generated :(

@Mixaill
Copy link
Owner

Mixaill commented Aug 26, 2021

Can you provide your .idb /.i64 file? ( [email protected] or Mixaill#1085 in Discord)

@sunbeam906
Copy link

sunbeam906 commented Aug 26, 2021

Can you provide your .idb /.i64 file? ( [email protected] or Mixaill#1085 in Discord)

I've also sent you a Discord invite :) Thanks, will produce the file and send over. In my case, it's a DLL and small.

P.S.: Here's my file (x86 DLL) + .idb (IDA 7.5 SP3) -> NOLF.zip

I've manually added the debug information to the DLL (Debug DIrectory, RSDS header, etc.). So it's all there:

Clipboard00

Clipboard01

Clipboard02

@xNxExOx
Copy link

xNxExOx commented Jun 3, 2022

hello, for me the pdb is also not generated, and no error is printed I tried to message @Mixaill on discord, but no response so far, so I am writing also here

@SoulXHades
Copy link

My quick fix based on v0.3 for those who are interested. https://github.com/SoulXHades/FakePDB/releases/tag/v0.3.1

@sunbeam906
Copy link

My quick fix based on v0.3 for those who are interested. https://github.com/SoulXHades/FakePDB/releases/tag/v0.3.1

Thank you for taking the time to look into this! Much appreciated!

P.S.: Oh, there are several of us still monitoring this ;)

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

No branches or pull requests

7 participants