From: "Gary V. Vaughan" <gary@gnu.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] ape/psh can't exec in 9vx
Date: Wed, 24 Sep 2008 15:17:24 +0800 [thread overview]
Message-ID: <47F50353-4F64-4153-9FCC-CBFA428AC81C@gnu.org> (raw)
In-Reply-To: <14ec7b180809232252j45cf8eeagaa8beabf8c48d88e@mail.gmail.com>
Hi Andrey,
On 24 Sep 2008, at 13:52, andrey mirtchovski wrote:
> On Tue, Sep 23, 2008 at 11:17 PM, Gary V. Vaughan <gary@gnu.org>
> wrote:
>> Was just starting to settle in to 9vx, but this is a real
>> showstopper:
>>
>> term% ls -ld /bin/ape
>> d-rwxr-xr-x Z 1 gary gary 578 Sep 23 11:28 /bin/ape
>> term% ls -l /bin/ape/sh
>> --rwxr-xr-x Z 1 gary gary 482209 Sep 23 11:28 /bin/ape/sh
>> term% /bin/ape/uname -a
>> Plan9 vx32 4 0 i386
>> term% ape/psh
>> $ /bin/ape/uname -a
>> /bin/sh: /bin/ape/uname: cannot execute - Access denied
>>
>> Any ideas on how to debug this one?
>
> i couldn't find out what the bug was but it was in the library's
> interaction with the VM environment and not in SH: for example, pcc
> also crashed when attempting to exec ape's 'diff'. acid's truss wasn't
> useful since it immediately faulted with: "invalid opcode 8c 24 d0 at
> eip 000130c3"
Hmmm... so the real problem is with the binaries in the dist tarball?
Which implies that compiling binaries for 9vx.OSX in a regular plan 9
environment is doing something bad.
> anyway, if you just recompile "ape" you will not see the problem, or
> at least that's what worked for me:
>
> % cd /sys/src/ape
> % mk nuke && mk install
> % uname
> uname: '/bin/uname' file does not exist
> % ape/psh
> $ uname -a
> Plan9 vx32 4 0 i386
> $
Yep, works like a charm! Many thanks again :)
> you may want to do it from the init rc window before you have started
> rio: it crashed the VM with "9vx panic: sigsegv on cpu3" with amazing
> regularity.
I threw caution to the wind and ran the rebuild inside rio, and didn't
have anything unusual happen. I'll keep an eye out for those panics
though, incase I find a way to get them repeatably.
Does that mean I can also recompile replica in 9vx and have it work
correctly? Or does ape have special issues of its own that require
a rebuild in the host environment?
Cheers,
Gary
--
Email me: gary@gnu.org ._(()
Read my blog: http://blog.azazil.net \' )
And my other blog: http://www.machaxor.net =( \
...and my book: http://sources.redhat.com/autobook _(~_)'
next prev parent reply other threads:[~2008-09-24 7:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-24 5:17 Gary V. Vaughan
2008-09-24 5:52 ` andrey mirtchovski
2008-09-24 7:17 ` Gary V. Vaughan [this message]
2008-09-24 14:15 ` andrey mirtchovski
2008-09-24 15:56 ` Steve Simon
2008-09-24 16:09 ` roger peppe
2008-09-24 18:32 ` Uriel
2008-09-24 18:31 ` Uriel
2009-10-19 1:44 Dimitry Golubovsky
2009-10-19 15:27 ` Russ Cox
2009-10-19 16:47 ` Dmitry Golubovsky
2009-10-20 9:14 ` Dmitry Golubovsky
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=47F50353-4F64-4153-9FCC-CBFA428AC81C@gnu.org \
--to=gary@gnu.org \
--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).