Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Doug Evans <dje@google.com>,
	       Martin Galvan <martin.galvan@tallertechnologies.com>
Cc: Ulrich Weigand <uweigand@de.ibm.com>,
	       gdb-patches <gdb-patches@sourceware.org>,
	Eli Zaretskii <eliz@gnu.org>,
	       Daniel Gutson <daniel.gutson@tallertechnologies.com>
Subject: Re: [PING][RFC][PATCH v2] Python API: add gdb.stack_may_be_invalid
Date: Wed, 12 Nov 2014 17:20:00 -0000	[thread overview]
Message-ID: <546396DC.1020803@redhat.com> (raw)
In-Reply-To: <CADPb22R+QxbZGHJxi1nC_idq3NmOnaDmGS_JLc_Wyio1m2LXBQ@mail.gmail.com>

On 11/12/2014 05:06 PM, Doug Evans wrote:
> 
> Plus the name "stack is destroyed" is confusing.
> This function is just a wrapper around gdbarch_in_function_epilogue_p
> so I'd just call it in_function_epilogue_p (or
> gdbpy_in_function_epilogue_p or some such).

Can we agree to rename the gdbarch hook instead?
The function does _not_ return whether the PC is in the epilogue.

https://sourceware.org/ml/gdb-patches/2014-10/msg00590.html

Thanks,
Pedro Alves


  reply	other threads:[~2014-11-12 17:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-07 13:32 Martin Galvan
2014-11-07 17:09 ` Pedro Alves
2014-11-07 17:18   ` Martin Galvan
2014-11-07 17:27 ` Ulrich Weigand
2014-11-07 17:37   ` Martin Galvan
2014-11-12 15:55     ` Martin Galvan
2014-11-12 17:06       ` Doug Evans
2014-11-12 17:20         ` Pedro Alves [this message]
2014-11-12 17:26           ` Martin Galvan
2014-11-12 17:32           ` Doug Evans
2014-11-12 17:24         ` Martin Galvan

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=546396DC.1020803@redhat.com \
    --to=palves@redhat.com \
    --cc=daniel.gutson@tallertechnologies.com \
    --cc=dje@google.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=martin.galvan@tallertechnologies.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