Strangest thing ???

Hi, strangest thing is happenning. Last night I was doing some debugging on my Delphi v3 app. Everything was fine...shut things down and went to bed. Today, I get up to continue my debugging...nothing has really changed...except all of a sudden Delphi v3 does not recognize the breakpoints I set in debug mode...it just flies right past them and doesn't stop! What is happening here? I'm pulling my hair out trying to figure this out...

Regards,
   Shawn Halfpenny
   drumme59@sprint.ca
aztecAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

interCommented:
Hi friend,

The problem it weird actually. I have the following suggestions for quick recovery:

1 - Open one of your old projects. Set a break point and see if it works.
2 - IF 1 above works, create a new project over your project, include all the forms and try debuging again.
3 - ELSE notify please,

Regards,
Igor
0
ZifNabCommented:
Mmmm, really spooky things ...
0
interCommented:
Hi Zif, (and are you there aztec?)

How is the grid going (you may not respond if you find it inconvinient in this problem)

Igor


0
Cloud Class® Course: CompTIA Cloud+

The CompTIA Cloud+ Basic training course will teach you about cloud concepts and models, data storage, networking, and network infrastructure.

ZifNabCommented:
Hi Igor & aztec (if I may say something about the grid), well I was working on it, but now i'm overloaded with work, again... I was making a pop-up for memo and bitmaps. Had a problem, but found a solution, so that's one we can add soon to our grid. How about you?
0
interCommented:
Hi there, you may assign a task to me about the grid(a dividable task such as design a for that shows the given bitmap in a blob, etc...). I was ill on all last 9 days so do nothing.
0
ZifNabCommented:
Hi Inter, you may choose a task that you like... Just, look at our CRS and do what you like or even find one out... PS. do you know how I can make a property editor for columns? Just a hint and I make one for different fonts, colors, lookings... I never made a property editor, so it would be great if I knew how to start...
0
ZifNabCommented:
Inter, glad you're cured!
0
OdieCommented:
aztec,

I sometimes have the same problem, it always seems that I just compiled the project as a release.  That is in the project options I somewhere put off the 'integrated debugging'-checkbox.  Don't know if that's the case here, but you can try.
Something else, try closing all files in the project, then reopen your file with the breakpoints and save that file - this sometimes solves this problem in c++builder.
0
aztecAuthor Commented:
Hi Igor...
   I tried debugging another one of my programs...it was fine. Something else strange happened: I compiled my app, then set a breakpoint on the first line of executable code in a BitBtnClick event...it flashed an error window saying that "Breakpoint cannot be set on tis line as there is no executable code on this...."...and so on. But it IS an excutable line of code! Also I notice in my main unit about half way down, it stops putting  those little blue dots in the grey area to left indicating the executable lines of code. The first half of my unit is OK, it has those little dots, then (curiously enough) in the portion I have been working on the last couple of days, the dots stop...and there are no dots from there to the end of the unit. Something weird is going on!

Cheers
   Shawn
0
aztecAuthor Commented:
Hi Igor...
   I tried debugging another one of my programs...it was fine. Something else strange happened: I compiled my app, then set a breakpoint on the first line of executable code in a BitBtnClick event...it flashed an error window saying that "Breakpoint cannot be set on tis line as there is no executable code on this...."...and so on. But it IS an excutable line of code! Also I notice in my main unit about half way down, it stops putting  those little blue dots in the grey area to left indicating the executable lines of code. The first half of my unit is OK, it has those little dots, then (curiously enough) in the portion I have been working on the last couple of days, the dots stop...and there are no dots from there to the end of the unit. Something weird is going on!
   Maybe my unit is too big? Or maybe using 128K as a buffer size in my Blockread statement made my data area too big and strange things are happening? I don't know...

Cheers
   Shawn
0
aztecAuthor Commented:
Hi Igor...
  I just tried your suggestion:

2 - IF 1 above works, create a new project over your project, include all the forms and try debuging again.

..It gave the same problems...there are no little dots to the left of the portion of code I have been working on lately..all the way down to the end of the unit. It will not recognize a breakpoint anywhere in that area.

Regards,
   Shawn
0
Stuart_JohnsonCommented:
I constantly have the same problem with D3.  I'll be happly working along, go home, come back the next day and I wont be able to set break points anywhere.  Even copying the project onto my other machine will not allow the set breakpoints to work.

If anyone has any ideas on this, I too would be interested to find an answer!!

Cheers!

Stu
0
interCommented:
Hi friends,

I am using Delphi 2.0 and do not know about your dots and such things. But if Delphi insist that there is no code generated for THAT line, it may not. Try BUILD ALL, clear all DCU and symbol staff and Compile etc. If I have delphi 3.0 I want to see your project. I am almost sure that this is caused by IDE settings and such staff saved when a delphi project is loaded. Sorry, I can not suggest further because do not have clue for the Delphi 3.0

Sincerely,
Igor
0
aztecAuthor Commented:
Hi Igor and Stuart...
  Well, I called Borland Tech Support ($2.95/minute..ouch) and told them of this problem. The guy I spoke with asked his colleagues and none of them had heard of this error before. he suggested deleting the DCU files and rebuiling. i did that...no good. I even re-installed Delphi 3 from scratch...still no good. The tech guy was no help...I told him to put it down as a bug in Delphi...I don't know if he will or not.
  Anyway, this thing is really screwing me up...I can't get in and do any debugging on a major chunk of my code...this really sets me back. Is there anyone else there that you can bounce this problem off of?
  Stuart, since you are experiencing the same thing,  maybe you could demonstrate the problem to your experts-exchange colleagues? We have to get to the bottom of this!

Cheers!
   Shawn Halfpenny
0
ZifNabCommented:
Hi all,
When you reinstalled D3, had you also cleared the registry entries of D3? If like you say reïnstalling doesn't help, then it has something to do with registry entries which aren't properly cleared when uninstalling D3. I once had such a problem with a component. I also lost of hair with it. Even uninstalling and reinstalling the component didn't help. Until I searched the registry for all the entries of that component, there I found an entry which could be the problem. I changed it and viola everything was solved. I hope you have something on this information.
Regards, ZiF.
0
aztecAuthor Commented:
Hi Zifnab...
   Well, I did the uninstall as the Borland documentation specifies: To go into control panel, then Add/Remove programs and choose Delphi 3. Does this remove the registry entries? I don't know. If it doesn't, how does one remove them?

Regards,
   Shawn
0
aztecAuthor Commented:
FOUND THE PROBLEM!! It's a memory-related issue. I had one procedure where I was using a Blockread statement. I had declared a local buffer variable of array[0..131071] of char (128K). It seems that big buffer blew the debugging all the hell. Once I lowered that down to about 48K (49152 bytes), the debugging worked fine!

   Igor, give me an 'A' for this one!  :-)


Cheers!
   Shawn Halfpenny
0
interCommented:
Hi friend,

I am happy that you got it. Take these AAAAAAAAAAAAAAAAAAAAAAAA's and thanks for all experts. So we have a rule of thumb:

USE DYNAMIC ALOCATION FOR ARRAYS LARGER THAN 32k(TO BE SAFE) IN LOCAL PROCEDURES TO PRESERVE STACK AS FOLLOWS:

var
  BufPtr : Pointer; // or PChar;
begin
  GetMem(BufPtr, 128*1024);
  // open file here
  ....
  try
    BlockRead(BufPtr^,.....);
  finally
     FreeMem(BufPtr, 128*1024);
  end;
end;

Congratulations Again,
Igor
0
dvalineCommented:
If you haven't upgrade to Dlelphi 3.01 do so.  Delphi 3 clears the breakpoints when you close the IDE down.  Then when you open your project up there exists none of the breakpoints you set in your last debugging session.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
aztecAuthor Commented:
Give the A grade to Inter...I already have v3.02, dvaline, and it did not help.

Regards,
   Shawn
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Delphi

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.