From: Daniel Jacobowitz <drow@false.org>
To: Jim Blandy <jimb@codesourcery.com>
Cc: Masatake YAMATO <yamato@redhat.com>, gdb-patches@sourceware.org
Subject: Re: To know the stopped reason from hook-stop
Date: Tue, 31 Jul 2007 20:38:00 -0000 [thread overview]
Message-ID: <20070731201310.GA9743@caradoc.them.org> (raw)
In-Reply-To: <m31weos7pu.fsf@codesourcery.com>
On Tue, Jul 31, 2007 at 12:18:05PM -0700, Jim Blandy wrote:
> It's painful to watch people wrestle GDB's scripting language into
> doing something useful. If Daniel's patch to add Python as a
> scripting language for GDB were in the public sources, then I could
> say, "Don't worry about trying to fix GDB's horrible scripting
> language, provide this data to Python." I'm sure that's the better
> investment.
>
> At the same time, I don't want to make the mistake of saying, "Oh, no,
> let's not commit that improvement, something much better is coming
> along real soon now" when there are no specific plans for the much
> better thing's arrival.
>
> Daniel, have you had time to work on that patch since we last talked
> about it?
I just started work on it again Sunday. I'll try to make some more
time for it soon.
I'm afraid I really don't like this patch. Adding magic numbers is
the only reasonable thing we can do in the existing CLI, but it is
arcane and hard to work with. Once there's a better language in
place, we can be a lot more flexible.
(My scripting tree also has some patches to make using strings for
this sort of thing easier.)
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-07-31 20:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 14:29 Masatake YAMATO
2007-07-31 20:02 ` Jim Blandy
2007-07-31 20:38 ` Daniel Jacobowitz [this message]
2007-07-31 21:32 ` Masatake YAMATO
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=20070731201310.GA9743@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=jimb@codesourcery.com \
--cc=yamato@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