Message-Id: <m0zECl1-000S4fC@inti.gov.ar>
Comments: Authenticated sender is <salvador AT natacha DOT inti DOT gov DOT ar>
From: "Salvador Eduardo Tropea (SET)" <salvador AT inti DOT gov DOT ar>
Organization: INTI
To: Endlisnis <s257m AT unb DOT ca>, djgpp AT delorie DOT com
Date: Wed, 2 Sep 1998 10:17:28 +0000
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: RHIDE Can't debug this.  Was: Am I retarded -or- Why is my e
In-reply-to: <35EC63E9.4FD54CF0@unb.ca>
Precedence: bulk

Endlisnis <s257m AT unb DOT ca> wrote:

> Eli Zaretskii wrote:
> > Wait a minute.  You cannot debug it even under -O0?  If so, then this
> > has nothing to do with debugging optimized code.  Can you post a code
> > fragment that escapes debugging and explain how exactly does it
> > prevent you from debugging it?
> 	That is correct, even with -O0, it will skip break-points.  The problem is
> that it only seems to happen on large (600+ lines of code) files.  I can't get
> any simple examples to screw up.  But, I was able to sort-of do something.  I
> removed as much code as I could, and commented out the rest (removing the
> comments made the problem go away).  I have binarily attached it to this
> message, because re-formatting the text file seems to get rid of this
> phenomenon.  You can step through the code, but setting a break-point (by
> pressing F4) on line #132 (or #133) in the main file will cause the entire
> program to be executed, not stopping where I desired.  It includes another
> file, which I have provided.  I have experienced this multiple times, but
> always in large files.  Just save the 2 files in the same directory, and load
> 'fade9T.cc' and press F4 on line 132, and you watch it skip that point.  All
> the program does is print out 2 strings and 1 integer using cout.  It doesn't
> seem to matter if it is compiled in a project or not, and optimization level
> doesn't seem to matter.

Looks like a bug in gdb I tried using gdb and it ignored the breakpoint.
Using -gstabs+ I was able to stop the program in the line 133, not in 132.
I checked and the debug information for line 132 is in the .S file generated 
by gcc.

SET 
------------------------------------ 0 --------------------------------
Visit my home page: http://set-soft.home.ml.org/
or
http://www.geocities.com/SiliconValley/Vista/6552/
Salvador Eduardo Tropea (SET). (Electronics Engineer)
Alternative e-mail: set-soft AT usa DOT net set AT computer DOT org
ICQ: 2951574
Address: Curapaligue 2124, Caseros, 3 de Febrero
Buenos Aires, (1678), ARGENTINA
TE: +(541) 759 0013