From: Michael Chastain <mec.gnu@mindspring.com>
To: jingham@apple.com, gdb@sources.redhat.com
Subject: Re: GDB/MI Output Syntax
Date: Fri, 27 Aug 2004 19:12:00 -0000 [thread overview]
Message-ID: <412F87A4.nail3LU117EOV@mindspring.com> (raw)
In-Reply-To: <76E69B58-F852-11D8-8E70-000A958F4C44@apple.com>
Jim Ingham <jingham@apple.com> wrote:
> The problem is that the sample extension actually adds a command called
> "sha1". In interactive mode, tcl resolves shortened commands to the
> full name if the resolution is unique.
*bonk* *bonk* *bonk*
That's the sound of me banging my head against the wall. Stupid me!
> I actually think that building Bob's parser into a Tcl C extension &
> using that with the DejaGnu testsuite would be brilliant.
New vistas are opening up to me!
It would be much better to use TCL data structures to parse MI rather
than regular expressions. I had a great experience getting away from
regular expressions with cp_test_ptype_class.
It's still a dozen host arches (actually, a dozen build arches,
TCL runs on build machine). But we're not debugging a target program
with shared libraries, we're just using one as a host.
next prev parent reply other threads:[~2004-08-27 19:12 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1093622671.2836.ezmlm@sources.redhat.com>
2004-08-27 17:56 ` Jim Ingham
2004-08-27 19:12 ` Michael Chastain [this message]
2005-01-05 23:27 ` Bob Rossi
2005-01-06 4:48 ` Eli Zaretskii
2005-01-06 23:31 ` Bob Rossi
2005-01-07 0:36 ` Jim Ingham
2005-01-07 1:12 ` Bob Rossi
2005-01-07 3:12 ` Russell Shaw
2005-01-11 19:35 ` Bob Rossi
2005-01-13 2:23 ` Bob Rossi
2005-01-13 2:46 ` Intrusive GDB Symbol Lookup when debugging remotely David Steven Trollope
2005-01-22 4:25 ` Dave Trollope
2005-01-24 19:48 ` Andrew Cagney
2005-01-24 19:54 ` David Steven Trollope
2005-03-18 16:29 ` Linux Realtime Scheduling Option David Steven Trollope
2005-03-18 18:12 ` Daniel Jacobowitz
2005-03-21 19:21 ` David Steven Trollope
2005-03-21 19:33 ` Daniel Jacobowitz
2005-03-22 3:04 ` Dave Trollope
2005-03-22 4:06 ` Daniel Jacobowitz
2005-01-06 0:28 GDB/MI Output Syntax Paul Schlie
2005-01-06 0:32 ` Kip Macy
2005-01-06 0:49 ` Paul Schlie
2005-01-06 1:10 ` Bob Rossi
2005-01-06 1:36 ` Paul Schlie
-- strict thread matches above, loose matches on Subject: below --
2004-08-25 15:44 Bob Rossi
2004-08-25 15:57 ` Michael Chastain
2004-08-25 19:37 ` Bob Rossi
2004-08-26 14:01 ` Michael Chastain
2004-08-26 18:31 ` Bob Rossi
2004-08-26 20:44 ` Michael Chastain
2004-08-26 20:52 ` Keith Seitz
2004-08-26 22:16 ` Michael Chastain
2004-08-26 22:03 ` Bob Rossi
2004-08-26 23:06 ` Michael Chastain
2004-08-26 21:13 ` Andrew Cagney
2004-08-26 21:25 ` Bob Rossi
2004-08-26 22:46 ` Michael Chastain
2004-08-27 10:14 ` Eli Zaretskii
2004-08-26 22:41 ` Michael Chastain
2004-08-24 3:12 Bob Rossi
2004-08-24 4:15 ` Michael Chastain
2004-08-24 12:30 ` Bob Rossi
2004-08-24 12:50 ` Michael Chastain
2004-08-24 18:59 ` Andrew Cagney
2004-08-24 19:07 ` Bob Rossi
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=412F87A4.nail3LU117EOV@mindspring.com \
--to=mec.gnu@mindspring.com \
--cc=gdb@sources.redhat.com \
--cc=jingham@apple.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