From: Daniel Jacobowitz <drow@false.org>
To: Markus Deuling <deuling@de.ibm.com>
Cc: GDB discuss <gdb@sourceware.org>
Subject: Re: gdb.base/fileio.exp necessary?
Date: Thu, 03 May 2007 15:36:00 -0000 [thread overview]
Message-ID: <20070503153625.GA19941@caradoc.them.org> (raw)
In-Reply-To: <463A007D.1080406@de.ibm.com>
On Thu, May 03, 2007 at 05:32:13PM +0200, Markus Deuling wrote:
> Hi,
>
> I'm looking at gdb.base/fileio.exp testcase. What gdb feature does it test?
> It's more a kind of test for open/read/write/ etc. syscalls isn't it? Does it
> make sense to have it in a testsuite for gdb? Maybe I'm overlooking s.th. ?
It tests GDB's emulation of file I/O activities for some remote
targets. See "File-I/O remote protocol extension" in the manual.
If you're noticing that it fails on gdbserver, add "set_board_info
gdb,nofileio 1" to your board file; the feature doesn't apply for all
remote targets.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-05-03 15:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-03 15:33 Markus Deuling
2007-05-03 15:36 ` Daniel Jacobowitz [this message]
2007-05-03 15:39 ` Markus Deuling
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=20070503153625.GA19941@caradoc.them.org \
--to=drow@false.org \
--cc=deuling@de.ibm.com \
--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