On Tue, Jul 1, 2008 at 10:13 AM, Russ Cox <[EMAIL PROTECTED]> wrote:
> When it stops, then can should attach gdb by
> looking up the pid in ps and running
>
>gdb 9vx pid
>thread apply all where 20
>
> That's usually safer than running 9vx under
> gdb from the start. 9vx is a multit
> No panic: the window appears and two lines print (the command-line
> arguments and the memory readout), then everything stops. When I use
> -X, the lines of assembly stop.
When it stops, then can should attach gdb by
looking up the pid in ps and running
gdb 9vx pid
thread apply
On Tue, Jul 1, 2008 at 9:00 AM, Russ Cox <[EMAIL PROTECTED]> wrote:
>> I have Ubuntu on a VPS (on Xen) and I'd like to install a Plan 9
>> server using 9vx. 9vx tip compiles, but segfaults after the "256M
>> memory" line (as does the precompiled binary, in the same place). I am
>> tunneling to loca
> I have Ubuntu on a VPS (on Xen) and I'd like to install a Plan 9
> server using 9vx. 9vx tip compiles, but segfaults after the "256M
> memory" line (as does the precompiled binary, in the same place). I am
> tunneling to local X11 on OS X 10.5.3.
>
> I don't know how to debug this properly, but
I have Ubuntu on a VPS (on Xen) and I'd like to install a Plan 9
server using 9vx. 9vx tip compiles, but segfaults after the "256M
memory" line (as does the precompiled binary, in the same place). I am
tunneling to local X11 on OS X 10.5.3.
I don't know how to debug this properly, but here is gdb
