From: Keith Seitz <keiths@cygnus.com>
To: <gdb-patches@sources.redhat.com>
Subject: Re: [RFA] gdb-events.sh portability update
Date: Thu, 07 Jun 2001 12:43:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.33.0106071239350.10814-100000@ryobi.cygnus.com> (raw)
In-Reply-To: <3B1FD4D1.2070401@cygnus.com>
On Thu, 7 Jun 2001, Andrew Cagney wrote:
> > 3) Uses "echo" to put strings containing special characters (e.g. \n) into
> > files:
> >
> > echo ""
> > echo "fprintf_unfiltered (gdb_stderr, \"This is an error\\n\");"
>
> Yes, ok.
Done.
> On the last one, gdbarch.sh now uses printf but it doesn't
> matter either way.
So it does. I wasn't sure whether this was portable, but it would seem to
be.
Perhaps one of my subsequent patches to gdb-events.sh will mimick more of
gdbarch.sh... :-)
Keith
prev parent reply other threads:[~2001-06-07 12:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-07 11:30 Keith Seitz
2001-06-07 12:24 ` Andrew Cagney
2001-06-07 12:43 ` Keith Seitz [this message]
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=Pine.GSO.4.33.0106071239350.10814-100000@ryobi.cygnus.com \
--to=keiths@cygnus.com \
--cc=gdb-patches@sources.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