Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: gdb-patches@sources.redhat.com, roland@redhat.com
Cc: mec.gnu@mindspring.com
Subject: Re: [committed testsuite patch] auxv.exp cascading failures
Date: Fri, 04 Jun 2004 23:44:00 -0000	[thread overview]
Message-ID: <20040604234409.146364B104@berman.michael-chastain.com> (raw)

It's PR gdb/1647, sorry if the number got detached somewhere.

I have a concern about this patch.  Code like this:

	-re "The program has no auxiliary information now.*$" {
 	    set bad 1
	    exp_continue
 	}
	...

It might consume an arbitrary number of characters with ".*",
maybe including a $gdb_prompt, maybe not.  Maybe even consuming
only part of the prompt!  We're at the mercy of OS buffering
for how many characters get delivered to expect at once.
Jim B has seen a lot of this lately.  So I don't think the ".*$"
is robust.

Michael C


             reply	other threads:[~2004-06-04 23:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-04 23:44 Michael Elizabeth Chastain [this message]
2004-06-05  0:11 ` Roland McGrath
  -- strict thread matches above, loose matches on Subject: below --
2004-06-04 21:37 Roland McGrath

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=20040604234409.146364B104@berman.michael-chastain.com \
    --to=mec.gnu@mindspring.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=roland@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