Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Randolph Chung <randolph@tausq.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfa] tweak patterns for annota3.exp
Date: Mon, 06 Dec 2004 02:56:00 -0000	[thread overview]
Message-ID: <20041206024904.GA30704@nevyn.them.org> (raw)
In-Reply-To: <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


  reply	other threads:[~2004-12-06  2:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-06  2:49 Randolph Chung
2004-12-06  2:56 ` Daniel Jacobowitz [this message]
2004-12-06  3:03   ` Randolph Chung
2004-12-06  3:06     ` Daniel Jacobowitz
2004-12-06  3:27       ` Randolph Chung
2004-12-06 20:52       ` Randolph Chung

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20041206024904.GA30704@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=randolph@tausq.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox