Yep, I did upgrade my system from Win98 but I installed Win2k in a seperate
folder on a seperate drive so as to keep the Win98 install. AFAIK this is
the same as a new install of Win2k as nothing from the Win98 install was
brought over.
The app is a realtime only app, no DB stuff. But the problem occurs
straight away. I can put a break point on the first begin statement in the
project source and the app breaks there first before the problem starts.
But the problem starts accuring when I press F8!! Go figure?!?!? And as I
said there is no call stack.
I looked at the other app and it does get a call stack. The same problem
for it seems to be happening on calls to create with decendents of
TComponent where nil is passed to the constructor as the owner, eg
TTimer.Create(nil)
Also when I installed D5 I got a message about replacing the default
debuging program in win2K, or something like that. It may have been talking
about replacing Dr Watson. It was something along those lines, but I have
no idea if I said yes or no though.
Nahum
-----Original Message-----
From: Nic Wise [mailto:[EMAIL PROTECTED]]
Sent: Monday, 3 April 2000 23:40
To: Multiple recipients of list delphi
Subject: Re:[DUG]: Win2K + D5 problems
I havn't enounted it (I run Win2K on both my work machine and my home
machine,
and have done for ages), but I know that in protected mode, INT 03 is the
debug
trigger - your debugger traps int 3, and inserts the hex for it whereever
you want
to break at.
Dunno why its doing it in ntdll.dbgbreakpoint, tho it IS a good name for it
:)
What does the app do? does it always do it in the same place? Worse yet,
please
tell me you didn't upgrade from 98 to win2k? If you did, that most likely to
be your
problem (my flatmate did NT4 -> Win2K, and it was a very nasty mess).
N
On 3/04/2000 22:55:59, "Nahum \(Realism\)" blurted out...
>I've got an app that I was developing in D5 under win98, I upgraded my
>system to win2000 and I am now getting bizzar behaviour from the D5 IDE
>whenever I try to run the app with integrated debugging enabled. My app
>keeps breaking, as in break point without any error messages, into the CPU
>window at ntdll.DbgBreakPoint : 77F9F9Df int 3. I press F9 to continue and
>it happens again, and again, and again - about 9 times in all then it run
>fine, sometimes it will break again for no reason. I have another app that
>I just give up pressing F9 on.
>
>Now I have never really used the CPU window before, but I can only guess
>what is happening - ntdll is manually throwing a break point with the 'int
>3'??? Oh, and I don't get a call stack either. If I run my app outside of
>the IDE it works fine.
>
>Has anyone encountered this before/yet??
>
>I have fully updated Win2000 and D5 and that didn't help.
>
>Thanks in advance for any help....
>
>
>
>Nahum Wild
>Manager
>Realism Limited
>
>---------------------------------------------------------------------------
> New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
> Website: http://www.delphi.org.nz
>
--
Nic Wise - Human (just)
ph: 09.277.5309 / cell: 021.676.418 / em: [EMAIL PROTECTED]
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
