From: Tom Tromey <tom@tromey.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
Justin Paston-Cooper <paston.cooper@gmail.com>,
gdb@sourceware.org
Subject: Re: Command to break before exiting stack frame?
Date: Tue, 19 Mar 2019 15:35:00 -0000 [thread overview]
Message-ID: <87r2b2x4gp.fsf@tromey.com> (raw)
In-Reply-To: <431d242053ca491be67a21d0d95b71a4@polymtl.ca> (Simon Marchi's message of "Sat, 16 Mar 2019 20:23:00 -0400")
>>>>> "Simon" == Simon Marchi <simon.marchi@polymtl.ca> writes:
Simon> I suppose that the list of all function exit points (regardless of
Simon> whether it is a jump or real return) is an information that the
Simon> compiler could theoretically produce and encode in the DWARF
Simon> information?
Yes, the line number program can include epilogue markers.
I don't believe gcc emits these, though.
This feature would be a good one to have in gdb.
Fixing it in the compiler is probably the best way to do it, though I
don't know whether it's the simplest way.
Tom
prev parent reply other threads:[~2019-03-19 15:35 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
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 [this message]
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=87r2b2x4gp.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb@sourceware.org \
--cc=paston.cooper@gmail.com \
--cc=schwab@linux-m68k.org \
--cc=simon.marchi@polymtl.ca \
/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