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 writes:
> > >
> > > >> Section 6.2.5.2 outlines the line number informa
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, 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". Its definition
> >> is:
>
> Segher> How should this work with sh
> "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". Its definition
>> is:
Segher> How should this work with shrink-wrapping? The whole point of that is
Segher> you do not tea
On Wed, Mar 20, 2019 at 10:13:23AM +, Justin Paston-Cooper wrote:
> Section 6.2.5.2 outlines the line number information state machine's
> opcodes. One of them is "DW_LNS_set_epilogue_begin". Its definition
> is:
>
> -
> The DW_LNS_set_epilogue_begin opcode takes no operands. It sets the
>
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 it would be possible to
> > implement a comma
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 it would be possible to
> implement a command which breaks at all exit points of the current
> stack frame. This w
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 Weimer
> wrote:
> >> >>
> >> >> * Justin Paston-Cooper:
> >> >>
> >> >> > T
* 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 Weimer wrote:
>> >>
>> >> * Justin Paston-Cooper:
>> >>
>> >> > Tom Tromey suggested in that thread that this would be quite easy on
>> >> > g
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 quite easy on
> >> > gdb's side if gcc indicates exit loca
* 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 quite easy on
>> > gdb's side if gcc indicates exit locations in the DWARF data, for
>> > instance in the C case, it would ind
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 indicate the locations of return
> >
* 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" comm
13 matches
Mail list logo
