Unwantet CPU-breakpoint

[Jan Emil Larsen]

I have an app that, when started from the IDE, stops at a CPU breakpoint -
"ntDll.DbgUserBreakPoint".
I didn't place any breakpoints myself.

Some time ago I read about such a behaviour, but I can't recall where, how
and what to do.

Any suggestions would be most welcome ...

[Mart]

> I have an app that, when started from the IDE, stops at a CPU breakpoint -
> "ntDll.DbgUserBreakPoint".
> I didn't place any breakpoints myself.
>

> Any suggestions would be most welcome ...

Under Win2k?

I would start by applying the Service Pack 2.

Mart

[Jan Emil Larsen]

Yes, D5E under Win2K, and after SP2...

"Mart" <ROT13...@genvafhesvat.pbz> skrev i en meddelelse
news:3cf53f5a$1_1@dnews...

[Marlin]

I too am having the same problem. I have used D5 in W2K, SP1 for over a year
and the problem just started in the last month or so.

I have searched for anything that changed in my IDE settings or new software
installations. I cannot find anything unusual.

[Marlin]

Anyone else out here having this problem or...

...perhaps have the solution?

TIA

[Woody (TMW)]

"Marlin" <mcr...@data-nexus.com> wrote in message
news:3CF77C33...@data-nexus.com...

> Anyone else out here having this problem or...
>
> ...perhaps have the solution?
>

There is an IDE patch that solves this. However, for me, it stops
the ability to examine dataset field values. I have to turn it off
for debugging database stuff. Other than that, it works good. <g>

I can't remember exactly where I got it now, but if you search
mers or google, you should turn up some past posts about the Win2k
Debug Breakpoint Fixup for the IDE. If anyone else has this
information, feel free to post the link.

Woody (TMW)

[Marlin]

>
> There is an IDE patch that solves this. However, for me, it stops
> the ability to examine dataset field values. I have to turn it off
> for debugging database stuff. Other than that, it works good. <g>
>
> I can't remember exactly where I got it now, but if you search
> mers or google, you should turn up some past posts about the Win2k
> Debug Breakpoint Fixup for the IDE. If anyone else has this
> information, feel free to post the link.
>

Thanks Woody. I found a DelphiFAQ reference and a community.borland.com
fix that you mentioned. The FAQ says the following:

--------Start of FAQ--------

"ntdll.DbgUserBreakPoint" during debug startup

Q:

Whenever I start a program from the IDE with debugging enabled, the CPU
window pops up and it reports something like ntdll.DbgUserBreakPoint -
but I do not have any breakpoints set in my project.

A:

This is debug code in NTDLL.DLL itself. It gets executed if you have
more than 16 colors for the application icon. You can help yourself by
changing the number of colors for icons (Control Panel, Display
Properties).

Microsoft must have hard-coded a debug breakpoint (int 3) in ntdll.dll
to trace a bug and then they forgot to take it out for final build of
Windows NT.

--------End of FAQ--------

The fix download is not working (currently) on the borland site so I
will try it later. According to the borland site, It does indeed have
the nasty side effect that you mentioned.

Thanks again.

[Woody (TMW)]

"Marlin" <mcr...@data-nexus.com> wrote in message

news:3CF7A1F8...@data-nexus.com...

>
> The fix download is not working (currently) on the borland site
so I
> will try it later. According to the borland site, It does
indeed have
> the nasty side effect that you mentioned.
>

I must have missed the reference to my problem there. I'll have to
go back and read it again. Thanks. Glad you found it.

Woody (TMW)

[Jan Emil Larsen]

I can't find the references mentioned below.
Anyway, does anyone know a remedy without the "nasty" patch.
Icons is 16 bits, and I'm using W2k SP2, but I still have the problem

"Marlin" <mcr...@data-nexus.com> skrev i en meddelelse
news:3CF7A1F8...@data-nexus.com...