Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <mec@shout.net>
To: msnyder@redhat.com
Cc: gdb-patches@sources.redhat.com, jason@redhat.com
Subject: Re: PATCH to testsuite/gdb.c++/namespace.exp
Date: Thu, 10 Jan 2002 10:06:00 -0000	[thread overview]
Message-ID: <200201101806.MAA25038@duracef.shout.net> (raw)

Michael Snyder wrote:
> Would it not be better, then, if the test accepted both 
>  \0 and \000?

I thought about that.  It would be better; and if I had written the
patch, I would have written it that way.

But there's so much to do in C++ land, and so little time, that I'd
rather let it be.  I'm 100x more worried about things like this:

  # native i686-pc-linux-gnu
  # gdb HEAD (2001-12-22)
  # gcc 2.95.3
  # -gdwarf-2
  print this^M
  $1 = (A * const) 0xa^M
  (gdb) PASS: gdb.c++/method.exp: print this (in foo)

gdb is printing an incorrect value and the testsuite does not catch it.
This is a bug in gdb and a shortfall in the testsuite and it affects
real users.

I am organizing my life so that I have more time to care about bugs
like that.  That means conserving attention on lesser things, to their
detriment.  It's an attention-triage question.

But if this issue bothers you enough to submit a patch, I will approve it.

Michael C


             reply	other threads:[~2002-01-10 18:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-10 10:06 Michael Elizabeth Chastain [this message]
2002-01-10 10:28 ` Michael Snyder
  -- strict thread matches above, loose matches on Subject: below --
2002-01-10 10:34 Michael Elizabeth Chastain
2002-01-10  8:50 Michael Elizabeth Chastain
2002-01-10  9:36 ` Michael Snyder
2002-01-10  5:20 Jason Merrill

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=200201101806.MAA25038@duracef.shout.net \
    --to=mec@shout.net \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jason@redhat.com \
    --cc=msnyder@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