I finally got ITS running on my simh plan9 port. I discovered that one
of the DDT command from ITS is snarf
:SNARF
if the current job (say, FOO) has an inferior named ,
this command takes away from FOO
and then does ":JOB ". Thus, becomes a direct
inferior of t
On Tue, Jan 11, 2011 at 8:25 AM, ron minnich wrote:
> can you do a ratrace for me?
>
> ron
>
>
i'll have to rebuild using the vx32 branch on your bitbucket. is it up
to date with the changes to compile on linux/x86-64?
here it is on acid:
% acid 8.hell-o
8.hell-o:386 plan 9 executable
/sys/lib/
slightly different on my mac, so i'll post it:
61: page fault 0x10bc MOVLCX,0xdfffefc0
acid: asm(*PC-32)
0x109c 0x109c ADDBAL,0x0(AX)
0x109e 0x109e ADDBAL,0x4489f0e4(BX)
0x10a4 0x10a4 ANDB$0x78,AL
0x10a6 0x10a6 MOVLBX,0x7c(SP)
0x10aa 0x
anyone know the lineage of plan9's ape/make,
I would like to find a manual page and understand what
clever features it does / doesn't support.
-Steve
On Wed, Jan 12, 2011 at 11:53 AM, Steve Simon wrote:
> anyone know the lineage of plan9's ape/make,
> I would like to find a manual page and understand what
> clever features it does / doesn't support.
>
> -Steve
>
>
http://plan9.bell-labs.com/sources/plan9/sys/src/ape/cmd/make/ident.c
-- vs
On Wed, Jan 12, 2011 at 9:12 AM, andrey mirtchovski
wrote:
> slightly different on my mac, so i'll post it:
>
> 61: page fault 0x10bc MOVL CX,0xdfffefc0
eek. Yeah, I guess the guys are right, you're dying on access to stack?
which 9vx are you running? I'm on travel but will look at this tom
ron minnich once said:
> are you saying change 8l so that it creates code that works on 9vx in
> the special case that it runs on a 64-bit system? Then we're going to
> need to make 8l aware of way too much stuff.
I'm talking about Go's linker. In the Go runtime, the G and M
pointers need to be i
> I'm talking about Go's linker. In the Go runtime, the G and M
> pointers need to be in a per-process storage area. On Plan 9,
> this is the stack. Right now, the offset of the pointers is
> hard-coded in the linker to be just before the Tos structure.
> The problem is that the value that was chos
>0xd000 (as it is on native Plan 9).
of course, that too can change, but i know you know that,
and the current go implementation was just to get going.
> main9.s sets _tos on entry. why not just use _tos as
> the c glue code does?
>
> - erik
>
>
I'm already setting _tos on entry:
http://code.google.com/p/go/source/browse/src/pkg/runtime/plan9/386/rt0.s
TEXT _rt0_386_plan9(SB),7, $0
MOVLAX, _tos(SB)
// move arguments
On Wed, Jan 12, 2011 at 12:32 AM, Skip Tavakkolian
wrote:
> On Tue, Jan 11, 2011 at 8:25 AM, ron minnich wrote:
>> can you do a ratrace for me?
>>
>> ron
>>
>>
>
> i'll have to rebuild using the vx32 branch on your bitbucket. is it up
> to date with the changes to compile on linux/x86-64?
yeah,
i have a problem with the internal caching
dns getting confused and thinking that google's
ip is something wierd like 192.168.0.1 or
205.185.192.1. since the list of ip addresses
google uses for google.com is fairly well-known,
it's easy enough to look and see if dns isn't nuts.
the problem is re
12 matches
Mail list logo
