Debugger limitations


Is there some limit to the amount of symbol information that Delphi 1 can cope with? I've a large project ( 100+ units ) which has started to show debugging problems. The browser doesn't always know about a symbol when asked, and setting breakpoints doesn't always work on lines that are definitely being called. Yes, I've got all the debug flags ( except TDW ) on, yes, I'm building everything in sight, and no, I'm not optimising for load time.
Is this a known problem? Any way to fix ? Does delphi 2 have any such limits ?
LVL 12
andrewjbAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
mivConnect With a Mentor Commented:
It´s the length of the combined path of all your units which hits the roof in Delphi.
Shorten your paths or place all units in one dir near the root ex. c:\src\
You can, however, debug as it is now, just use a high level unit in the unit you wish to debug.
(Mail me if you did´nt get that :-) )

Ex.
UNIT LowLevelUnit;

USES
  HighLevelUnit;
0
 
sperlingCommented:
I've heard of this before, but haven't experienced it myself. I believe it has something to do with some internal limitations in the IDE debugger.

As far as I know you can't fix it... Consider DLLs is the best idea I can come up with.

I haven't experienced nor heard of any such problems in D2...


Regards,

Erik.
0
 
andrewjbAuthor Commented:
Current thoughts are that it might be something to do with the number of UNITS you've got, not their size. Although this sounds strange, someone else has indicated that a fix is to combine units into one.
0
Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
sperlingCommented:
That might work, if the problem is that the "namespace" of the debugger is too small. I've also seen comments indicating that keeping the units in the same directory would help.

Regards,

Erik.
0
 
nils pipenbrinckCommented:
At least I can help you with the breakpoint problem.

If you want to raise a breakpoint you can hardcode it into your
program. Just use these three lines:

  asm;
    int 3;
  end;

Int3 will be trapped by the debugger and will always work. But be sure you removed all these calls before you run the program without delphi. It'll crash!


0
 
andrewjbAuthor Commented:
Miv,
Interesting! Looks as though this might be helping. Two questions :
First, how did you find this out? Is there something documented somewhere, or was it by experimenting ?
Second, Sorry I didn't understand your 'include a high level unit' bit to get it to debug now. Could you explain again??

100 points are about to be yours!!.......

0
 
mivCommented:
Found out the hard way - 350 units, 250.000 lines of code...

The units first parsed when you compile is low level units - file handling, math routines etc.
Your Mainform is prob. a very high level unit. (My own definition).

If you wish to debug f.ex. a math unit, place your mainforms unit name in the uses statement of the implementation in the math unit and rebuild. That should do the trick.

Happy coding, I hope Delphi 2/3 solves the problem.
0
 
mivCommented:
What´s happening Andrew ?
0
 
andrewjbAuthor Commented:
Sorry, miv, just checking that it actually works.....
No problems so far. Still no reply from Borland!
Here are your points !
0
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.

All Courses

From novice to tech pro — start learning today.