Delphi Breakpoint that I didn't set! What-the-hell is Delphi doing?
Colin MacKenzie
Every time I run my program it stops at a certain point, it doesn't
give me an error, and there is no breakpoint there I have to press F9
again to continue running normally. If I run the same executable
outside of delphi (no debugger) it doesn't stop, it works properly.
I don't understand why it keeps stopping here, I have ignored it for
weeks now and the place that it stops at has changed as my program has
gotten larger, etc., eventhough I havent modified that part of the
source it stops on. IN fact it is now stopping in a section of
Delphi's Sample Components, the spin edit component.
I am getting annoyed at it. Anybody have any idea what it is?
Thanks Colin,
Colin MacKenzie
Silicon Electronics
http://www.atcon.com/~cmackenz
Metro Halifax, Nova Scotia, Canada
(902) 864-3982
Eric Meyers
Try a rebuild all.
Colin MacKenzie <cmack...@mail.ips.ca> wrote in article
<4vvffj$u...@thor.atcon.com>...
Terry Harris
cmack...@mail.ips.ca (Colin MacKenzie) wrote:
>
>Every time I run my program it stops at a certain point, it doesn't
>give me an error, and there is no breakpoint there I have to press F9
>again to continue running normally. If I run the same executable
>outside of delphi (no debugger) it doesn't stop, it works properly.
Try looking at View|Breakpoints you will probably find one there. I
see this a lot. A breakpoint set before a code change seems to hang
around but not show as a breakpoint in the source view.
Cheers Terry...
Iman L. Crawford
cmack...@mail.ips.ca (Colin MacKenzie) wrote:
>Every time I run my program it stops at a certain point, it doesn't
>give me an error, and there is no breakpoint there I have to press F9
>again to continue running normally. If I run the same executable
>outside of delphi (no debugger) it doesn't stop, it works properly.
>I don't understand why it keeps stopping here, I have ignored it for
>weeks now and the place that it stops at has changed as my program has
>gotten larger, etc., eventhough I havent modified that part of the
>source it stops on. IN fact it is now stopping in a section of
>Delphi's Sample Components, the spin edit component.
>I am getting annoyed at it. Anybody have any idea what it is?
>Thanks Colin,
>Colin MacKenzie
>Silicon Electronics
>http://www.atcon.com/~cmackenz
>Metro Halifax, Nova Scotia, Canada
>(902) 864-3982
Is the break occurring inside a try except block? If so you probably
have break on exception. You caught the exception, but Delphi will
still break. Try going to the options page and turning it off.
Iman L. Crawford
ilcr...@aracnet.com
Dear diary,
My teen angst has a body count
-Heathers
John Hansen
In article <4vvffj$u...@thor.atcon.com>, cmack...@mail.ips.ca says...
>
>
>Every time I run my program it stops at a certain point, it doesn't
>give me an error, and there is no breakpoint there I have to press F9
>again to continue running normally. If I run the same executable
>outside of delphi (no debugger) it doesn't stop, it works properly.
>
In my experience the reason this happens is you have a VCL compiled with Debug
options turned on linked into your Complib.dcl file and your current project
options are set with the debug options turned off. If you turn on the debug
options for your project and build all the problem should go away.
Conversely, if you copy the source of the VCL in question to the directory of
your project and build all with debug options off the problem will also go
away. Then you can (if you want) copy the DCU file for the VCL to the
appropriate location and Rebuild the component library. Once the non-debug
version of the VCL is "in" the component library then this problem will go
away.
Do you keep the source for components you add in the same directory as the DCU
version? If you do, I believe Delphi will recompile that file each time you
build-all on your project and if you've changed debug settings you can end up
with a DCU that doesn't match what is compiled into the component library.
Then the next time you add another component the DCU for that other component
(which now may well have debug information inside it) will be relinked into
the library. And your problems will begin all over again. I always remove
the PAS files from the directory where my VCL DCU component library files are
kept so the ones there remain all compiled with no debug information. If I
need to debug the VCL with my app I put the PAS file in the directory of my
project and build all with debug options turned on.
--
----------------------------
John C. Hansen
han...@wpgate1.wpafb.af.mil
Arjan J. Moraal
Hi Eric,
Eric Meyers wrote:
>> Every time I run my program it stops at a certain point, it
>> doesn't give me an error, and there is no breakpoint there I have
>> to press F9 again to continue running normally. If I run the same
>> executable outside of delphi (no debugger) it doesn't stop, it
>> works properly.
> Try a rebuild all.
I sometimes have the same problem. Rebuild all doesn't work and the
Breakpoints window doesn't contain any breakpoint.
Regards,
Arjan
Arjan J. Moraal | PGP key? Send empty msg to
Paninaro Development | pgp-aj...@paninaro.iaf.nl
Groningen, The Netherlands |
BlkBoxDev
If you set the breakpoint by hitting the F5 key, and subsequently delete
that line, the break point is still active but hidden. Check the
breakpoint settings by hitting Alt+V,R
Yo.
KS
Mark Radcliffe
Hi Eric,
Eric Meyers wrote:
> Try a rebuild all.
Regards,
Arjan
---------------------------------------------------------------------
Try deleteing all non-source files from the source directory
(e.g. *.~*, *.dsm, *.dsk) and then Rebuild All. This once got rid of
a build problem for me!
Jose R. Nebro
> >> Every time I run my program it stops at a certain point, it
> >> doesn't give me an error, and there is no breakpoint there I have
> >> to press F9 again to continue running normally. If I run the same
> >> executable outside of delphi (no debugger) it doesn't stop, it
> >> works properly.
>
> > Try a rebuild all.
>
>I sometimes have the same problem. Rebuild all doesn't work and the
>Breakpoints window doesn't contain any breakpoint.
>
>
I have the opposite problem I have a project with alot of units/Forms
In some of these units I can't place a break point and in other I can
I know that the compiler/linking is not deleting this code since I
can put a showbox or Messagedlg on the code and when I run the app
I can see the dialog box. Still if I try to put the break point, delphi
tells me that there is not debug info at this line. I have debug info
turned on on Options|Environment Options|Integrated Debugging, and also
in Options|Project|Compiler|Debug Info, Local Symbols, Symbol Info. I
Tried playing with these setting at no avail. Why does delphi not let
me debug some units while on others it is ok?
Thanks In Advance..
This is Driving me Crazy!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
--
===================================================================
Jose R. Nebro
jo...@amanda.dorsai.org
===================================================================
i-su...@nwu.edu
I have the same problem too, and I tried to delete and won't go away.
Definitely a bug I say.
I. Sumera
i-su...@nwu.edu
David Dice
> >> Every time I run my program it stops at a certain point, it
> >> doesn't give me an error, and there is no breakpoint there I have
> >> to press F9 again to continue running normally. If I run the same
> >> executable outside of delphi (no debugger) it doesn't stop, it
> >> works properly.
I believe this is a bug in Delphi. I have had the same problem on an
application I have been working on for at least the last 6 months.
This app has been rebuilt many times, and all break points cleared out
many times as well. In one unit, if I set a breakpoint in the unit on
_any_ line, the debugger will stop on two lines (consistently the same)
that have no breakpoint. These lines may have had a breakpoint at one
time--I can't recall. They are in the on close procedure, so the
program always stops there. If no breakpoint is set in the unit, it
does not stop at this point.
--
David Dice
Technologies Facilitator, Carlton Comprehensive High School
dd...@paschools.pa.sk.ca
http://www.carlton.paschools.pa.sk.ca/digipac/dice.htm
Svante Granqvist
Jose R. Nebro wrote:
>
>
> I have the opposite problem I have a project with alot of units/Forms
> In some of these units I can't place a break point and in other I can
> I know that the compiler/linking is not deleting this code since I
> can put a showbox or Messagedlg on the code and when I run the app
> I can see the dialog box. Still if I try to put the break point, delphi
> tells me that there is not debug info at this line. I have debug info
> turned on on Options|Environment Options|Integrated Debugging, and also
> in Options|Project|Compiler|Debug Info, Local Symbols, Symbol Info. I
> Tried playing with these setting at no avail. Why does delphi not let
> me debug some units while on others it is ok?
>
> Thanks In Advance..
> This is Driving me Crazy!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> --
> ===================================================================
> Jose R. Nebro
> jo...@amanda.dorsai.org
> ===================================================================
Without having done any deeper research in this area, could it be that
the code you put the breakpoint on doesn't really do anything useful,
and the complier removes it. That is, have you tried to put the
breakpoint ON THE LINE CONTAINING MESSAGEDLG... ?
Also you may try to see the assembly code generated by the "CPU" window
described previously in this group.
Hope it helps!
--
Svante Granqvist Speech, Music and Hearing
Phone +46-8-790 7561 Box 700 14
Fax +46-8-790 7854 S-100 44 Stockholm
mailto://sva...@speech.kth.se http://www.speech.kth.se/~svante
Peter Hamilton-Scott
Colin,
I've had similar problems and I tracked it down to two possibilities.
First, try the obvious of clearing all
breakpoints. But, this does'nt always help. Second, there are occasional
problems with the IDE getting
messed up. For example, I had a project that used the OLE controls unit,
and no matter what I tried
to do, it would actually try to compile the blasted thing! The solution to
both faults lay in creating a brand
new project. Then, add units as normal. BUT... AND THIS WAS CRUCIAL... make
sure you copy and paste
the code from the old project. DO NOT copy the files. Something goes very
wrong with the pathnames where
your new project tries to hook to the old. Code changes update the old
project and this is a real mess. Having done this, it certainly cleared up
my problem with fictitious breakpoints. My local South African distributor
has reluctantly confrimed that the IDE is a bit buggy and that Borland know
about these problems.
Hope this helps...regards
Colin MacKenzie <cmack...@mail.ips.ca> wrote in article
<4vvffj$u...@thor.atcon.com>...
>
> Every time I run my program it stops at a certain point, it doesn't
> give me an error, and there is no breakpoint there I have to press F9
> again to continue running normally. If I run the same executable
> outside of delphi (no debugger) it doesn't stop, it works properly.
>
Ken K.
When I get this, I just set a breakpoint on the problem line, then clear
it
again. Ghost breakpoint gone! So far, it's worked every time.
Hope this helps.
>
> > >> Every time I run my program it stops at a certain point, it
> > >> doesn't give me an error, and there is no breakpoint there I have
> > >> to press F9 again to continue running normally. If I run the same
> > >> executable outside of delphi (no debugger) it doesn't stop, it
> > >> works properly.
>
Jose R. Nebro
In article <322BEF...@speech.kth.se>, sva...@speech.kth.se says...
#
#Jose R. Nebro wrote:
##
##
## I have the opposite problem I have a project with alot of units/Forms
## In some of these units I can't place a break point and in other I can
## I know that the compiler/linking is not deleting this code since I
## can put a showbox or Messagedlg on the code and when I run the app
## I can see the dialog box. Still if I try to put the break point, delphi
## tells me that there is not debug info at this line. I have debug info
## turned on on Options|Environment Options|Integrated Debugging, and also
## in Options|Project|Compiler|Debug Info, Local Symbols, Symbol Info. I
## Tried playing with these setting at no avail. Why does delphi not let
## me debug some units while on others it is ok?
##
## Thanks In Advance..
## This is Driving me Crazy!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
## --
##
#Without having done any deeper research in this area, could it be that
#the code you put the breakpoint on doesn't really do anything useful,
#and the complier removes it. That is, have you tried to put the
#breakpoint ON THE LINE CONTAINING MESSAGEDLG... ?
#
#Also you may try to see the assembly code generated by the "CPU" window
#described previously in this group.
#Hope it helps!
#
#--
#Svante Granqvist Speech, Music and Hearing
#Phone +46-8-790 7561 Box 700 14
#Fax +46-8-790 7854 S-100 44 Stockholm
#mailto://sva...@speech.kth.se http://www.speech.kth.se/~svante
Definetly not These units are not beeing deleted by the compiler
I have (BTW) put the break point right at the MessageDlg and the
system will say that the break Point is in a line with no debug
info. That is alot of BS. I know that this code is beeing executed
Since some of these units contain code which is crucial to the
app.
Any advice anybody?
Thanks....
Sean Cross
On 1 Sep 1996 02:02:07 GMT, jo...@dorsai.dorsai.org (Jose R. Nebro)
wrote:
>
>> >> Every time I run my program it stops at a certain point, it
>> >> doesn't give me an error, and there is no breakpoint there I have
>> >> to press F9 again to continue running normally. If I run the same
>> >> executable outside of delphi (no debugger) it doesn't stop, it
>> >> works properly.
>>
>> > Try a rebuild all.
>>
>>I sometimes have the same problem. Rebuild all doesn't work and the
>>Breakpoints window doesn't contain any breakpoint.
>>
>>
>
Close your project, delete your dsk file and reopen the project.
>
>I have the opposite problem I have a project with alot of units/Forms
>In some of these units I can't place a break point and in other I can
>I know that the compiler/linking is not deleting this code since I
>can put a showbox or Messagedlg on the code and when I run the app
>I can see the dialog box. Still if I try to put the break point, delphi
>tells me that there is not debug info at this line. I have debug info
>turned on on Options|Environment Options|Integrated Debugging, and also
>in Options|Project|Compiler|Debug Info, Local Symbols, Symbol Info. I
>Tried playing with these setting at no avail. Why does delphi not let
>me debug some units while on others it is ok?
>
Look for a $D- declaration in the problem unit.
Sean
Koen Serry
According to what i read i think you have to change in
project-options-compiler and check the debugger checkbox to on. i had
the same problem some minutes ago
hope this helps
Jonas Rapp
David Dice wrote:
>
> > >> Every time I run my program it stops at a certain point, it
> > >> doesn't give me an error, and there is no breakpoint there I have
> > >> to press F9 again to continue running normally. If I run the same
> > >> executable outside of delphi (no debugger) it doesn't stop, it
> > >> works properly.
>
the recompiling ?
This should do it, I think. (Maybe this was obvious to you, but this is
my suggestion)
/JR
Stephane P. Leclair
Jose R. Nebro wrote:
> Definetly not These units are not beeing deleted by the compiler
> I have (BTW) put the break point right at the MessageDlg and the
> system will say that the break Point is in a line with no debug
> info. That is alot of BS. I know that this code is beeing executed
> Since some of these units contain code which is crucial to the
> app.
>
> Any advice anybody?
> Thanks....
> --
> ===================================================================
> Jose R. Nebro
> jo...@amanda.dorsai.org
> ===================================================================
I've seen this kind of problem happen in the visual c++ debugger as
well (notice the lowercase letters 8-)). I eventually found out it had
to do with the location of the executable: the compiler had created the
DLL in directory A and I was executing a copy of it from directory B.
From the debugger's point of view, the object program was not the one
executing. It may be related, I don't know. I've never seen this with
Delphi 2.
Related or not, one possible way to work around your problem would be
with an inline-assembled INT 3 instruction. No debugger can skip that,
but it does imply that you have to recompile every time you want to move
your breakpoint... Instead of the INT 3, a call to the Windows API
function DebugBreak might do the trick...
Just my two cents' worth...
Urs Scherrer
already tried? I'm sorry
--
Urs Scherrer
imt - Information Management Technology AG, CH-9471 Buchs
http://www.imt.ch phone: +41 81 750 06 44
mailto:Sche...@imt.ch fax : +41 81 750 06 45
Malcolm Coulter
In article <322E23...@CAM.ORG> "Stephane P. Leclair" <sle...@CAM.ORG> writes:
>From: "Stephane P. Leclair" <sle...@CAM.ORG>
>Subject: Re: Delphi Breakpoint that I didn't set! What-the-hell is Delphi doing?
>Indeed
>Date: Wed, 04 Sep 1996 20:48:07 -0400
>Jose R. Nebro wrote:
>SPL
>sle...@cam.org
I had a similar problem with delphi 1, but in my case it was the source files
that were wrong (due to some external-to-Delphi copying).
Just my ten cents (adjusting for inflation) worth ...
Malcolm
yuvalp
>
> >
> >> >> Every time I run my program it stops at a certain point, it
> >> >> doesn't give me an error, and there is no breakpoint there I have
> >> >> to press F9 again to continue running normally. If I run the same
> >> >> executable outside of delphi (no debugger) it doesn't stop, it
> >> >> works properly.
> >>
> >>
> >>I sometimes have the same problem. Rebuild all doesn't work and the
> >>Breakpoints window doesn't contain any breakpoint.
> >>
> >>
> >
>
> Close your project, delete your dsk file and reopen the project.
>
> >
> >I have the opposite problem I have a project with alot of units/Forms
> >In some of these units I can't place a break point and in other I can
> >I know that the compiler/linking is not deleting this code since I
> >can put a showbox or Messagedlg on the code and when I run the app
> >I can see the dialog box. Still if I try to put the break point, delphi
> >tells me that there is not debug info at this line. I have debug info
> >turned on on Options|Environment Options|Integrated Debugging, and also
> >in Options|Project|Compiler|Debug Info, Local Symbols, Symbol Info. I
> >Tried playing with these setting at no avail. Why does delphi not let
> >me debug some units while on others it is ok?
> >
>
> Look for a $D- declaration in the problem unit.
>
> Sean
Turn code optimization off
Josef Garvi
I have the same problem. Would be appreciate any help.
>Thanks In Advance..
>This is Driving me Crazy!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
>--
>===================================================================
>Jose R. Nebro
>jo...@amanda.dorsai.org
>===================================================================
Josef Garvi
E-Mail: eden.fo...@mailbox.calypso.net
http://members.tripod.com/~JosefG/
--
"Everything you see is blocking your sight..."
TimeOilMIS
Whenever I've had those problems, I've noticed a couple of things. Often
times I will have screwed up a nearby if then else kindadeal, missing a
";" after an end or something, or else it occurs after I have tried to
"Run" an application that has a problem. I usually quit Delphi and
restart, and the problem is solved. Doesn't help you much tho...
Brad Miller
Timeo...@aol.com
Smith
Has anyone ever had the problem that Delphi complains that the
breakpoint you just laid down isn't on any line of code when, infact,
it is???
"Ken K." <ken...@nethos.net> wrote:
>When I get this, I just set a breakpoint on the problem line, then clear
>it
>again. Ghost breakpoint gone! So far, it's worked every time.
>Hope this helps.
>>
>> > >> Every time I run my program it stops at a certain point, it
>> > >> doesn't give me an error, and there is no breakpoint there I have
>> > >> to press F9 again to continue running normally. If I run the same
>> > >> executable outside of delphi (no debugger) it doesn't stop, it
>> > >> works properly.
>>
>> I believe this is a bug in Delphi. I have had the same problem on an
>> application I have been working on for at least the last 6 months.
>> This app has been rebuilt many times, and all break points cleared out
>> many times as well. In one unit, if I set a breakpoint in the unit on
>> _any_ line, the debugger will stop on two lines (consistently the same)
>> that have no breakpoint. These lines may have had a breakpoint at one
>> time--I can't recall. They are in the on close procedure, so the
>> program always stops there. If no breakpoint is set in the unit, it
>> does not stop at this point.
>>
Cheers,
Damien
========================================================
Are you a shareware programmer? E-mail me for info on
something I'm writing to make your life a lot easier!!!
=== "http://204.101.50.93/students/damien/dmhome.htm" ===
Mark Pritchard
This could be the optimiser removing code which is never called. Are you
sure the procedure you are placing the breakpoint in is in use?
--
Mark Pritchard
Smith <dms...@newcomm.net> wrote in article
<32360...@endeavor.newcomm.net>...
Phoenix Business Enterprises
>Has anyone ever had the problem that Delphi complains that the
>breakpoint you just laid down isn't on any line of code when, infact,
>it is???
Do a build all. There are several things that can cause this. One is breaking,
then changing code with out resetting. (ie moving lines)
_
NOTE: This software is currently in early alpha. If you notice any
problems, or RFC non-compliance, please report it to p...@pbe.com
\------------------------------------------------------------\
\ Chad Z. Hower - pho...@pobox.com \
\ Phoenix Business Enterprises - p...@pbe.com - www.pbe.com \
\ Physically in Church Hill, TN - Logically Not Sure \
\------------------------------------------------------------\
>>SQUID - The ultimate 95/NT offline databasing reader
**Special Compile: 3.000A (Alpha)