This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: RFC GDB Linux Awareness analysis
- From: Doug Evans <dje at google dot com>
- To: Peter Griffin <peter dot griffin at linaro dot org>
- Cc: gdb-patches <gdb-patches at sourceware dot org>, Lee Jones <lee dot jones at linaro dot org>
- Date: Mon, 5 Oct 2015 11:36:45 -0700
- Subject: Re: RFC GDB Linux Awareness analysis
- Authentication-results: sourceware.org; auth=none
- References: <20150603142858 dot GA19370 at griffinp-ThinkPad-X1-Carbon-2nd> <CADPb22QsOz-ToWB+Fp8yoxy0Tecxdae+TbTOEjn0RCHNQjU6YQ at mail dot gmail dot com> <20150930080205 dot GA26183 at griffinp-ThinkPad-X1-Carbon-2nd>
On Wed, Sep 30, 2015 at 1:02 AM, Peter Griffin <peter.griffin@linaro.org> wrote:
> Something which I believe is missing currently is the ability to add a new thread
> via the python interface. Is that something you would consider appropriate?
I think it's appropriate conceptually.
"How" is the tricky part.
> By way of example, currently the kernel python scripts add a "lx-ps" which
> parses the task_structs, and builds a list of threads. This is the beginning
> of task-awareness in python, but currently the list is simply printed
> out.
>
> Being able to either return this thread list to GDB, or actually create thread
> objects inside GDB via the python interface would appear to be the next logical
> step.
>
>
>> Can we proceed by making "do it in python" the default choice,
>> and then address each issue as needed?
>
> Ok, sounds good to me. This was also my gut feeling when starting this
> analysis, but to have it confirmed by you is encouraging :).