From: Simon Marchi <simon.marchi@polymtl.ca>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Justin Paston-Cooper <paston.cooper@gmail.com>, gdb@sourceware.org
Subject: Re: Command to break before exiting stack frame?
Date: Sun, 17 Mar 2019 00:23:00 -0000 [thread overview]
Message-ID: <431d242053ca491be67a21d0d95b71a4@polymtl.ca> (raw)
In-Reply-To: <87va0i74jq.fsf@igel.home>
On 2019-03-16 20:00, Andreas Schwab wrote:
> On Mär 16 2019, Justin Paston-Cooper <paston.cooper@gmail.com> wrote:
>
>> I can't imagine that I am the first person to suggest or request this.
>> Are
>> there any architectural or practical reasons as to why this is might
>> be
>> difficult?
>
> 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.
>
> Andreas.
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?
Simon
next prev parent reply other threads:[~2019-03-17 0:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-16 23:15 Justin Paston-Cooper
2019-03-17 0:01 ` Andreas Schwab
2019-03-17 0:23 ` Simon Marchi [this message]
2019-03-17 13:59 ` Justin Paston-Cooper
2019-03-19 15:42 ` Tom Tromey
2019-03-19 20:44 ` Justin Paston-Cooper
2019-03-19 15:35 ` Tom Tromey
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=431d242053ca491be67a21d0d95b71a4@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb@sourceware.org \
--cc=paston.cooper@gmail.com \
--cc=schwab@linux-m68k.org \
/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