转发: segment fault for fiasco-ux

halo.duan halo.duan at huawei.com
Thu Dec 14 10:40:52 CET 2006


 

Hi
the linux kernel is 2.6.15-1.2054-FC5, gcc is 4.1.0 20060304.
code is the latest update.

following is screen copy of gdb

Fiasco-UX on Linux 2.6.15-1.2054_FC5 (i686) Mapped 64 MB Memory + 0 KB
Framebuffer + 0 MB Input Area on FD 6

Loading Module 0x00090000-0x00099380 [sigma0] Loading Module
0x00120000-0x002b09e4 [roottask]

Bootstrapping...

Welcome to Fiasco(ux)!
DD-L4(v2)/x86 microkernel (C) 1998-2006 TU Dresden
Rev: Fri Dec  8 18:40:04 2006 compiled with gcc 4.1.0 for Intel Pentium III

Detaching after fork from child process 2486.

Program received signal SIGSEGV, Segmentation fault.
Dirq::alloc (this=0xd242d, t=0xd7b80, ack_in_kernel=-1)
    at /home/halo/l4/kernel/fiasco/src/drivers/ux/processor-ux.cpp:62
62        asm volatile ("cli" : : : "memory");
(gdb)


according to the fiasco-ux documents, the SIGSEGV must be handled by fiasico
registered handler. but I don't know why fiasco generate such enomous number
of SYSSEGV.

so what's happened


best regards


On 12/11/06, halo.duan <halo.duan at huawei.com> wrote:
>
>
> -----邮件原件-----
> 发件人: l4-hackers-bounces at os.inf.tu-dresden.de
> [mailto:l4-hackers-bounces at os.inf.tu-dresden.de] 代表 Udo A. Steinberg
> 发送时间: 2006年12月11日 15:22
> 收件人: l4-hackers at os.inf.tu-dresden.de
> 主题: Re: segment fault for fiasco-ux
>
> On Mon, 11 Dec 2006 09:08:13 +0800 halo.duan (HD) wrote:
>
> HD>     I am newbie for L4 and just downloaded the fiasco last week. 
> HD> as i compiled as ux  and run fiasco hello stuff. loading of sigma0 
> HD> and roottask and irq0 is ok. but nothing displayed. as i use 
> HD> strace attach
> the fiasco
> HD> process, it shown full screen   segment fault. only think i can do is
> "kill
> HD> -9 PID".
> HD>     any sugestion?
>
> What tools did you use to build Fiasco-UX (gcc, binutils, glibc)? Also 
> your globalconfig.out would be helpful as well putting up a tarball of 
> your built binaries on the web somewhere.
>
>                - Udo
>
>
>






More information about the l4-hackers mailing list