From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: Re: [RFA] Make symbol completion language-specific
Date: Wed, 30 Jan 2008 20:43:00 -0000 [thread overview]
Message-ID: <20080130203138.GE12387@adacore.com> (raw)
In-Reply-To: <20080129172800.GA3773@caradoc.them.org>
> > 1. How does someone verify that a GDB command does not return
> > any output. Do we really have to do it "manually" (using
> > gdb_send et al)? Right now, there is a hole in my testcase
> > regarding this, and I need to fix it before I commit it.
>
> Pretty much, though I think you could do it with gdb_test_multiple;
> see how lib/mi-support.exp does it. MI tests are anchored by default.
> There may be more trouble doing it for the CLI, though, because
> readline puts extra stuff in the output sometimes.
Will take a look, thanks. I suggest we add a new routine inside gdb.exp
that does check that a given command doesn't return any output. Would
that be ok?
> Also see gdb_expect_list, which is similar. I think that the way
> you've written it lends to things being too far indented, which will
> be hard to read...
Thanks for the tip! I'll have a look as well.
> > +struct string_vector
> > +{
> > + char **array; /* The vector itself. */
> > + int index; /* Index of the next available element in the array. */
> > + size_t size; /* The number of entries allocated in the array. */
> > +};
>
> We have a generic VEC nowadays.
Argh, right. I will rewrite the patch to use a VEC, remove the FIXME,
and resubmit.
Thanks,
--
Joel
next prev parent reply other threads:[~2008-01-30 20:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-28 13:07 Joel Brobecker
2008-01-29 17:35 ` Daniel Jacobowitz
2008-01-30 20:43 ` Joel Brobecker [this message]
2008-01-30 21:25 ` Daniel Jacobowitz
2008-02-04 23:15 ` Joel Brobecker
2008-02-04 23:30 ` Daniel Jacobowitz
2008-02-05 22:32 ` Joel Brobecker
2008-02-06 2:40 ` [RFA/commit/Ada] Replace home-made string_vector struct with VEC Joel Brobecker
2008-02-06 2:48 ` Daniel Jacobowitz
2008-02-07 19:14 ` Joel Brobecker
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=20080130203138.GE12387@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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