From: Joel Brobecker <brobecker@adacore.com>
To: Simon Marchi <simon.marchi@ericsson.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PUSHED] Handle OP_STRING in dump_subexp_body_standard
Date: Tue, 15 Jul 2014 16:07:00 -0000 [thread overview]
Message-ID: <20140715155644.GI4888@adacore.com> (raw)
In-Reply-To: <53C54C6E.40607@ericsson.com>
> Oh, indeed. That would go in gdb.base/debug-expr.exp I presume.
Looks like a great place for it, indeed.
Thanks!
--
Joel
prev parent reply other threads:[~2014-07-15 15:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 15:33 Simon Marchi
2014-07-15 15:44 ` Joel Brobecker
2014-07-15 15:45 ` Simon Marchi
2014-07-15 16:07 ` Joel Brobecker [this message]
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=20140715155644.GI4888@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@ericsson.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