Segfault when passing UTF8 character on VBoxManage controlvm option => Fixed in SVN

[Macedo]

Minor argument parsing issue.

While executing some operations on a stopped VM with my keyboard set to PT-BR on an Ubuntu host (generating dual-byte special characters), VBoxManage returned a segfault when receiving an option which was wrongly written with such character.

Attached are:

• The VBoxManage core file

• A text/shell file with the garbled option.

I did not try to reproduce the event with other options than the used on the sample provided.

It's not a show stopper but I hope this information can help VB team to improve the argument parsing to avoid something worst on another place.

[Macedo]

Text file with command able to cause the error.

[Macedo]

I couldn't upload the 2.8MB core file to the bugtrack.

If considered really necessary (shouldn't be, because the error is reproductible easily enough), I can add it splitted on smaller parts.

Please let me know.

[Frank Mehnert]

Thanks, I think an upload of the core dump shouldn't be necessary, I hope we can reproduce the crash.

[Frank Mehnert]

Actually I can NOT reproduce this problem. VBoxManage reports unknown option. Are you sure this was VBox 3.2.8?

[Macedo]

Yes, I'm sure.

Just to clarify the setup (what I wrote on the description doesn't match 100% the scenario and may be the reason you couldn't reproduce the problem):

• Host where the VirtualBox was running: Centos with UTF8 disabled (LANG=C)
• Management station: Ubuntu with LANG=en_US.UTF-8

I opened a gnome terminal on the ubuntu station, ssh'd to the VBox host and there typed the VBoxManage command that caused the error.

Anyway, here's a link to the VBoxManage core.

​http://hiangel.tmp.com.br/VBoxManage.core.bz2

Thanks for the attention.

[Frank Mehnert]

Thanks, LC_ALL=C was the missing bit. I finally was able to reproduce this problem.

[Frank Mehnert]

Finally fixed in SVN. The fix will also be included in the next maintenance release.