From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: drow@false.org
Cc: mark.kettenis@xs4all.nl, gdb@sourceware.org
Subject: Re: What happended to sepdebug.exp?
Date: Mon, 10 Sep 2007 09:49:00 -0000 [thread overview]
Message-ID: <200709092225.l89MPnxe007011@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <20070909215527.GA22886@caradoc.them.org> (message from Daniel Jacobowitz on Sun, 9 Sep 2007 17:55:27 -0400)
> Date: Sun, 9 Sep 2007 17:55:27 -0400
> From: Daniel Jacobowitz <drow@false.org>
>
> On Sun, Sep 09, 2007 at 11:49:04PM +0200, Mark Kettenis wrote:
> > On OpenBSD I'm seeing the following testsuite regression/freakout:
>
> I noticed something similar today while testing ia64-linux.
>
> > 1. The "PASS: debuglink: XXXX" look wrong to me, do people see those
> > on other systems too?
>
> I've been meaning to fix this.
Please do ;).
> > 2. This test should fail a bit more graceful if the necessary
> > toolchain support is missing.
> >
> > The diff below addresses the second issue. Does it look reasonable?
>
> It does to me!
Committed!
prev parent reply other threads:[~2007-09-09 22:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-09 21:55 Mark Kettenis
2007-09-09 22:26 ` Daniel Jacobowitz
2007-09-10 9:49 ` 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=200709092225.l89MPnxe007011@brahms.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=drow@false.org \
--cc=gdb@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