From: Daniel Jacobowitz <drow@false.org>
To: Nathan Sidwell <nathan@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: fileio test
Date: Tue, 10 Nov 2009 19:12:00 -0000 [thread overview]
Message-ID: <20091110191231.GA17009@caradoc.them.org> (raw)
In-Reply-To: <4AF94694.1090601@codesourcery.com>
On Tue, Nov 10, 2009 at 10:55:16AM +0000, Nathan Sidwell wrote:
> It's not obvious to me how the testsuite could distinguish between
> these two cases. remote-fileio.c doesn't have any verbose logging we
> could turn on (and have the testsuite watch for it). I suppose we
> could add it. Or we could turn on remote-protocol logging and watch
> for that (which seems less desirable).
>
> Thoughts?
I'm not sure either. I like the idea of adding logging to
remote-fileio.c; we could use that to disable the test if not using
semihosting. (Although that risks turning this to UNSUPPORTED if
semihosting is completely broken...)
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2009-11-10 19:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-05 18:04 Nathan Sidwell
2009-11-09 20:14 ` Daniel Jacobowitz
2009-11-10 10:55 ` Nathan Sidwell
2009-11-10 19:12 ` Daniel Jacobowitz [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=20091110191231.GA17009@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=nathan@codesourcery.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