![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Given several .dll/.sys files, and their respective .pdb/.dbg files, is there any way to get a reasonable assembly dump with symbols and function blocks of said files, in Linux?
objdump doesn't read .dbg/.pdb files :-(.
The compiler used was "Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 12.00.8799.0" - gleaned by running strings on the .pdb.
I see that IDA Pro can do it, but I don't have access to IDA, hence I'm looking for a Linux route.
Failing that, does somebody have the internal file format for the .pdb debug files?
(Not to be confused with .pdb palm databases or .pdb protein databases).
Edit: Wine was suggested, and winedbg in particular, but it crashes and burns quite specactullarly on the .sys, and won't even open the .dll - secondly it doesn't even open the .pdb files :-(. Also winedump doesn't handle .pdb debug data it seems.
objdump doesn't read .dbg/.pdb files :-(.
The compiler used was "Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 12.00.8799.0" - gleaned by running strings on the .pdb.
I see that IDA Pro can do it, but I don't have access to IDA, hence I'm looking for a Linux route.
Failing that, does somebody have the internal file format for the .pdb debug files?
(Not to be confused with .pdb palm databases or .pdb protein databases).
Edit: Wine was suggested, and winedbg in particular, but it crashes and burns quite specactullarly on the .sys, and won't even open the .dll - secondly it doesn't even open the .pdb files :-(. Also winedump doesn't handle .pdb debug data it seems.
