On Thu, 21 Mar 2019 at 09:11, Justin Paston-Cooper
wrote:
>
> On Thu, 21 Mar 2019 at 08:23, Richard Biener
> wrote:
> >
> > On Wed, Mar 20, 2019 at 8:05 PM Tom Tromey wrote:
> > >
> > > >>>>> "Segher" == Segher Boessenkool
On Thu, 21 Mar 2019 at 08:23, Richard Biener wrote:
>
> On Wed, Mar 20, 2019 at 8:05 PM Tom Tromey wrote:
> >
> > > "Segher" == Segher Boessenkool writes:
> >
> > >> Section 6.2.5.2 outlines the line number information state machine's
> > >> opcodes. One of them is "DW_LNS_set_epilogue_begin
On Wed, 20 Mar 2019 at 08:31, Richard Biener wrote:
>
> On Tue, Mar 19, 2019 at 9:38 PM Justin Paston-Cooper
> wrote:
> >
> > Hello,
> >
> > In my message https://sourceware.org/ml/gdb/2019-03/msg00042.html to
> > the gdb mailing list, I asked whether
On Tue, 19 Mar 2019 at 22:40, Florian Weimer wrote:
> * Justin Paston-Cooper:
>
> > On Tue, 19 Mar 2019 at 21:52, Florian Weimer wrote:
> >>
> >> * Justin Paston-Cooper:
> >>
> >> > On Tue, 19 Mar 2019 at 21:29, Florian Weim
On Tue, 19 Mar 2019 at 21:52, Florian Weimer wrote:
>
> * Justin Paston-Cooper:
>
> > On Tue, 19 Mar 2019 at 21:29, Florian Weimer wrote:
> >>
> >> * Justin Paston-Cooper:
> >>
> >> > Tom Tromey suggested in that thread that this would be
On Tue, 19 Mar 2019 at 21:29, Florian Weimer wrote:
>
> * 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
Hello,
In my message https://sourceware.org/ml/gdb/2019-03/msg00042.html to
the gdb mailing list, I asked whether it would be possible to
implement a command which breaks at all exit points of the current
stack frame. This would be very useful for evaluating a function's
final state before it retu
