From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: fche@redhat.com
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Avoid using sprintf in the testsuite
Date: Sun, 20 Mar 2005 21:28:00 -0000 [thread overview]
Message-ID: <200503202128.j2KLSgVF027349@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <y0mekeex7wp.fsf@toenail.toronto.redhat.com> (fche@redhat.com)
From: fche@redhat.com (Frank Ch. Eigler)
Date: 17 Mar 2005 16:46:30 -0500
Mark Kettenis <kettenis@gnu.org> writes:
> Using sprintf in the testsuite causes problems with the upcoming
> OpenBSD 3.7. The warning about its usuge printed by the linker makes
> us think the compilation failed. [...]
Perhaps instead gdb's testsuite should adopt gcc's warning-pruning
code: see for example gcc/testsuite/lib/prune.exp.
Better yet, I should add OpenBSD linker warning pruning to DejaGnu
itself. Thanks for the suggestion. I withdraw the patch.
Mark
prev parent reply other threads:[~2005-03-20 21:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-17 21:12 Mark Kettenis
2005-03-17 21:46 ` Frank Ch. Eigler
2005-03-20 21:28 ` Mark Kettenis [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=200503202128.j2KLSgVF027349@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=fche@redhat.com \
--cc=gdb-patches@sourceware.org \
/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