From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Fri, 14 Jan 2011 18:00:59 -0800
From: Anthony Martin <ality@pbrane.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Message-ID: <20110115020059.GB20238@dinah>
References: <AANLkTin8_MZ0B8GSDDSa-k87aOi2-88zpN4n2suHv5gd@mail.gmail.com>
	<AANLkTim0dPgQaqg6+E9oF6xMfPeFEg8QuT8q4cFf8yfw@mail.gmail.com>
	<AANLkTi=tnaw5b7PMWd0sTP6CGG1fROvBatFgZPasiHCW@mail.gmail.com>
	<AANLkTi=Z7+g+o-KYvWci2Tf27m5qgYvcAcTEvWmBa75a@mail.gmail.com>
	<AANLkTim9Vw10LF626ZSx1QLBQeAr75oUBVgpQwZp-MFC@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <AANLkTim9Vw10LF626ZSx1QLBQeAr75oUBVgpQwZp-MFC@mail.gmail.com>
Subject: Re: [9fans] plan9 go output faults on 9vx but ok on cpu
Topicbox-Message-UUID: 98c73aae-ead6-11e9-9d60-3106f5b1d025

Pavel Zholkover <paulzhol@gmail.com> once said:
> I have no idea what is causing it to die, I've tried adding a bunch of
> INT $3 to see how far in the flow I can get, but all I get this:
>
> 9vx panic: unknown trap/intr: 0x203
> aborting, to dump core.
>
> for an INT $3 just before
> CALL	SI	// fn()

This happens because the linker outputs the two bytes
{ 0xCD, 0x03 } for an INT $3 instruction but libvx32
only sends a VXTRAP_BREAKPOINT to 9vx if it sees an
INT3 instruction (a single 0xCC byte). Try using a
'BYTE $0xCC' instead.

  Anthony