Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: Siva Chandra <sivachandra@google.com>,
	gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH v4] Make chained function calls in expressions work
Date: Wed, 12 Nov 2014 17:29:00 -0000	[thread overview]
Message-ID: <CADPb22R-E+8QL6ww8om4oNYevLOrxSuSerMOd=A6i6kbEK409A@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:
> [...]
> One catch is that if all calls end up being xmethod calls then we
> won't need the dummy frame.
> I'm not sure if there'd be any real harm in setting one up though.

Heh, unless one is working with a core file.
Maybe the outer dummy frame could still exist, if in some modified form.


  reply	other threads:[~2014-11-12 17:29 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 [this message]
2014-11-13  3:00                       ` Siva Chandra

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='CADPb22R-E+8QL6ww8om4oNYevLOrxSuSerMOd=A6i6kbEK409A@mail.gmail.com' \
    --to=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sivachandra@google.com \
    --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