This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PING][RFC][PATCH v2] Python API: add gdb.stack_may_be_invalid
- From: Pedro Alves <palves at redhat dot com>
- To: Doug Evans <dje at google dot com>, Martin Galvan <martin dot galvan at tallertechnologies dot com>
- Cc: Ulrich Weigand <uweigand at de dot ibm dot com>, gdb-patches <gdb-patches at sourceware dot org>, Eli Zaretskii <eliz at gnu dot org>, Daniel Gutson <daniel dot gutson at tallertechnologies dot com>
- Date: Wed, 12 Nov 2014 17:20:28 +0000
- Subject: Re: [PING][RFC][PATCH v2] Python API: add gdb.stack_may_be_invalid
- Authentication-results: sourceware.org; auth=none
- References: <CAOKbPbZd+ppseGQW2OirBm4y5O=LgUMP-Pf8=RF00hnPOuMutw at mail dot gmail dot com> <201411071727 dot sA7HRNIQ007851 at d03av02 dot boulder dot ibm dot com> <CAOKbPbY24zgvHdmAYQvR6H=sCsF6ixzwvwdbhPpBkcdcsMotiw at mail dot gmail dot com> <CAOKbPbaa2jZonzn-tcH9C8ge5AVUJHJeREwWNLOokFqr7dd6vw at mail dot gmail dot com> <CADPb22R+QxbZGHJxi1nC_idq3NmOnaDmGS_JLc_Wyio1m2LXBQ at mail dot gmail dot 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