Date: Thu, 2 Mar 2000 19:04:49 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
cc: djgpp-workers AT delorie DOT com
Subject: Re: Debugging difficulties with GCC 2.95.2
In-Reply-To: <Pine.LNX.4.10.10003021554350.11752-100000@acp3bf>
Message-ID: <Pine.SUN.3.91.1000302190325.28584B@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: dj-admin AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Thu, 2 Mar 2000, Hans-Bernhard Broeker wrote:

> 2000-02-17  Mark Mitchell  <mark AT codesourcery DOT com>
> 
>         * function.c (thread_prologue_and_epilogue_insns): Put a line note
>         after the prologue.
> 
> has broken the GDB testsuite. 
> 
> I think that change tries to work around the bug we've been talking about,
> here: that there currently is no .ln between the prologue and the 'real'
> code of the function. Seems it's outputting the wrong line number (of the
> opening brace, instead of the first line of active code), confusing the
> GDB test scripts.

Yes, most GDB test scripts begin with the following sequence:

	b main
	run
	next

and assume they are now after the first executable line of `main'.

> I'll put a mail to the gdb mailing list, describing my results.

Thanks!