From: Joel Brobecker <brobecker@adacore.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: FYI: [python/Ada] gdb.lookup_type fails to looking primitive type
Date: Wed, 14 Jan 2015 05:01:00 -0000 [thread overview]
Message-ID: <20150114050051.GH8167@adacore.com> (raw)
In-Reply-To: <CADPb22T8FM7a0GDVqig79OhfG_9juhWZ9L1wu3XO-HF++SDZDg@mail.gmail.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
next prev parent reply other threads:[~2015-01-14 5:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-12 17:26 Joel Brobecker
2015-01-12 17:59 ` Doug Evans
2015-01-13 9:44 ` Joel Brobecker
2015-01-13 20:57 ` Doug Evans
2015-01-14 5:01 ` Joel Brobecker [this message]
2015-01-21 9:44 ` Joel Brobecker
2015-01-21 17:52 ` Doug Evans
2015-01-26 10:51 ` pushed: " 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=20150114050051.GH8167@adacore.com \
--to=brobecker@adacore.com \
--cc=dje@google.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