This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [patch/rfa] tweak patterns for annota3.exp
- From: Daniel Jacobowitz <drow at false dot org>
- To: Randolph Chung <randolph at tausq dot org>
- Cc: gdb-patches at sources dot redhat dot com
- Date: Sun, 5 Dec 2004 21:49:04 -0500
- Subject: Re: [patch/rfa] tweak patterns for annota3.exp
- References: <20041206021944.GX6359@tausq.org>
On Sun, Dec 05, 2004 at 06:19:44PM -0800, Randolph Chung wrote:
> Note: i don't really understand the annotation stuff in gdb...
>
> I've been getting FAILs for this test for a long time, and i never quite
> understood why....
>
> In the first case, i see an extra \r\n between "breakpoint 2" and
> "Breakpoint 2, ...". Also on hppa-linux, the backtrace prints out the
Are you sure there's nothing but an extra \r\n? It definitely passes
for others, so I'd like to know where that came from.
> address of the signal handler... i.e. i get
>
> #0 0x000105d4 in handle_USR1 (sig=16) at /home/tausq/gdb/gdb-cvs/gdb/testsuite/gdb.base/annota3.c:18
>
> instead of what the script expected, which seems to be
> #0 handle_USR1 (sig=16) at /home/tausq/gdb/gdb-cvs/gdb/testsuite/gdb.base/annota3.c:18
The extra address means we didn't put the breakpoint at the beginning
of a line. This could be a prologue skipper bug, a GCC bug, a general
the-world-hates-us bug, or we could decide it wasn't a bug. The
testsuite seems to contain examples of all of the above.
--
Daniel Jacobowitz