Re: [9fans] mk results in rc: suicide:

This is what acid prints out: rc 505: suicide: sys: trap: fault read addr=0x965708 pc=0xb5d9 mk: 8c -FTVw -I. ../port/devcons.c : exit status=rc 505: sys: trap: fault read addr=0x965708 pc=0xb5d9 term% term% acid 505 /proc/505/text:386 plan 9 execut

Re: [9fans] mk results in rc: suicide:

On Sat, Jul 13, 2024 at 10:13 AM Marco Feichtinger wrote: > > This is what acid prints out: > rc 505: suicide: sys: trap: fault read addr=0x965708 pc=0xb5d9 > mk: 8c -FTVw -I. ../port/devcons.c : exit status=rc 505: sys: trap: > fault read addr=0x965708 pc=0xb5d9 >

Re: [9fans] mk results in rc: suicide:

I did run mk over and over, but couldn't find any %.acid files when it crashed. Interestingly, running 'mk nuke' resulted in an error for the first time: rc 2503: suicide: sys: trap: fault read addr=0x965708 pc=0xb5d9 mk: mkfile:121: syntax error; no var on left side of assignm

Re: [9fans] mk results in rc: suicide:

> > I am lost here. > I read the acid manual, but I still don't know what this output is about. > lstk() prints a stack trace -- or at least tries to, but fails. That implies to me that your stack frame is busted. asm()/casm() shows assembly. The PC you crashed on is 0xb5d9, which happens

Re: [9fans] mk results in rc: suicide:

o...@eigenstate.org wrote: ori: asm()/casm() shows assembly. The PC you crashed on ori: is 0xb5d9, which happens to be in the middle of ori: this comparison instruction: ori: ori: > Readdir+0x2c 0xb5d8 CMPLdir+0x8(SB)(CX*1),AX ori: > Readdir+0x33 0xb5df JNE Read