From: Fernan Bolando <fernanbolando@mailc.net>
To: 9fans@9fans.net
Subject: Re: [9fans] p9p vac issue
Date: Sat, 27 Jun 2009 10:12:32 +0800 [thread overview]
Message-ID: <1d5d51400906261912t34abc96eg62b07e4fd9a6372a@mail.gmail.com> (raw)
In-Reply-To: <d7c5dc2d2043edb5f99143a8e701f5e8@quanstro.net>
On Tue, Jun 23, 2009 at 12:50 AM, erik quanstrom<quanstro@quanstro.net> wrote:
>> looks like it's related to the error above. you might want to downgrade to
>> http://swtch.com/plan9port/plan9port-20090609.tgz
>
> fortune tells me
>
> The most effective debugging tool is still careful thought,
> coupled with judiciously placed print statements.
> -Kernighan, 1978
>
> i don't think this bug is going to be fixed without a
> bit of actual debugging. since your theories are rather
> easy to test, i would think it would be much easier to
> arrive at a solution via a frontal assault bwk style, rather
> than sniping at it from the safety of the mailing list.
>
> i promise, vac won't shoot back. even if you pull out
> gdb.
>
> i'm interested in what the actual bug is.
yes, It appears I might be wrong
This warning is probably just a overly paranoid openbsd compiler
vac.c:509: warning: sizeof(pointer) possibly incorrect in argument 3
and might not be related to this error
create bsize 8192 psize 8160vac: vacfscreate: vacfileroot: read too
small: asked for 0 need at least 389
I looked at it again and tried the vac command on a test venti and it
worked with no errors. Even with the sizeof warning. I no longer have
a copy of the problematic plan9port.tgz so I took
a new copy from swtch.com. It was either fixed by someone else or the
error was a fluke.
fernan
--
http://www.fernski.com
next prev parent reply other threads:[~2009-06-27 2:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 8:10 phætøn
2009-06-22 8:33 ` Mathieu L.
2009-06-22 11:33 ` Adrian Tritschler
2009-06-22 12:06 ` Josh Wood
2009-06-22 12:08 ` Mathieu L.
2009-06-22 14:40 ` Fernan Bolando
2009-06-22 16:20 ` Fernan Bolando
2009-06-22 16:50 ` erik quanstrom
[not found] ` <d7c5dc2d2043edb5f99143a8e701f5e8@quanstro.net>
2009-06-27 2:12 ` Fernan Bolando [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-06-21 4:18 phætøn
2009-06-20 16:11 phætøn
2009-06-21 0:08 ` Adrian Tritschler
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=1d5d51400906261912t34abc96eg62b07e4fd9a6372a@mail.gmail.com \
--to=fernanbolando@mailc.net \
--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).