Delphi 6 CPU Window
Neo
I do not know what changed in my delphi 6, but every time I click "Run"
(F9) A window "CPU" appears where the code appears to be stopped. Seems
to be I had put there a breakpoint.
I do not know what to do with that window.
How can I do to not appear that window?
TIA
Pieter Zijlstra
You mean directly at the start of the program?
What happens if you continue? AVs?
Do you use FastMM4?
If so then it could be that you have FullDebugMode switched on and that
the application cannot find the FastMM_FullDebugMode.dll.
--
Pieter
Peter Below (TeamB)
Check the breakpoint view (View->Debug windows), delete all breakpoints
you see there. Do a full rebuild of your project.
--
Peter Below (TeamB)
Don't be a vampire (http://slash7.com/pages/vampires),
use the newsgroup archives :
http://www.tamaracka.com/search.htm
http://groups.google.com
Neo
the window of breakpoints appears but is empty.
I do not know what is happening to my delphi 6.
Thanks for readme and If it happens some other idea is welcome.
Neo
Peter Below (TeamB) escribió:
Neo
> The CPU Windows appears when I click "Run" (F9).
But After answering Peter I´ve found more data. Following your question
I went to dpr to put a breakpoint in
Application.Initialize ,
...But there is not the problem. The problem is a few lines further down.
The problem (CPU Window appear) is in a function call to a external DLL
that I use to protect the executable. At the time of calling the
function of the Dll, the CPU Window appear.
What can I do?
Thanks for readme, sorry mi pathetic english.
Neo
Pieter Zijlstra escribió:
Pieter Zijlstra
> Hi Pieter, I said:
>
> > The CPU Windows appears when I click "Run" (F9).
>
> But After answering Peter I´ve found more data. Following your
> question I went to dpr to put a breakpoint in
>
> Application.Initialize ,
>
> ...But there is not the problem. The problem is a few lines further
> down.
> The problem (CPU Window appear) is in a function call to a external
> DLL that I use to protect the executable. At the time of calling the
> function of the Dll, the CPU Window appear.
>
> What can I do?
Do you use static or dynamic linking?
What happens when you press F9 after the CPU windows appear, does the
application continue/stop/give access violations???
What happens when you run your app outside the IDE?
--
Pieter
Neo
I“m using static linking. After the CPU windows appear, I press F9 and
the App run normally without any exception. The app run normally even in
the debug mode (only stop in these moment, like break point). There is
not a Acces Violation.
Of course, if I run my app outside the IDE, run perfectly. No problem.
But inside IDE, the execution stop in dll call and show CPU Window.
Is a mystery to me
Thanks
Pieter Zijlstra escribió:
Pieter Zijlstra
> Hi, thanks for the answer
> I´m using static linking. After the CPU windows appear, I press F9
> and the App run normally without any exception. The app run normally
> even in the debug mode (only stop in these moment, like break point).
> There is not a Acces Violation. Of course, if I run my app outside
> the IDE, run perfectly. No problem. But inside IDE, the execution
> stop in dll call and show CPU Window. Is a mystery to me
Did it ever worker before?
Was the DLL just update?
Did you change anything else in the system / Delphi in the mean-time.
What does it show in the debug window... or post a screenshot (png) of
the CPU window, when your app stops, to borland.public.attachments.
--
Pieter
Peter Below (TeamB)
> Hi, thanks for the answer
> I´m using static linking. After the CPU windows appear, I press F9
> and the App run normally without any exception. The app run normally
> even in the debug mode (only stop in these moment, like break point).
> There is not a Acces Violation. Of course, if I run my app outside
> the IDE, run perfectly. No problem. But inside IDE, the execution
> stop in dll call and show CPU Window. Is a mystery to me
What instruction does the CPU window show at the current code location?
What you see sounds as if the DLL contains a hardcode breakpoint (int
3) instruction...
Neo
Pieter Zijlstra escribió:
>> I´m using static linking. After the CPU windows appear, I press F9
>> and the App run normally without any exception. The app run normally
>> even in the debug mode (only stop in these moment, like break point).
>> There is not a Acces Violation. Of course, if I run my app outside
>> the IDE, run perfectly. No problem. But inside IDE, the execution
>> stop in dll call and show CPU Window. Is a mystery to me
>
> Did it ever worker before?
> Was the DLL just update?
Yes, the DLL version is "new". Has changed.
> Did you change anything else in the system / Delphi in the mean-time.
No. I have not changed (I think) anything at my delphi 6.
> What does it show in the debug window... or post a screenshot (png) of
> the CPU window, when your app stops, to borland.public.attachments.
moments ago I put in borland.public.attachments a picture of the CPU
window when appear in my screen.
Thank you very much.
<
Neo
Peter Below (TeamB) escribió:
>> I´m using static linking. After the CPU windows appear, I press F9
>> and the App run normally without any exception. The app run normally
>> even in the debug mode (only stop in these moment, like break point).
>> There is not a Acces Violation. Of course, if I run my app outside
>> the IDE, run perfectly. No problem. But inside IDE, the execution
>> stop in dll call and show CPU Window. Is a mystery to me
>
> What instruction does the CPU window show at the current code location?
> What you see sounds as if the DLL contains a hardcode breakpoint (int
> 3) instruction...
Yes, moments ago I put in borland.public.attachments a picture of the
CPU window when appear in my screen. Yes, Sounds like what you say.
In reality stops a line below.
I am thinking now that manufacturers have forgotten a breakpoint here.
Right? Should I talk to them?.
Thank you for the answers.
-
Peter Below (TeamB)
> I am thinking now that manufacturers have forgotten a breakpoint
> here. Right? Should I talk to them?.
Yes, that would be the cleanest solution: get a new version without the
breakpoint.