Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [RFC] Strings and arrays without malloc
Date: Tue, 11 Mar 2008 06:58:00 -0000	[thread overview]
Message-ID: <m3r6ehssjj.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20080309161335.GA26917@caradoc.them.org> (Daniel Jacobowitz's message of "Sun\, 9 Mar 2008 12\:13\:35 -0400")

>>>>> "Daniel" == Daniel Jacobowitz <drow@false.org> writes:

Daniel> This patch allows a number of expressions to work without
Daniel> having to call malloc.

Thanks.

First a comment on your patch: in case it matters, I think it is fine
as is.


I applied this and then my convenience function patch on top of it.
Then, it was trivial to extend that to allow string-valued "show":

(gdb) p $(show lang)
$1 = "auto; currently c"

I started adding regex support, then thought to take a moment to think
about what functions I would really like to have.

Of course, this list turned out to be basically everything -- access
to all the attributes of breakpoints, watchpoints, frames, utility
commands, etc.  It is pretty daunting, but of course fun in a way.

In the end I think it would be preferable to just use Python for all
this stuff.  That way all the access code only needs to be done once.
IMO the $(...) syntax should simply eval the contents as a Python
expression.

let me know what you think,
Tom


  parent reply	other threads:[~2008-03-11  6:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-09 16:14 Daniel Jacobowitz
2008-03-09 22:20 ` Eli Zaretskii
2008-03-11  6:58 ` Tom Tromey [this message]
2008-03-13  6:12   ` Tom Tromey
2008-03-13 14:16     ` Thiago Jung Bauermann
2008-03-13 14:54       ` Tom Tromey
2008-03-13 16:22         ` Thiago Jung Bauermann
2008-03-13 16:59           ` Tom Tromey
2008-03-13 20:47             ` Tom Tromey
2008-03-13 19:22 ` Joel Brobecker
2008-03-21 15:03   ` Daniel Jacobowitz

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=m3r6ehssjj.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.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