VMProtect Software » Forum

Recently we bought vmprotect for our released product, And we have automatically dump processor in our server. Now the processor can not give right analysis result.
I have tried MiniDumpFixer. With right exe and dmp file, it prints:
"DMP file sucessfully updated."
But nothing has changed in our dump file.
I can not figure out why.

The more detail information about MiniDumpFixer sent to your e-mail.

I have the same cases when using Minidumpfixer.exe
After type the command with dump and exe file, it return"DMP file sucessfully updated."
but, nothing changed with the dump file.

Would you mind tell me what I am missing?

derekfung wrote:Would you mind tell me what I am missing?

That's probably an our miss, we have finally reproduced the issue and will try to fix it soon.

Sorry

Thank you!

Hi, I have the same issue as is posted above. I have a .pdb file (from the pre-VMProtected file), a minidump file (generated from the program.vmp.exe), and the program.vmp.exe file. Of course, when i try to open the minidump file, Visual Studio tells me there is no debug information available.

I understood that minidumpfixer would solve this problem. Is that correct?

If yes, why won't it work after the utility runs and reports success?

thanks
stevo9876

Minidumpfixer fixes an image size in DMP file for loading unprotected file in Visual Studio. Notice that names of protected and unprotected files must be same.

Here is my procedure:

1) build application that contains VMProtectBegin, VMProtectEnd, and VMProtect functions
2) open newly built app in VMProtect console, click Compilation button
3) share protected executable with customer
4) customer has a crash - they send their mini dump file
5) mini dump, protected exe (renamed as original file), original pdb file all collected together.
6) minidumpfixer dumpfile executable
reports success
7) open mini dump in Visual studio
** No debug information can be found for executable


Can anyone comment on what I can do to allow debugging using Visual Studio, the minidump file and the .pdb file?

thanks,
stevo9876

5) mini dump, protected exe (renamed as original file), original pdb file all collected together.

Do you want to debug the protected file?

I do wish to apply the same debugging strategy that I currently employ, that is using the generated minidump file to assist in the problem determination.

If this isn't the typical method of debugging post VMProtect, is there an existing best practice that I can turn to?

thanks,
stevo9876

Please read the MiniDumpFixer description:
Here’s a little nifty tool that allows you to fix minidump files, so they can be loaded with the unprotected file to a debugger. Protection changes file parameters, so debugger can’t match the minidump file to the executable one, so crash dump debugging becomes a pain. Now you can do that with ease using the MiniDumpFixer tool.

Yes, I see that I misread the instructions. Here is my working procedure:

1) build application that contains VMProtectBegin, VMProtectEnd, and VMProtect functions
2) open newly built app in VMProtect console, click Compilation button
3) share protected executable with customer
4) customer has a crash - they send their mini dump file
5) mini dump, original executable file (not protected), original pdb file all collected together.
6) minidumpfixer dumpfile executable
reports success
7) open mini dump in Visual studio

Thanks for your patience and your assistance!
stevo9876