I'm having trouble debugging a win32 executable file under Windows 7. I've tried using ollyDbg and x64dbg: the former simply does nothing, while the latter complains with an Error starting process (invalid pe?)! message.I think this might have to do with the fact that said executable is digitally signed. I did some quick research and this SO question came up, where I learned that digital signatures in windows executables are referenced in the file's PE header, which I think might be what x64dbg was complaining about.The executable I'm talking about is the Mumble windows client version 1.2.10.It is the only executable signed with two different digital signatures, which further reinforces my hypothesis.Sadly, even after stripping the digital signatures using the delcert.exe linked in the SO question above, the problem remains which brings me to a dead end.Is it possible digital signatures are messing these debuggers up? Is it possible that the signature stripping tool doesn't produce a valid pe file for the debuggers I tried? What else could I be doing wrong?As a footnote: I know mumble is free software and I could just compile my own version, but this is Reverse Engineering, right?Update: Following Jason comment, I'm posting the ollydbg log, which doesn't really say anything, unfortunately:Log dataAddress    MessageOllyDbg v1.10Bookmarks sample plugin v1.06 (plugin demo)  Copyright (C) 2001, 2002 Oleh YuschukCommand line plugin v1.10  Written by Oleh YuschukFile 'C:\Program Files (x86)\Mumble\mumble.exe'
Debugging digitally signed executable
windows;debugging;pe