Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: gdb-patches@sources.redhat.com
Cc: Fernando Nasser <fnasser@redhat.com>
Subject: Re: RFA: add testsuite function for answering internal error questions
Date: Fri, 22 Nov 2002 11:36:00 -0000	[thread overview]
Message-ID: <vt265up2yzv.fsf@zenia.red-bean.com> (raw)
In-Reply-To: <vt2k7j53098.fsf@zenia.red-bean.com>


I've reverted the change from the 5.3 branch, too.  Fernando needs to
approve them for both the trunk and the branch.

Jim Blandy <jimb@redhat.com> writes:

> Actually, I've reverted this, and the other change to
> gdb.base/step-line.exp.  Daniel J. pointed out that they've been
> committed to the 5.3 branch, but weren't present on the trunk; in a
> sleepy haze, it seemed to me that I should just check them in.
> 
> Fernando, any comment on these?  The companion patch is:
> "RFA: test macro expansion in presence of #line directives"
> 
> Jim Blandy <jimb@redhat.com> writes:
> 
> > I've committed this.
> > 
> > Jim Blandy <jimb@redhat.com> writes:
> > 
> > > [re-posting: bad changelog entry.]
> > > 
> > > 2002-11-06  Jim Blandy  <jimb@redhat.com>
> > > 
> > > 	* lib/gdb.exp (gdb_internal_error_regexp): New variable.
> > > 	(gdb_internal_error_resync): New procedure.
> > >         (gdb_test): If the command results in an internal error,
> > >         answer GDB's questions until we get back to a prompt.


  reply	other threads:[~2002-11-22 19:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-06 12:28 Jim Blandy
2002-11-21 23:01 ` Jim Blandy
2002-11-22 11:09   ` Jim Blandy
2002-11-22 11:36     ` Jim Blandy [this message]
2002-12-03  9:00 ` Fernando Nasser
2003-01-14 18:50   ` Fernando Nasser
2003-02-04 22:33     ` Jim Blandy
2003-09-22 23:46     ` # " Jim Blandy
2003-09-23 23:48       ` Andrew Cagney

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=vt265up2yzv.fsf@zenia.red-bean.com \
    --to=jimb@redhat.com \
    --cc=fnasser@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