From: Michael Chastain <mec.gnu@mindspring.com>
To: drow@false.org, jimb@redhat.com
Cc: gdb@sources.redhat.com, ezannoni@redhat.com, cagney@redhat.com
Subject: Re: gdb.mi/*.exp and absolute line numbers
Date: Thu, 05 Aug 2004 16:02:00 -0000 [thread overview]
Message-ID: <41125A3D.nail2KQ18L2HZ@mindspring.com> (raw)
In-Reply-To: <vt2d625d5bz.fsf@zenia.home>
Well all right, one re-implementation of gdb_get_line_number in
native tcl coming right up.
This is high priority to me because that new gcc warning wipes out most
of the gdb.mi results.
I used to hate and not really get Tcl. Then I learned Perl. I totally
heart Perl. Now I think of Tcl as Perl's demented step-sibling, and I
can wield it a lot better.
Michael C
next prev parent reply other threads:[~2004-08-05 16:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-05 9:20 Michael Chastain
2004-08-05 13:23 ` Daniel Jacobowitz
2004-08-06 6:26 ` Michael Chastain
2004-08-05 14:34 ` Jim Blandy
2004-08-05 16:02 ` Michael Chastain [this message]
2004-08-06 8:24 ` Eli Zaretskii
2004-08-06 9:41 ` Michael Chastain
2004-08-06 14:46 ` Andrew Cagney
2004-08-06 16:06 ` Michael Chastain
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=41125A3D.nail2KQ18L2HZ@mindspring.com \
--to=mec.gnu@mindspring.com \
--cc=cagney@redhat.com \
--cc=drow@false.org \
--cc=ezannoni@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).