From: Hui Zhu <teawater@gmail.com>
To: Stan Shebs <stan@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] tracepoint: add new trace command "printf"[0] gdb
Date: Thu, 06 Jan 2011 06:43:00 -0000 [thread overview]
Message-ID: <AANLkTi=K3tw6_-uYDL8W4mSaL6nFPx-N541ALMC9-JZX@mail.gmail.com> (raw)
In-Reply-To: <4D24D9DD.8090104@codesourcery.com>
On Thu, Jan 6, 2011 at 04:51, Stan Shebs <stan@codesourcery.com> wrote:
> On 1/3/11 10:18 PM, Doug Evans wrote:
>>
>> [for reference sake]
>> To me this is a subset of a bigger feature set that is missing:
>> partitioning of the things that can be accomplished by gdbserver from
>> the setup that is needed (IOW separate the heavy lifting of parsing
>> debug info and translating a user query into, for example, an agent
>> expression (the gdb side) from the processing of that query when the
>> breakpoint(/tracepoint) is hit (the gdbserver side).
>> Plus it might be useful to not require a gdb/gdbserver connection to
>> get things started, e.g., convey the tracepoint info (and anything
>> else) to gdbserver from a local source.
>> [I'm using "query" loosely here. I'm using "gdbserver" loosely too:
>> anything that looks like gdbserver to gdb will do.]
>
> I'm actually working on a contract proposal to do a bunch of work in this
> area.
>
> One of the specific ideas is to introduce a "dynamic printf" that works
> somewhat like what I think Hui Zhu was wanting; it stops the program at a
> location, runs the printf in gdbserver, and then continues.
>
> Another one of the ideas is to use agent expressions to do target-side
> conditional breakpoints. This is especially compelling for many-core
> targets, where we don't want 100 threads on 100 cores to be trying to get
> GDB to do 100 conditional expression evaluations all at once.
>
> I didn't specifically propose to go beyond that, into general partitioning
> of command lists between host and target, although it's a very interesting
> direction. The idea gets me to thinking about whether we should keep the
> command list form, or raise it to the level of a real language, or maybe
> support several - Mentor's EDGE debugger for instance uses a C syntax for
> its "codelets" (
> http://www.mentor.com/embedded-software/resources/overview/codelets-15b9eaed-8e4b-43a2-aad5-c189cd7f2d68
> ) even though they run on the host, and whether the language is C or Python,
> it seems useful to be able to inject real code bits into the target system.
>
> Anyway, if we get the contract (fingers crossed!) then I expect we'll be
> putting up some proposals for discussion within the next couple of months.
>
> I'll comment on the patch in a different message.
>
> Stan
>
>
That will be great! Thanks Stan.
Hui
next prev parent reply other threads:[~2011-01-06 6:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-03 16:29 Hui Zhu
2011-01-03 19:21 ` Doug Evans
2011-01-04 4:34 ` Hui Zhu
2011-01-04 6:19 ` Doug Evans
2011-01-04 12:07 ` Hui Zhu
2011-01-05 17:24 ` Doug Evans
2011-01-05 18:18 ` Michael Snyder
2011-01-06 6:42 ` Hui Zhu
2011-01-05 20:51 ` Stan Shebs
2011-01-06 6:43 ` Hui Zhu [this message]
2011-01-28 5:54 ` Hui Zhu
2011-02-04 15:59 ` Hui Zhu
2011-02-11 3:49 ` Hui Zhu
2011-02-11 18:45 ` Tom Tromey
2011-02-17 8:16 ` Hui Zhu
2011-02-21 8:18 ` Hui Zhu
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='AANLkTi=K3tw6_-uYDL8W4mSaL6nFPx-N541ALMC9-JZX@mail.gmail.com' \
--to=teawater@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=stan@codesourcery.com \
/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).