From: Michael Chastain <mec.gnu@mindspring.com>
To: pgilliam@us.ibm.com, gdb-patches@sources.redhat.com
Subject: Re: [patch] New test for set backtrace related functionality
Date: Fri, 22 Oct 2004 15:59:00 -0000 [thread overview]
Message-ID: <41792E5A.nailCWS110OUT@mindspring.com> (raw)
In-Reply-To: <200410210955.15904.pgilliam@us.ibm.com>
Paul Gilliam <pgilliam@us.ibm.com> wrote:
> one week ping.
Argh, sorry about that.
Some of the lines in setbacktrace.exp are incorrectly formatted
(weird line wrapping after the '+' markers have been inserted).
you send me a clean copy of the files, by sending them as attachments
perhaps?
Meanwhile I will clean up what I've got and give it a review.
Michael
===
2004-10-14 Paul Gilliam <pgilliam@us.ibm.com>
* gdb.base/setbacktrace.c gdb.base/setbacktrace.exp: New files.
next prev parent reply other threads:[~2004-10-22 15:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-14 22:41 Paul Gilliam
2004-10-14 22:47 ` Paul Gilliam
2004-10-21 16:57 ` Paul Gilliam
2004-10-22 15:59 ` Michael Chastain [this message]
2004-10-22 17:00 ` Paul Gilliam
2004-10-22 21:48 ` Michael Chastain
2004-10-25 16:32 ` Paul Gilliam
2004-10-26 18:54 ` Paul Gilliam
2004-11-08 21:01 ` Paul Gilliam
2004-11-17 22:01 ` Andrew Cagney
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=41792E5A.nailCWS110OUT@mindspring.com \
--to=mec.gnu@mindspring.com \
--cc=gdb-patches@sources.redhat.com \
--cc=pgilliam@us.ibm.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