This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: How do I get regexp from expect at gdb_expect?
- From: Bob Rossi <bob at brasko dot net>
- To: GDB <gdb at sources dot redhat dot com>
- Date: Tue, 1 Feb 2005 09:20:08 -0500
- Subject: Re: How do I get regexp from expect at gdb_expect?
- References: <20050129025743.GA4053@white> <200501290309.j0T39F1i020834@tully.CS.Berkeley.EDU> <20050131150652.GA7955@white> <20050131162609.GA19459@nevyn.them.org> <20050131211042.GA8411@white> <20050131212122.GA10092@nevyn.them.org> <20050131220050.GB8411@white> <20050131220354.GA11955@nevyn.them.org> <20050131221247.GC8411@white> <20050201035236.GA24182@nevyn.them.org>
On Mon, Jan 31, 2005 at 10:52:36PM -0500, Daniel Jacobowitz wrote:
> On Mon, Jan 31, 2005 at 05:12:47PM -0500, Bob Rossi wrote:
> > On Mon, Jan 31, 2005 at 05:03:54PM -0500, Daniel Jacobowitz wrote:
> > > On Mon, Jan 31, 2005 at 05:00:50PM -0500, Bob Rossi wrote:
> > > > It also tighten's up the MI output command matching, I honestly don't
> > > > know how the -break-delete was getting eaten in the regular expression,
> > > > unless $pattern happened to have a .*. Oops, in that case, I guess we
> > > > aren't really validation much, anything could have come out of GDB, and
> > > > it probably would have passed.
> > >
> > > Your pattern doesn't start with an anchor. -break-delete wasn't eaten;
> > > we just started matching after it.
> >
> > Please forgive my ignorance, I've been reading online as much as
> > possible to understand tcl/expect ...
> >
> > I understand how anchors work, however, I didn't realize you could start
> > matching in the middle of what the 'buffer' is. If it started matching
> > after it, does that mean it's skipped forever? So basically, you can
> > match a subset of the output, and the rest is lost (never matched)?
>
> That's correct.
>
> > If that's the case, the testsuite for the MI is matching even less than
> > I thought. GDB could output almost anything, but then just have to match
> > the last string, and the testcase would pass, correct?
>
> Yes. Sometimes this is even deliberate - fixing it would be
> interesting, but probably quite hard.
Could we have GDB turn off echo'ing with an MI command.
-mi-disable-echo
I think that would fix this entire problem.
Thanks,
Bob Rossi