Breakpoint does not break
Johan Smit
After some weird mishap, I had to re-install Delphi5, and the update.
Now I cannot use the integrated debugger.
The blue dots are there, and clicking on the left brings the selected
line in red, but it does not break at the breakpoint. The DLL that is
being debugged just runs.
I have selected the project/options all that I can see for debugging,
and am at wits end.
When I insert asm int 3 end; the CPU page is shown, but I cannot go to
the next line, it keeps on showing machine code.
The project did recognise breakpoints before, so I cannot believe it
is in the project. The problem must be in the Delphi.
Please help!
Thank you
Johan Smit
Nicholas Sherlock
It sounds like the unit you're viewing in the editor is not the unit
that Delphi is using. Make sure that you don't have more than one copy
of your unit anywhere on Delphi's search paths. Delete the .dcu for your
unit and rebuild, then try again.
Cheers,
Nicholas Sherlock
GB Blanchard
> line in red, but it does not break at the breakpoint.
I've read here in the past that normally a 'Build All' fixes it, or -
delete all .dcu files and re-compile.
--
Brad Blanchard
http://www.braser.com
Email accepted from the website
VBDis
<11...@1122noexiste.net> schreibt:
> I've read here in the past that normally a 'Build All' fixes it, or -
>delete all .dcu files and re-compile.
Depending on a project structure it may be possible to have source files open
in the IDE that differ from the actually compiled source files. Then Delphi may
use some open file of the same name, instead of the really compiled source
file. Then it may help to close the (edit) file in question.
Sometimes also breakpoints from previous (up to very old) compiles continue to
exist. Then I found it useful to consult the breakpoint list and to delete
there all otherwise not accessible breakpoints.
DoDi
Johan Smit
<smit...@spamlantic.net> wrote:
>Hi,
>After some weird mishap, I had to re-install Delphi5, and the update.
>Now I cannot use the integrated debugger.
Hi,
Thank you for the replies.
I have finally found the problem.
I had rebuilt the project, and I did delete all the .dcu's, and still
it did not work.
Then in desperation, I closed the open files one by one, and lo and
behold, there behind the DLL files, was an open .dpk package file. I
had to re-install some packages, and somehow, the package file was
still open. I closed that, reopened the DLL .dpr, and everything was
fine again.
We live and learn. I don't know how the package file and the DLL
project file can both be open, but that is what happened, and the .dpk
file was invisible behind the other open files.
Thank you all again.
Best Regards
Johan Smit
Maarten Wiltink
news:hrt1s0t02tqkbrot0...@4ax.com...
> [...] I don't know how the package file and the DLL project file can
> both be open,
Any number of packages can be open in addition to a project.
> [...] the .dpk file was invisible behind the other open files.
Alt-0 shows a list of all open windows. Alt-Esc is a _Windows_ key
combination that has the side-effect of sending the focused window
to the back. It's also useful to get at modal dialogs that are
behind their application window.
Groetjes,
Maarten Wiltink
Johan Smit
<maa...@kittensandcats.net> wrote:
>Any number of packages can be open in addition to a project.
>
>Alt-0 shows a list of all open windows. Alt-Esc is a _Windows_ key
>combination that has the side-effect of sending the focused window
>to the back. It's also useful to get at modal dialogs that are
>behind their application window.
>
Hello Maarten,
Thank you very much. This shows you my lack of knowledge.
I will now remember both those keystrokes.
Regards
Groete uit Suid-Afrika!
Johan Smit