From: Daniel Jacobowitz <drow@false.org>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFC add "convenience functions" to gdb
Date: Sat, 08 Mar 2008 20:30:00 -0000 [thread overview]
Message-ID: <20080308203027.GA25644@caradoc.them.org> (raw)
In-Reply-To: <m38x0t107r.fsf@fleche.redhat.com>
On Sat, Mar 08, 2008 at 12:31:52PM -0700, Tom Tromey wrote:
> I use $"..." to denote a host string.
>
> After this it would be pretty simple to start allowing scripting
> access to all kinds of interesting state: string-valued set/show
> variables, the exe name, the names of functions up and down the stack,
> types, syscalls (whatever happened to that "catch syscall" patch?) --
> anything we can think of.
Hold on a bit; I promised to post my lazy strings patch for Doug and I
have so far failed to do so. We can use the normal string syntax, as
long as we don't flush them out to the target unless some operation
requires it.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-03-08 20:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-01 5:50 Tom Tromey
2008-03-01 7:05 ` Tom Tromey
2008-03-08 20:24 ` Tom Tromey
2008-03-08 20:30 ` Daniel Jacobowitz [this message]
2008-03-08 20:35 ` Tom Tromey
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=20080308203027.GA25644@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=tromey@redhat.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