This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH v3 3/3] Dynamic core regset sections support
- From: Andreas Arnez <arnez at linux dot vnet dot ibm dot com>
- To: Pedro Alves <palves at redhat dot com>
- Cc: Mark Kettenis <mark dot kettenis at xs4all dot nl>, gdb-patches at sourceware dot org, Ulrich dot Weigand at de dot ibm dot com
- Date: Thu, 13 Jun 2013 13:02:02 +0200
- Subject: Re: [PATCH v3 3/3] Dynamic core regset sections support
- References: <877ghzmkmj dot fsf at br87z6lw dot de dot ibm dot com> <8738sngy5e dot fsf at br87z6lw dot de dot ibm dot com> <201306121521 dot r5CFLvl9024858 at glazunov dot sibelius dot xs4all dot nl> <871u86e5gi dot fsf at br87z6lw dot de dot ibm dot com> <51B99143 dot 3080808 at redhat dot com>
Pedro Alves <palves@redhat.com> writes:
>> Do you mean to always write the TDB regset into the core dump, like
>> without the patch? And then add some logic such that GDB recognizes
>> zero values in the register note section as invalid and clears the
>> regset? Or do I misinterpret your suggestion?
>
> Not zero, but present them as unavailable/invalid.
Not sure I understand your point here. *Presenting them* as unavailable
is exactly what the patch does.
> Isn't there a control register GDB can read to check whether a
> transaction is in progress (useful for both core and live debugging) ?
No, the kernel indicates an interrupted transaction with the presence of
the TDB regset. This applies to ptrace as well as to a core dump. My
goal for gcore was to behave the same.