This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Indicating function exit points in debug data
- From: Florian Weimer <fw at deneb dot enyo dot de>
- To: Justin Paston-Cooper <paston dot cooper at gmail dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: Tue, 19 Mar 2019 22:29:48 +0100
- Subject: Re: Indicating function exit points in debug data
- References: <CAEndGgTw07DSdK+O+ydvZo+SBoZvsaQJKoLxZ0SSULzB8s=1nw@mail.gmail.com>
* Justin Paston-Cooper:
> Tom Tromey suggested in that thread that this would be quite easy on
> gdb's side if gcc indicates exit locations in the DWARF data, for
> instance in the C case, it would indicate the locations of return
> statements. On a related note, he mentions that the "finish" command
> does not work for inlined functions because the compiler does not emit
> the required information.
What about calls to noreturn functions? I assume they would need
breakpoints as well. It could be tricky if those are only called
indirectly, I assume.