Ticket #7020 (closed defect: invalid)

Opened 9 years ago

Last modified 9 years ago

Assertion failed while executing shell-script by "VBoxManage guestcontrol execute" command

Reported by: upokatik Owned by:
Component: VM control Version: VirtualBox 3.2.4
Keywords: Cc:
Guest type: other Host type: other


I use VirtualBox 3.2.4 installed on Microsoft Windows 7 host system and work under Mandriva 2010 Linux guest system with VBoxGuestAdditions3.2.4 installed. In Mandriva guest I have a self-created simple shell-script /home/user/ with the following contents:


And when I try to run that script by executing VBoxManage guestcontrol execute command, I get an "Assertion Failed" message:

C:\Users\DIM>VBoxManage --nologo guestcontrol execute "Mandriva2010" "/home/user/" --username user --verbose --wait-for stdout
Waiting for guest to start process ...
Process '/home/user/' (PID: 3033) started
Waiting for process to exit ...

!!Assertion Failed!!
Expression: <none>
Location  : /mnt/tinderbox/add-3.2/src/VBox/Runtime/r3/posix/process-posix.cpp(396) int RTProcCreateEx(const char*, const char* const*, RTENVINTERNAL*, unsigned
 int, const RTHANDLE*, const RTHANDLE*, const RTHANDLE*, const char*, const char*, RTPROCESS*)
execve returns -1 errno=8

Process error details:
ERROR: Process terminated via signal with status '5'
Details: code E_FAIL (0x80004005), component Guest, interface IGuest, callee

Exit code=5 (Status=3 [terminated by signal], Flags=0)

Script /home/user/ works fine if I execute it under Mandriva guest system.

Also, if I pass /bin/ls instead of /home/user/ as a <pathToProgram> parameter of VBoxManage guestcontrol execute command, it works correctly.


VBox.log Download (48.5 KB) - added by upokatik 9 years ago.

Change History

Changed 9 years ago by upokatik

comment:1 Changed 9 years ago by frank

  • Status changed from new to closed
  • Resolution set to invalid

That assertion means that the binary format cannot be properly parsed. This will work if you insert


at the top of your shell script. Though we should improve the error message.

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use