This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: FYI: [python/Ada] gdb.lookup_type fails to looking primitive type
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Doug Evans <dje at google dot com>
- Cc: gdb-patches <gdb-patches at sourceware dot org>
- Date: Wed, 14 Jan 2015 09:00:51 +0400
- Subject: Re: FYI: [python/Ada] gdb.lookup_type fails to looking primitive type
- Authentication-results: sourceware.org; auth=none
- References: <1421083588-927-1-git-send-email-brobecker at adacore dot com> <CADPb22RQrxP8oESnjwnxm-Z8HYs=9inFE_JPStmcBCqOy7ZMaA at mail dot gmail dot com> <20150113094426 dot GE8167 at adacore dot com> <CADPb22T8FM7a0GDVqig79OhfG_9juhWZ9L1wu3XO-HF++SDZDg at mail dot gmail dot com>
> > gdb/testsuite/ChangeLog:
> >
> > * gdb.python/py-lookup-type.exp: New file.
>
> Not that I'm expecting anyone to go back and change things,
> but maybe for future reference it'd be better to print the result
> and record the expected output, instead of expecting no output.
> Performing a lookup action, and then expecting no output,
> is just too confusing to me.
The only issue I have with that is that I'd like to do something
whose behavior is defined. Looking at the GDB manual, I can't see
anything said about what to expect when converting a gdb.Type to
a string... If we clarify that, I have no problem adding the extra
"print" in the test.
--
Joel