Home General

CPU breakpoint???

edited August 2001 in General
When I compile and execute my application while running Delphi (D6E) using
ReportBuilder 6.01 I get a CPU breakpoint at address 77FA018D ret, followed
by ntdll.dbgUserBreakPoint. If I press go, it goes ahead and creates the
report. However, since I have not set any breakpoints this is annoying.
How do I get rid of this behavior?

--
Regards,

John

www.barjohn.com
johng@barjohn.com

Comments

  • edited September 2001
    > When I compile and execute my application while running Delphi (D6E) using
    followed

    This is caused by breakpoints that Microsoft left in some windows 2000
    dll's. It has nothing to do with either Delphi or ReportBuilder.

    For a workaround look on the Delphi Code Central for USG Delphi 6 Utilities:

    http://codecentral.borland.com/codecentral/ccweb.exe/listing?id=16098

    There's also a fix by Dennis Passmore for Delphi 5.

    Jan Derk
  • edited September 2001
    Thanks for the tip. I tried it and unfortunately it didn't work. Even
    after recompiling in the event that entry points had changed.

    --
    Regards,

    John

    www.barjohn.com
    johng@barjohn.com
  • edited September 2001
    > Thanks for the tip. I tried it and unfortunately it didn't work. Even

    You've got to read the readme very carefully. If you don't put the exact
    right address in the ini it will not work. You need the int3 breakpoint
    address. I had to iterate a couple of times before it worked.

    JD
  • edited September 2001
    > When I compile and execute my application while running Delphi (D6E) using
    followed

    I think the latest release of Win2K resolves this, since I've not seen it in
    since the upgrade.

    --
    Tim Sullivan
    Unlimited Intelligence Limited
    Dimethylaminoethanol for your software
    http://www.uil.net
  • edited September 2001
    > I think the latest release of Win2K resolves this, since I've not seen it
    in

    I'm afraid not. ntdll debug breakpoints are still there even with Service
    Pack 2.

    JD
This discussion has been closed.