Ok, that makes sense.  The python22-pth port seems to cause problems for =
me,=20
but the normal python22 port went it just fine.

- Pat

On February 8, 2003 09:09 pm, ePAc wrote:
> On Sat, 8 Feb 2003, Alex Kirk wrote:
> > Date: Sat, 08 Feb 2003 05:12:35 GMT
> > From: Alex Kirk <alex@schnarff.com>
> > To: Pat Wendorf <mlist@beholder.homeunix.net>
> > Cc: port-dreamcast@netbsd.org
> > Subject: Re: DB prompt
> >
> > > My DC is currently sitting at a debug prompt.
> > >
> > > panic: tlb_handler: invalid user-space access from kernel mode
> > > va=3D0x00000000 ssr=3D0x400000f0 lwp=3D0x8c832794 onfault=3D0x0c0ec=
efa
> > >
> > > Stopped in pid 16578.1 (python) at 0x8c0eae0a
> > > mov r14, r15
> > >
> > > It was doing a python22-pth build from pkgsrc at it made it as far =
as
> > > executing the compiled binary.  Not sure why executing the binary i=
s
> > > part of the build...
>
> I beleive that python is compiled from C source (base package), but tha=
t a
> number of "modules" or "Extensions" are precompiled (ala java) modules.
> That would be why it is running python as part of the build :o)
>
> Just in case someone is curious about it..
>
> Jok
>
> ---
> Nothing is foolproof to a sufficiently talented fool...
>   oo
> ,(..)\
>   ~~