[vbox-dev] VM-debugger status
ramshankar.venkataraman at oracle.com
Tue Dec 10 03:42:47 UTC 2019
The VM debugger should work in principle but there may be bugs that may
be specific to CPU hardware features.
The ticket you pointed to for instance,
(https://www.virtualbox.org/ticket/17348) does not provide sufficient info.
The best way to get a problem solved is by giving us a VBox.log and the
simplest, smallest reproducible test-case on how to trigger the issue.
Here is what I usually use: "ba x 1 <cs:rip-address>" That sets a
breakpoint at the cs:rip you need to break at. Once the breakpoint
triggers, you can single step using "t" (trace) or continue
guest-execution using "g" (go).
On 04/12/19 9:20 PM, felix nasch wrote:
> I am wondering what the status of the VM-Debugger is.
> I am unable to make it work on a Linux host, regardless of the guest OS.
> A quick search shows that people in the forums and on trac have
> the same problem: The VM can only be paused and resumed, but no
> breakpoints or stepping requests are respected.
> Both the thread in the forum and the bug tracker have received no reply.
> Has the VM-Debugger been deprecated?
> Or should it still work in principle?
>  https://www.virtualbox.org/manual/ch12.html#ts_debugger
>  https://forums.virtualbox.org/viewtopic.php?t=78370
>  https://www.virtualbox.org/ticket/17348
> vbox-dev mailing list
> vbox-dev at virtualbox.org
More information about the vbox-dev