Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Paul Gilliam <pgilliam@us.ibm.com>
To: gdb-patches@sources.redhat.com
Cc: Daniel Jacobowitz <drow@false.org>
Subject: Re: [PATCH] Fixes testsuit/gdb.base/annota1.exp
Date: Wed, 27 Apr 2005 20:02:00 -0000	[thread overview]
Message-ID: <200504271304.14413.pgilliam@us.ibm.com> (raw)
In-Reply-To: <20050427154758.GD7765@nevyn.them.org>

On Wednesday 27 April 2005 08:47, Daniel Jacobowitz wrote:
> On Fri, Apr 15, 2005 at 03:37:55PM -0800, Paul Gilliam wrote:
> > OK.  this is in partial responce to:
> >         http://sourceware.org/ml/gdb-patches/2005-04/msg00145.html
> > 
> > There were two problems with gdb.base/annota1.exp.  This patch is only for the second one.
> > 
> > The problem here is that a bug in backtrace was causing a false nagitive in gdb.base/annota1.exp,
> > so the feature being tested was OK, but was being failed due to some other bug that caused the
> > backtrace to not stop at the end.
> > 
> > NOTE: this also allows for 'doc symbols' like '.printf'.  I understand that these are going away
> > soon, but an extra '\.?' shouldn't hurt anything.
> > 
> > -=# Paul #=-
> > 
> > --
> > 2005-04-15  Paul Gilliam  <pgilliam@us.ibm.com>
> > 
> > 	* gdb.base/annota1.exp: Deal with backtrace 'skidding' past
> > 	top-of-stack due to a bug unrealted to annotation.
> 
> I would strongly prefer not to include this one.  This isn't a unit
> testsuite; all GDB tests cover multiple features.  Some backtrace bugs
> only show up in these testcases, because they're so picky.

OK, I understand.

I withdraw this patch.

> 
> You didn't mention when resubmitting these patches that there were
> objections to them.  That's kind of important.  I see that Andrew had
> the same objection that I do.
> 

Opps, Sorry.  I'll be more carefull next time


  reply	other threads:[~2005-04-27 20:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-07 17:27 Paul Gilliam
2005-04-14 19:36 ` Daniel Jacobowitz
2005-04-15 23:03   ` [PATCH] add new .exp file and a 'c' testfile to test backtrace limits etc Paul Gilliam
2005-04-30 18:49     ` Daniel Jacobowitz
2005-05-28 23:42       ` Daniel Jacobowitz
2005-04-15 23:38   ` [PATCH] Fixes testsuit/gdb.base/annota1.exp to deal with 'Breakpoint address adjusted' Paul Gilliam
2005-04-27 15:43     ` Daniel Jacobowitz
2005-04-27 21:47       ` [COMMIT] " Paul Gilliam
2005-04-15 23:38   ` [PATCH] Fixes testsuit/gdb.base/annota1.exp Paul Gilliam
2005-04-27 15:49     ` Daniel Jacobowitz
2005-04-27 20:02       ` Paul Gilliam [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-09-21 21:43 Paul Gilliam
2004-09-22 14:01 ` Andrew Cagney
2004-09-22 16:56   ` Paul Gilliam
2004-09-22 19:54     ` Andrew Cagney
2004-09-23  2:13       ` Paul Gilliam
2004-09-23 17:08         ` Michael Chastain
2004-09-23 17:25         ` Michael Chastain
2004-09-23 17:25 ` Michael Chastain

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=200504271304.14413.pgilliam@us.ibm.com \
    --to=pgilliam@us.ibm.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    /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