From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: drow@false.org
Cc: gdb-patches@sourceware.org
Subject: Re: [commit] Testsuite updates
Date: Sun, 31 Dec 2006 20:35:00 -0000 [thread overview]
Message-ID: <200612312035.kBVKZ0jI001086@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <20061231200905.GA24490@nevyn.them.org> (message from Daniel Jacobowitz on Sun, 31 Dec 2006 15:09:05 -0500)
> Date: Sun, 31 Dec 2006 15:09:05 -0500
> From: Daniel Jacobowitz <drow@false.org>
>
> This patch fixes or avoids a number of failures on my Debian
> x86_64-pc-linux-gnu system.
>
> I was using a HEAD build of glibc rather than the system's glibc,
> in order to pick up Jan's fix for unwinding information in signal
> handlers. Having debugging information for the C library caused the
> annota1.exp and annota3.exp failures.
So continueing to printf didn't actually get is to printf? What's
going on here?
> The selftest.exp patch adds an XFAIL for a GCC bug in my system
> compiler, which I reported several months ago to the GCC bugzilla.
> I'm not optimistic about it getting fixed soon.
A bug in *your* system compiler. How widespread is this bug? We
really should be careful with complicating tests to work around
problems in particular GCC versions.
> And finally, for linux-dp.exp, an omission in Nathan's recent change
> generated UNSUPPORTEDs on native GNU/Linux systems, where the test
> should pass.
Can you elaborate? I mean, what output is genererated that should be
ignored?
next prev parent reply other threads:[~2006-12-31 20:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-31 20:09 Daniel Jacobowitz
2006-12-31 20:35 ` Mark Kettenis [this message]
2006-12-31 20:49 ` Daniel Jacobowitz
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=200612312035.kBVKZ0jI001086@brahms.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=drow@false.org \
--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