VirtualBox

Ticket #477 (new defect)

Opened 1 year ago

Last modified 3 weeks ago

Hardware breakpoints don't work in Virtualbox

Reported by: marius_mtm Assigned to:
Priority: major Component: VMM
Version: VirtualBox 2.0.2 Keywords: hardware breakpoints
Cc: Guest type: other
Host type: other

Description

It seems that doesn't work setting hardware breakpoints in Virtualbox (Olly Debugger). [Hardware, on Execution] WinXP guest

Change History

(follow-up: ↓ 5 ) 05/25/08 16:49:50 changed by sandervl73

Being worked on at the moment, but will not show up until after 1.6.2.

05/25/08 16:49:59 changed by sandervl73

  • version changed from VirtualBox 1.4.0 to VirtualBox 1.6.0.

05/25/08 16:50:20 changed by sandervl73

  • priority changed from major to critical.
  • summary changed from Hardware breakpoints doesn't work in Virtualbox to Hardware breakpoints don't work in Virtualbox.

07/10/08 08:30:43 changed by frank

  • owner changed.
  • component changed from other to VMM.

(in reply to: ↑ 1 ) 08/06/08 16:36:31 changed by marius_mtm

Replying to sandervl73:

Being worked on at the moment, but will not show up until after 1.6.2.

Anything on this? Doesn't work in 1.6.4 Thx.

09/09/08 22:00:28 changed by zashone

hi guys , virtualbox is the more user friendly virtual machine , for use , configuration and installation under linux. but with that lack you disappoint all a community of driver developers and reverse engineers.we are waiting for this more than one year now !!!!!

09/09/08 22:08:31 changed by frank

Yelling loud any writing dozens of exclamation marks does not help. Where did you attach the patch to fix that bug? The VirtualBox source code is freely available.

09/16/08 14:45:35 changed by Tim Sobolev

Here are files for testing this issue

Where did you attach the patch to fix that bug? The VirtualBox source code is freely available.

Not everyone can spend enough time to explore the source of VirtualBox to fix that bug. So many of them choose VMware instead VirtualBox solely because of this problem.

09/16/08 20:38:01 changed by sandervl73

I've implemented it for VT-x and AMD-V, but haven't had time to test it yet. Hopefully later this week.

09/18/08 17:55:44 changed by sandervl73

  • priority changed from critical to major.
  • version changed from VirtualBox 1.6.0 to VirtualBox 2.0.2.

Successfully tested with windbg (kernel debugging session). Code is already in SVN.

(in reply to: ↑ description ) 10/22/08 10:09:05 changed by stephanecharette

Replying to marius_mtm:

It seems that doesn't work setting hardware breakpoints in Virtualbox (Olly Debugger).

What does "don't work" means? I'm trying to figure out if this is the same problem I'm seeing.

With ddd/gdb, when it hits a breakpoint it (sometimes? always?) causes the host and guest to lock hard. System completely locks up. Cannot CTRL+ALT+DEL, must physically reboot the entire system.

I'm attempting to debug a simple C++ app on my Debian Etch-64bit guest. Host is Ubuntu 8.04-64bit. VB is 2.0.2.

(follow-ups: ↓ 13 ↓ 14 ) 10/22/08 12:42:31 changed by frank

Anyway, the problem is fixed with the next major release (2.1, not 2.0.4).

(in reply to: ↑ 12 ) 10/22/08 18:02:20 changed by stephanecharette

Replying to frank:

Anyway, the problem is fixed with the next major release (2.1, not 2.0.4).

That's just the things -- this problem, or a different one that I'm seeing? At this point I cannot confirm whether or not the problem I'm seeing is the same thing, or something else.

(in reply to: ↑ 12 ) 10/27/08 22:02:46 changed by stephanecharette

Replying to frank:

Anyway, the problem is fixed with the next major release (2.1, not 2.0.4).

This is causing me lots of pain. (The inability to debug my C++ applications.) Do we know approximately when VB 2.1 is scheduled to be released? Or is there a workaround that can be applied to VB 2.0.4?

© 2008 Sun Microsystems, Inc.
Contact – Privacy policy