From: Anthony Martin <ality@pbrane.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9vx on OpenBSD
Date: Tue, 15 Feb 2011 18:14:02 -0800 [thread overview]
Message-ID: <20110216021402.GA24848@dinah> (raw)
In-Reply-To: <0c422a303390d92446dd36292733bffb@stanleylieber.com>
> % ktrace -d ./9vx -r /n/plan9 -u glenda -g -S
> namec #/
> namec #e/terminal
> namec #e/cputype
> namec #e/rootdir
> namec #e/service
> namec #e/user
> namec #e/sysname
> namec #Zplan9/
> namec /
> namec #p
> namec /proc
> namec #~/mntloop
> namec #Zplan9/
> namec #s/boot
> 9vx panic: vxproc_run: Invalid argument
In src/libvx32/openbsd.c:/vxemu_map
int s, sel;
struct vxproc *vxp;
union descriptor desc;
...
/*if(emu->datasel == 0){
if ((s = i386_set_ldt(LDT_AUTO_ALLOC, &desc, 1)) < 0)
return -1; */
emu->datasel = (s<<3) + 4 + 3; // 4=LDT, 3=RPL
if(i386_set_ldt(emu->datasel >> 3, &desc, 1) < 0)
return -1;
...
The s variable is used un-initialized because
of the commented piece of code, causing EINVAL.
And since LDT_AUTO_ALLOC is only on FreeBSD or
Darwin, you're going to have to get it another
way.
At least, that's what I think from reading the
code since I don't have access to an OpenBSD box.
Anthony
next prev parent reply other threads:[~2011-02-16 2:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 16:42 Stanley Lieber
2011-02-15 22:06 ` ron minnich
2011-02-16 17:06 ` Stanley Lieber
2011-02-15 23:34 ` Anthony Martin
2011-02-15 23:53 ` Stanley Lieber
2011-02-16 0:10 ` ron minnich
2011-02-16 1:13 ` Stanley Lieber
2011-02-16 1:17 ` ron minnich
2011-02-16 1:23 ` Stanley Lieber
2011-02-16 1:24 ` Devon H. O'Dell
2011-02-16 2:14 ` Anthony Martin [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-02-16 15:36 Stanley Lieber
2011-02-15 21:01 ` ron minnich
2011-02-16 16:05 ` Stanley Lieber
2011-02-16 0:50 rsdehart
2011-02-16 0:36 rsdehart
2011-02-16 0:26 rsdehart
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=20110216021402.GA24848@dinah \
--to=ality@pbrane.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).