This is the mail archive of the
mailing list for the GDB project.
Re: Command to break before exiting stack frame?
- From: Simon Marchi <simon dot marchi at polymtl dot ca>
- To: Andreas Schwab <schwab at linux-m68k dot org>
- Cc: Justin Paston-Cooper <paston dot cooper at gmail dot com>, gdb at sourceware dot org
- Date: Sat, 16 Mar 2019 20:23:00 -0400
- Subject: Re: Command to break before exiting stack frame?
- References: <CAEndGgToidTsVOhwvV=9RFf=nYWwK+3_qWheYJ8JtoNez3Pq8w@mail.gmail.com> <email@example.com>
On 2019-03-16 20:00, Andreas Schwab wrote:
On Mär 16 2019, Justin Paston-Cooper <firstname.lastname@example.org> wrote:
I can't imagine that I am the first person to suggest or request this.
there any architectural or practical reasons as to why this is might
There may not even be a place where the frame is exited in the current
function due to tail call. Also, inline literal pools or jump tables
can result in false positives when searching for return insns.
I suppose that the list of all function exit points (regardless of
whether it is a jump or real return) is an information that the compiler
could theoretically produce and encode in the DWARF information?