From: Doug Evans <dje@google.com>
To: Peter Griffin <peter.griffin@linaro.org>
Cc: gdb-patches <gdb-patches@sourceware.org>,
Lee Jones <lee.jones@linaro.org>
Subject: Re: RFC GDB Linux Awareness analysis
Date: Mon, 05 Oct 2015 18:37:00 -0000 [thread overview]
Message-ID: <CADPb22TRVgovZzTxQXaDif5xT3MvqUMK-r=eZeb+9nSn=V8q3Q@mail.gmail.com> (raw)
In-Reply-To: <20150930080205.GA26183@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 :).
prev parent reply other threads:[~2015-10-05 18:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 14:29 Peter Griffin
2015-06-04 16:32 ` Doug Evans
2015-09-30 8:02 ` Peter Griffin
2015-10-05 18:37 ` Doug Evans [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADPb22TRVgovZzTxQXaDif5xT3MvqUMK-r=eZeb+9nSn=V8q3Q@mail.gmail.com' \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=lee.jones@linaro.org \
--cc=peter.griffin@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).