From: EBo <ebo@sandien.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] read(2) problem on p9p?
Date: Fri, 13 Aug 2010 13:03:14 -0600 [thread overview]
Message-ID: <015c32d4affb8354ab603782115e5451@swcp.com> (raw)
In-Reply-To: <AANLkTinRbO3KM3W7TDuJMABOmbQO16omJKpXj4TDvxvr@mail.gmail.com>
> No, you shouldn't send the whole code base.
> You should take the time to cut the program down to
> a short demonstration of the problem before posting to
> the list. 9 times out of 10 you find, as was the case
> here, that the problem is not where you thought it was,
> and you avoid the list post entirely, saving the time of
> the many readers and your time too, since you get the
> answer faster.
I agree, but to get that specific test to work (writing to a file that is
synthetically generated my the system) requires running against the server
I'm working on, which in turn requires almost all the code I have to date
(minus the other regression tests). I know that this is WAY to much to
send the list without a very good reason. All I was asking is that if
there was something obvious wrong. In most cases I do take the time to
trim it down to a standalone case (like I did with dirreadall failing when
run on in-memory trees).
The problem turned out to be that I wrote "add tst_var type int" to ctl --
which creates an int variable (which is 4 bytes). All of my later tests
assumed I was working with strings. So, a seek or pread fixed the obvious
problem, but the underlying one length was due to it was doing exactly what
I asked it to ;-) So, this discussion pointed the way to two other bugs.
EBo --
next prev parent reply other threads:[~2010-08-13 19:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-13 16:54 EBo
2010-08-13 17:16 ` [9fans] " erik quanstrom
2010-08-13 17:46 ` EBo
2010-08-13 17:51 ` Skip Tavakkolian
2010-08-13 18:14 ` Russ Cox
2010-08-13 18:35 ` EBo
2010-08-13 18:46 ` Russ Cox
2010-08-13 19:03 ` EBo [this message]
2010-08-13 18:16 ` EBo
2010-08-13 18:58 ` erik quanstrom
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=015c32d4affb8354ab603782115e5451@swcp.com \
--to=ebo@sandien.com \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).