VirtualBox

Opened 10 years ago

Closed 4 years ago

#12636 closed defect (fixed)

Delphi/RAD Studio debugger unusable => Fixed in SVN

Reported by: Serge Kraikov Owned by:
Component: other Version: VirtualBox 4.3.6
Keywords: radstudio delphi debugger Cc:
Guest type: Windows Host type: Linux

Description

After updating from 4.2.18 to 4.3 the built-in debugger on RAD Studio does not step over/step into, it stays on the breakpoint line constantly.

I reproduced this issue in 4.3.2, 4.3.4 and in the latest 4.3.6 (these are the all 4.3.x versions I tested).

I encountered this issue on all XE, XE2, XE3, XE4 and XE5 versions of the RAD Studio (other users encountered this issue on Delphi7 also). There is a free trial version of affected RAD Studio XE5 on embarcadero.com site.

I run ArchLinux x64.

After downgrading to 4.2.18 this issue disappears.

Attachments (2)

VBox.log.zip (22.4 KB ) - added by Serge Kraikov 10 years ago.
VBox.log.zip
VBox.log.2.zip (21.8 KB ) - added by ksc654 10 years ago.

Download all attachments as: .zip

Change History (19)

by Serge Kraikov, 10 years ago

Attachment: VBox.log.zip added

VBox.log.zip

comment:1 by Serge Kraikov, 10 years ago

There is a forum thread about this issue: https://forums.virtualbox.org/viewtopic.php?f=7&t=59137

comment:2 by Petr Vones, 10 years ago

Note there was issue with Visual Studio debugger #9659 that did not work in 4.2 versions but it was fixed in 4.3.

Last edited 10 years ago by Petr Vones (previous) (diff)

comment:3 by DeveloperDave, 10 years ago

Still an issue as at 4.3.8.r92456 - affects my Delphi 5, 7, XE5

comment:4 by Ramshankar Venkataraman, 10 years ago

There were some fixes to pending debug exceptions, stepping over IO instructions on Intel VT-x which didn't make it into 4.3.8.

Could you please if the following 4.3.9 test build helps the problem?

Windows host

Linux (64-bit) host

(Links expire in ~14 days).

comment:5 by DeveloperDave, 10 years ago

Tested OK (Thanks!)

Host: Windows 7 (intel Core 2 Duo)

VMS and Delphi versions tested are shown below

Windows 8 VM

Embarcardero Delphi XE5

Windows 7 VM

Delphi 5
Delphi 7
Embarcadero RAD Studio XE2
Embarcadero RAD Studio XE4

Windows Server 2003 VM

Delphi 5
Delphi 7
Delphi 2009
Delphi XE

comment:6 by Ramshankar Venkataraman, 10 years ago

So does it fix the problem you have?

comment:7 by DeveloperDave, 10 years ago

Yes. Fixed. (as noted in the VM / Delphi versions I have above)

Last edited 10 years ago by DeveloperDave (previous) (diff)

comment:8 by Ramshankar Venkataraman, 10 years ago

Summary: Delphi/RAD Studio debugger unusableDelphi/RAD Studio debugger unusable => Fixed in SVN

Thanks for testing, the fix will be available in the next maintenance release (4.3.10).

comment:9 by ksc654, 10 years ago

Experiencing the same problem after upgrading to test build 4.3.9 r92672.

I'm running Windows 7 on host and guest. Version of RAD Studio is Delphi 2010.

by ksc654, 10 years ago

Attachment: VBox.log.2.zip added

comment:10 by Ramshankar Venkataraman, 10 years ago

The other reporter claims Delphi 2009 works. Is this Delphi 2010 RAD Studio free to download and test?

It would save time if I can get a direct download link as well as a testcase to try out.

comment:11 by ksc654, 10 years ago

Unfortunately no. Only the most recent version is available as a trial. For now I've downgraded to 4.2.22.

comment:12 by Frank Mehnert, 10 years ago

Fix is part of VBox 4.3.10.

comment:13 by Serge Kraikov, 10 years ago

I confirm this issue is fixed in v4.3.10, thank you.
Tested ArchLinux x64 host with Windows 7 x86 guests and RAD Studio XE5 and XE4.

comment:14 by Frank Mehnert, 10 years ago

Resolution: fixed
Status: newclosed

ksc654, still this problem with VBox 4.3.12? In that case, please reopen and add a new VBox.log file with VBox 4.3.12.

comment:15 by gvm, 5 years ago

In VirtualBox 6.x, this problem appeared again ...

comment:16 by gvm, 5 years ago

Resolution: fixed
Status: closedreopened

comment:17 by aeichner, 4 years ago

Resolution: fixed
Status: reopenedclosed

No follow up by the user reopening the ticket and no VBox.log provided, closing. Please reopen if still an issue with the most recent VirtualBox release and provide at least a VBox.log of the affected VM and a detailed description of the steps you are taking to reproduce this.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use