From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: carlton@kealia.com, ezannoni@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa] pc bounds checking and namespaces
Date: Mon, 19 Jan 2004 06:06:00 -0000 [thread overview]
Message-ID: <20040119060642.DFA504B359@berman.michael-chastain.com> (raw)
Elena Zannoni writes:
> Again, a sanity check with 2.95 and -gdwarf-2 would be good.
I'm about to add carlton_dictionary-branch and drow-cplus-branch
to my test bed. That ought to help.
Instead of finding these problems at the point of merging
the branches onto HEAD, how about if we fix the branches so that
they have zero regressions versus gdb 6.0, and then merge the
branches?
Michael C
next reply other threads:[~2004-01-19 6:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-19 6:06 Michael Elizabeth Chastain [this message]
2004-01-19 18:16 ` Andrew Cagney
2004-01-19 19:18 ` David Carlton
-- strict thread matches above, loose matches on Subject: below --
2004-01-17 0:49 David Carlton
2004-01-19 0:05 ` Elena Zannoni
2004-01-19 18:36 ` David Carlton
2004-01-22 19:57 ` David Carlton
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=20040119060642.DFA504B359@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=carlton@kealia.com \
--cc=ezannoni@redhat.com \
--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