From: Stanley Lieber <stanley.lieber@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] native (mostly) go for plan9
Date: Mon, 31 Oct 2011 14:23:44 -0500 [thread overview]
Message-ID: <CAHfqX-rSHiiN4fQmnT_jXQ+SBS92M1biPhP7WmDhkmYrvseP8Q@mail.gmail.com> (raw)
In-Reply-To: <CAP6exYK8+DB2P3F1X4tDSs3pdc=takr--AOMAF=FJJG2pprPHw@mail.gmail.com>
On Mon, Oct 31, 2011 at 12:50 PM, ron minnich <rminnich@gmail.com> wrote:
> On Mon, Oct 31, 2011 at 10:45 AM, Stanley Lieber
> <stanley.lieber@gmail.com> wrote:
>> On Mon, Oct 31, 2011 at 12:41 PM, andrey mirtchovski
>>> i'm not seeing this in either 9vx or a plan9 vm... what are compiling on?
>>
>> 9front in vmware.
>
> ah, not something I can help with, certainly ...
>
> ron
8c is also dying on real hardware. For what it's worth, here's the stack
trace from the vmware install:
piro% acid 5781
/proc/5781/text:386 plan 9 executable
/sys/lib/acid/port
/sys/lib/acid/386
acid: lstk()
outcode()+0x473 /go/src/cmd/8c/swt.c:272
p=0x1125a8
b=0x0
f=0x4
i=0x4c
h=0x0
sym=0xa010000
sf=0x0
s=0x960b8
t=0x3f
st=0x0
gclean()+0xd8 /go/src/cmd/8c/txt.c:153
i=0x3ff
s=0x4fbe0
compile(file=0xdfffefb6,ndef=0x0,defs=0x0)+0x334 /go/src/cmd/cc/lex.c:287
ofile=0x53130
p=0x53136
c=0x3
fd=0x38717
av=0x4fba0
i=0xf
opt=0x41988
main(argv=0xdfffef7c,argc=0x1)+0x151 /go/src/cmd/cc/lex.c:155
ndef=0x0
defs=0x0
_argc=0x49
_args=0x3fc19
p=0x0
_main+0x31 /sys/src/libc/386/main9.s:16
acid:
And on real hardware:
tr99% acid 441088
/proc/441088/text:386 plan 9 executable
/sys/lib/acid/port
/sys/lib/acid/386
acid: lstk()
outcode()+0x473 /go/src/cmd/8c/swt.c:272
p=0x1125a8
b=0x0
f=0x4
i=0x4c
h=0x0
sym=0xa010000
sf=0x0
s=0x960b8
t=0x3f
st=0x0
gclean()+0xd8 /go/src/cmd/8c/txt.c:153
i=0x3ff
s=0x4fbe0
compile(file=0xdfffefb6,ndef=0x0,defs=0x0)+0x334 /go/src/cmd/cc/lex.c:287
ofile=0x53130
p=0x53136
c=0x3
fd=0x38717
av=0x4fba0
i=0xf
opt=0x41988
main(argv=0xdfffef7c,argc=0x1)+0x151 /go/src/cmd/cc/lex.c:155
ndef=0x0
defs=0x0
_argc=0x49
_args=0x3fc19
p=0x0
_main+0x31 /sys/src/libc/386/main9.s:16
acid:
next prev parent reply other threads:[~2011-10-31 19:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-31 15:11 ron minnich
2011-10-31 16:41 ` Stanley Lieber
2011-10-31 16:51 ` andrey mirtchovski
2011-10-31 17:08 ` ron minnich
2011-10-31 17:30 ` Stanley Lieber
2011-10-31 17:41 ` andrey mirtchovski
2011-10-31 17:44 ` ron minnich
2011-10-31 17:45 ` Stanley Lieber
2011-10-31 17:50 ` ron minnich
2011-10-31 19:23 ` Stanley Lieber [this message]
2011-10-31 19:32 ` ron minnich
2011-10-31 19:44 ` Stanley Lieber
2011-10-31 19:48 ` ron minnich
2011-10-31 21:01 ` ron minnich
2011-10-31 22:10 ` Skip Tavakkolian
2011-10-31 22:17 ` ron minnich
2011-10-31 22:34 ` Bakul Shah
2011-10-31 22:38 ` ron minnich
2011-10-31 22:21 ` ron minnich
2011-11-01 10:20 ` Charles Forsyth
[not found] ` <CAP6exYJ8MQdcRa1vofMVjgaFK0Xu-po4eZBOOb>
[not found] ` <CAP6exYJf1UKFdpeXyFXRt0Y7hPc=Hyq7oBdvi9uX3Z7+FQbxsA@mail.gmail.c>
2011-10-31 22:24 ` erik quanstrom
2011-10-31 22:34 ` cinap_lenrek
2011-10-31 22:44 ` erik quanstrom
2011-10-31 22:47 ` cinap_lenrek
[not found] ` <CAP6exYKue2e7NWx07+RMNDs38aXex0y9urfT6eT1LKbjvvA_yw@mail.gmail.c>
2011-10-31 22:46 ` erik quanstrom
2011-11-01 10:41 ` Yaroslav
2011-11-01 16:57 ` Skip Tavakkolian
2011-11-01 17:26 ` ron minnich
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=CAHfqX-rSHiiN4fQmnT_jXQ+SBS92M1biPhP7WmDhkmYrvseP8Q@mail.gmail.com \
--to=stanley.lieber@gmail.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).