Debugger incompatible with Windows XP SP2

From: hanko panko (hhofmans_at_xs4all.nl)
Date: 03/26/04

  • Next message: crystal: "ADO - XML file" 
    Date: 26 Mar 2004 13:17:40 -0800

    I installed Windows XP SP2 RC1 on two machines.

    I am worried.

    Because the debugger now gets stuck on ADO components. Reinstallation
    of Delphi and MDAC did not help. Currently Windows XP SP2 and Delphi
    7.0 debugger are having a conflict.

    Who is gonna resolve this: Microsoft? Borland?

  • Next message: crystal: "ADO - XML file"

    Relevant Pages

    • Re: Access violation when allocating memory in windows
      ... >> while the function causes access violation message in debugger. ... > The Delphi debugger is not good at catching this sort of thing. ... > exception is probably happening somewhere else altogether. ... I use my delphi source code in Ollydbg all the time. ...
      (comp.lang.pascal.delphi.misc)
    • Re: Does MSIL Qualify?
      ... I realize I am getting spoiled with RosAsm, ... There are still some crashes with the debugger. ... Delphi, had bugs, at least uptil version 3.0 For instance, when replacing ... object memory, causing me to have to work in a real memory inspector to ...
      (alt.lang.asm)
    • Re: IDE for Pascal-family language
      ... Delphi 7 was the last version to use the old IDE. ... I have similar issues with Visual Studio so recently ended up ... it has an MDI interface rather than tabbed windows. ... The debugger does a whole lot more than that. ...
      (comp.lang.pascal.misc)
    • Debugger causes program to slow down
      ... debugger, and press F9 to run the application, it's perfect. ... application that is running from within Delphi under debug is affected. ... The notebook is a 2ghz centrino with 1GB ram and a medium spec ATI ... I've tried all the patches for both windows, ati, the notbook and ...
      (alt.comp.lang.borland-delphi)
    • Re: Borland is neglecting Delphi for Win32 badly
      ... > near as consistently as it IME (and I don't think old Delphi ... Just observing it under a debugger suffers from the ... > Calling conventions messups aren't so much affected, ...
      (borland.public.delphi.non-technical)