From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,ef1e0eb6cfbf8bfb X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news3.google.com!news4.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local02.nntp.dca.giganews.com!nntp.comcast.com!news.comcast.com.POSTED!not-for-mail NNTP-Posting-Date: Mon, 24 Jul 2006 20:42:00 -0500 From: "Steve" Newsgroups: comp.lang.ada References: <1153733130.374572.91400@p79g2000cwp.googlegroups.com> Subject: Re: Can't set breakpoints Date: Mon, 24 Jul 2006 18:42:20 -0700 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.2869 X-RFC2646: Format=Flowed; Original X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 Message-ID: NNTP-Posting-Host: 24.20.111.245 X-Trace: sv3-0AI0GfcM5iuu5AkIBJL+KBA/73vpz8mU1mEz+pZgosGDYMZrHt+bothy1Onp9GYbHHrdYtsA2p3Ek2x!Wo4lasnvD5uVRWYvJ15s9atHSj5Xvo/sbK+L7MjzPpKfP4o0kn7JXZ1FjXKF39pvOWUhqQmYEvtw!iRc9ybtTcVHsHA== X-Complaints-To: abuse@comcast.net X-DMCA-Complaints-To: dmca@comcast.net X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.32 Xref: g2news2.google.com comp.lang.ada:5910 Date: 2006-07-24T18:42:20-07:00 List-Id: wrote in message news:1153733130.374572.91400@p79g2000cwp.googlegroups.com... > I'm using ObjectADA version 7.2.2. > Of late, i'm not able to set breakpoints. The error message that pops > up when i try to set breakpoints is not very helpful; it just says > "cannot set breakpoint". > I was able to set breakpoints earlier; it's just that the number of > lines of code and hence the size of the code have increased. > If it's of any help, the size of my code is 184KB and the size of the > executable is 800KB. Assuming you're using the Professional edition, it is not a code size or executable size issue. I have successfully debugged exectables that are several megabytes with over 100K SLOC. I do however sometimes run into difficulty debugging. The most common problem is when the debugger gets out of sync with the source code... usually off by a line or two. While I haven't identified a particular cause, it is more prevalent in larger source modules. You might try increasing the stack size. I remember having problems when the stack size was too small, but it has been so long I can't remember the nature of the problem. Steve (The Duck) > > Please help. >