From: Siva Chandra <sivachandra@google.com>
To: Doug Evans <dje@google.com>
Cc: Ulrich Weigand <uweigand@de.ibm.com>,
gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH v4] Make chained function calls in expressions work
Date: Thu, 13 Nov 2014 03:00:00 -0000 [thread overview]
Message-ID: <CAGyQ6gwGg2d+3iLjCtsBrS2fy6hkrRS_qKs49BJDV1h5qaOHQA@mail.gmail.com> (raw)
In-Reply-To: <CADPb22S1XgTw060B2C18-DvqAxmuQ3L2QFPWRpygPitSyVKKHg@mail.gmail.com>
On Wed, Nov 12, 2014 at 8:08 AM, Doug Evans <dje@google.com> wrote:
> On Tue, Nov 11, 2014 at 7:21 AM, Ulrich Weigand <uweigand@de.ibm.com> wrote:
>> [...]
>> The most cleanly "correct" solution would probably be to cache the temporaries
>> on the *dummy frame*, because that is the frame associated with all the
>> GDB-generated content on the stack, and the dummy_frame struct does persist
>> a bit longer than the frame struct. However, getting there would still be
>> a bit more difficult, since we'd first have to arrange for a dummy frame to
>> persist over multiple inferior call invocations. Currently, the dummy frame
>> is automatically popped in infrun as soon as the call returns.
>
> Hi.
> OOC, Could one do a quick pass over the parsed expression to first see
> if there are any function calls, and if so wrap the entire expression
> evaluation in a routine that manages the creation/cleanup of an
> "outer" dummy frame?
If I understand you correctly, isn't the general direction of the
proposed solution already this? It differs in the fact that the
"outer" frame is adjusted as required by the expression instead of
"fixing" it before the evaluation of the expression. The notion of an
"outer" frame is not explicitly present though.
prev parent reply other threads:[~2014-11-13 3:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-25 14:24 Siva Chandra
2014-11-03 14:35 ` Siva Chandra
2014-11-03 14:43 ` Ulrich Weigand
2014-11-03 19:55 ` Siva Chandra
2014-11-03 21:22 ` Siva Chandra
2014-11-04 13:43 ` Ulrich Weigand
2014-11-04 15:08 ` Siva Chandra
2014-11-04 15:40 ` Ulrich Weigand
2014-11-04 13:38 ` Ulrich Weigand
2014-11-04 14:26 ` Siva Chandra
2014-11-04 14:59 ` Ulrich Weigand
2014-11-04 15:23 ` Siva Chandra
2014-11-04 15:40 ` Ulrich Weigand
2014-11-11 14:55 ` Siva Chandra
2014-11-11 15:00 ` Siva Chandra
2014-11-11 15:21 ` Ulrich Weigand
2014-11-11 17:05 ` Siva Chandra
2014-11-12 16:08 ` Doug Evans
2014-11-12 17:29 ` Doug Evans
2014-11-13 3:00 ` Siva Chandra [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=CAGyQ6gwGg2d+3iLjCtsBrS2fy6hkrRS_qKs49BJDV1h5qaOHQA@mail.gmail.com \
--to=sivachandra@google.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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