Re: Data Access Exception when trying to Boot installed NetBSD of hard drive

[Adrian Christiansen <adrian.christiansen%gmail.com@localhost>]

Hi Eduardo!

I see, thought this would be the case too.

Here's the output of those two if it would help anyone:

ok .s
Empty

ok ctrace
PC: ffe9a430
Last leaf: call ffe9985c    from ffea5da4
     0 w  %o0-%o5: (        1   38786f        1 ffd40000 ffefffbf ffe8ef04 )

jmpl  ffea794c    from 388e7c
     1 w  %o0-%o5: ( ffefb8a0        0     2000 ffd40000       ff       66 )

jmpl  ffea794c    from 388180
     2 w  %o0-%o5: (        0        0     2000        0        0        0 )

jmpl  ffea794c    from 38d1c4
     3 w  %o0-%o5: (   398c60        1        0       10     2000   398e50 )

jmpl  ffea794c    from 391924
     4 w  %o0-%o5: (   387ee8   398bd8   398400   387df4   387e44        0 )

call 391818    from 39113c
     5 w  %o0-%o5: (   387ee8        1   387ecc       1f fff7fffc ffea6fd8 )

call 391134    from 38a898
     6 w  %o0-%o5: (   387ee8        0   396dc8 ffffddbb ffeffd7f        0 )

call 38a4f0    from 38811c
     7 w  %o0-%o5: (   3960f0   396120   396178   384000     2000 ffffc000 )

jmpl  ffea794c    from 300c40
     8 w  %o0-%o5: ( ffe8f3c8   388000   2fff9c ffd40000 ffefffbf ffe8ef04 )

call 300b64    from 30011c
     9 w  %o0-%o5: ( ffe8f3c8   301c00        0 ffd40000       ff  fffffff )

XXXXXXX    from 0
     a w  %o0-%o5: ( ffe8f3c8   300000        0        0        0        0 )

That looks even less helpful, is there a way to find some declarations
or labels for those addresses?

2014-10-13 18:20 GMT+02:00 Eduardo Horvath <eeh%netbsd.org@localhost>:
> On Mon, 13 Oct 2014, Adrian Christiansen wrote:
>
>> I tried to find some backtrace debugging tools in the OpenBoot 2.x
>> manual and saw there was ftrace. I don't know if ftrace is of any
>> help, but just in case here's the output of ftrace after the Data
>> Access Exception.
>
> `ftrace' is for tracing Forth code.  AFAIK the NetBSD/sparc bootloader is
> C code so you want to use `ctrace'.
>
> Looking at the backtrace:
>
>
>>
>> ok ftrace
>
> Here we have a load operation.  Dunno what address it's trying to load,
> that would be on the Forth stack.  You can access that (if it hasn't been
> reset) with `.s'.
>
>> @                 Called from (ffea5d84)                at  ffea5dae
>
> The rest of it looks to be calling `seek' on some device.
>
>> my-voc            Called from $call-self                at  ffea714a
>> $call-self        Called from $call-method              at  ffea71e0
>>  ffefb8a0
>> $call-method      Called from seek                      at  ffebc7fa
>> execute           Called from $vexecute?                at  ffea62a4
>> $vexecute?        Called from $call-self                at  ffea714e
>> $call-self        Called from $call-method              at  ffea71e0
>>         0
>> execute           Called from catch                     at  ffe9c3f2
>>  ffefefd4
>>         0
>>  ffefebbc
>> catch             Called from op-seek                   at  ffea78f6
>> op-seek           Called from op-seek                   at  ffea7958
>>         0
>
> Here we have the call to load the bootblock.  It was called from the
> command interpreter (`interact').
>
>> (fload)           Called from interact                  at  ffe9eaac
>> execute           Called from catch                     at  ffe9c3f2
>>  ffefefec
>>         0
>>  ffefebd4
>> catch             Called from (quit                     at  ffe9ead0
>>
>
> Eduardo