Date:	Wed, 22 Aug 2001 18:42:45 +0300
From:	"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender:	halo1 AT zahav DOT net DOT il
To:	djgpp-workers AT delorie DOT com
Message-Id:	<5137-Wed22Aug2001184244+0300-eliz@is.elta.co.il>
X-Mailer:	Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.9
In-reply-to:	<3B837ED5.9470.9EB9A@localhost> (snowball3@bigfoot.com)
Subject:	Re: rhgdb and dwarf2 oddity
References:	<3B82C0E4 DOT 31510 DOT 103144 AT localhost> (snowball3 AT bigfoot DOT com) <3B837ED5 DOT 9470 DOT 9EB9A AT localhost>
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> From: "Mark E." <snowball3 AT bigfoot DOT com>
> Date: Wed, 22 Aug 2001 09:43:49 -0400
> 
> > Does this happen with GDB as well?
> 
> No, but I also don't know what the equivalent sequence of commands would be. 
> If load the program and set a breakpoint, gdb does it without complaint.

I understand that the problem happens in RHGDB only when you restart
the debuggee.  If so, the equivalent sequence in GDB would be to let
the program run to completion, then type "run" again.  This restarts
the program with the same argv[] array as before, and the breakpoints
you've set should still be valid.

> So the current version of 2.11.2 has a rather serious 
> problem with dwarf2 support.

Perhaps a fixed release of Binutils could be available by the time
GDB 5.1 is out.  (I estimate that will take at least another month.)

- Raw text -