Page 1 of 1

.pgmphystofile error message

Posted: 28. Dec 2013, 09:28
by flyone
I tried to go into the virtualbox debug mode to dump the physical memory. I can get into the debug mode. However, when I type in

.pgmphystofile <filename>

to dump the physical memory. It has the following error message.

VBoxDbg> .pgmphystofile memory.raw
pgmphystofile: parser error: iArg=0 iLine=3870 pszExpr=paArgs[0].enmType != DBGCVAR_TYPE_STRING

Does anyone ever see that? Thank you.

Re: .pgmphystofile error message

Posted: 17. Sep 2014, 01:58
by Nullsec
Hi, im experiencing a very similar error. Tried several different Windows 7 VM's.

VBoxDbg> .pgmphystofile memory.raw
pgmphystofile: parser error: iArg=0 iLine=3871 pszExpr=paArgs[0].enmType != DBGCVAR_TYPE_STRING

There is no solution or documentation anywhere, I have searched google. Can somebody here please help ?

Re: .pgmphystofile error message

Posted: 28. Dec 2014, 19:59
by frznn
Same problem here. Any help?

Re: .pgmphystofile error message

Posted: 30. Dec 2014, 10:50
by mpack
Moved to "VirtualBox API".

Re: .pgmphystofile error message

Posted: 7. Jan 2015, 12:38
by noteirak
I would strongly suggest to ask this question in the Dev Mailing list. This is a bit too advanced question for the forum and you would require direct chat with the devs.

Re: .pgmphystofile error message

Posted: 28. Apr 2015, 12:06
by frznn
I think i found the problem in the command implementation code.
In file "src/VBox/VMM/VMMR3/PGM.cpp" at line 3871:

Code: Select all

 DBGC_CMDHLP_ASSERT_PARSER_RET(pCmdHlp, pCmd, 0, paArgs[0].enmType != DBGCVAR_TYPE_STRING); 
the assert condition is wrong, since it checks the argument to be different from a string, while it should be a string.
Hence the the '!=' should be a '=='.
Same applies to the assert for the second argument, at line 3874:

Code: Select all

DBGC_CMDHLP_ASSERT_PARSER_RET(pCmdHlp, pCmd, 1, paArgs[2].enmType != DBGCVAR_TYPE_STRING);
Would anyone fix this, please?

Re: .pgmphystofile error message

Posted: 29. Apr 2015, 10:13
by frank
Fixed. Thank you for the report!