j
: Next unread message k
: Previous unread message j a
: Jump to all threads
j l
: Jump to MailingList overview
Why does just typing "see comp" cause a segmentation fault? Here are the details:
Welcome to OpenBIOS v1.0 built on Aug 12 2012 20:51 Type 'help' for detailed information [unix] Booting default not supported. Trying disk... No valid state has been set by load or init-program
0 > see comp : comp
r 0 -rot r> bounds (?do) panic: segmentation violation at 56
dict=0xb7e50008 here=0xb7e66eec(dict+0x16ee4) pc=0xb7e52ee4(dict+0x2edc) dstackcnt=3 rstackcnt=26 instruction=b7e502ec
I am using the target unix if that helps.
On 14/08/12 00:19, Programmingkid wrote:
Why does just typing "see comp" cause a segmentation fault? Here are the details:
Welcome to OpenBIOS v1.0 built on Aug 12 2012 20:51 Type 'help' for detailed information [unix] Booting default not supported. Trying disk... No valid state has been set by load or init-program
0> see comp : comp
r 0 -rot r> bounds (?do) panic: segmentation violation at 56
dict=0xb7e50008 here=0xb7e66eec(dict+0x16ee4) pc=0xb7e52ee4(dict+0x2edc) dstackcnt=3 rstackcnt=26 instruction=b7e502ec
I am using the target unix if that helps.
Hmmm yeah it probably shouldn't do that. Can you get a debug backtrace to figure out what's happened? I'm fairly tied up over the next few weeks to take a look at this :/
ATB,
Mark.