From: Michael Elizabeth Chastain <mec@shout.net>
To: gdb-patches@sources.redhat.com
Subject: Re: [patch] gdb.c++/local.exp: make usable with gcc
Date: Tue, 09 Apr 2002 20:56:00 -0000 [thread overview]
Message-ID: <200204100356.g3A3ul626760@duracef.shout.net> (raw)
Committed.
Two bug reports to follow.
Michael C
2002-04-08 Michael Chastain <mec@shout.net>
* gdb.c++/local.cc (main): Move call to marker1() inside nested
scope so that the nested scope tests will make sense.
* gdb.c++/local.exp: Write patterns that actually work with gcc
(the HP patterns "were never known to work with gcc").
Keep the old aCC patterns too.
next reply other threads:[~2002-04-10 3:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-09 20:56 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-12 11:51 Michael Elizabeth Chastain
2002-04-08 20:15 Michael Elizabeth Chastain
2002-04-08 21:39 ` Daniel Jacobowitz
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=200204100356.g3A3ul626760@duracef.shout.net \
--to=mec@shout.net \
--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