Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: gdb-patches@sourceware.org
Subject: Re: Windows semihosting (remote-fileio) fix for console reads
Date: Sat, 10 Jun 2006 21:28:00 -0000	[thread overview]
Message-ID: <uwtbopuny.fsf@gnu.org> (raw)
In-Reply-To: <20060610182130.GA3527@nevyn.them.org> (message from Daniel 	Jacobowitz on Sat, 10 Jun 2006 14:21:31 -0400)

> Date: Sat, 10 Jun 2006 14:21:31 -0400
> From: Daniel Jacobowitz <drow@false.org>
> 
> Here's the problem: a customer tried to use the remote file I/O protocol to
> read from standard input.  Trivial little program, just a read() from stdin
> followed by a write() to stdout.  Read was returning -1.  A well-placed
> printf discovered that this was actually ENOMEM.
> 
> By trial and error, we worked out that on the system we were using a read of
> 26609 bytes from the console, or more, would always return ENOMEM.  Given
> 26608 bytes or less, it would succeed normally.  Please don't ask me what
> that number means.  No, it does not vary with the size of the malloced
> buffer.

That rings a bell, but I'll need to dig deep into old files to find
out the details.  In the meantime, could you please post a short test
program that demonstrates this failure?

Thanks.


  reply	other threads:[~2006-06-10 21:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-10 18:21 Daniel Jacobowitz
2006-06-10 21:28 ` Eli Zaretskii [this message]
2006-06-10 23:44   ` Daniel Jacobowitz
2006-06-11 19:33     ` Eli Zaretskii
2006-06-14  0:32       ` Jim Blandy

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=uwtbopuny.fsf@gnu.org \
    --to=eliz@gnu.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