l4-hackers

l4-hackers@os.inf.tu-dresden.de

2827 discussions

Re: How to log the text when fiasco bootup?
by Björn Döbel 25 Jan '08

25 Jan '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, | I see. My setup here, I only use one machine, loaded with Debian Etch, which | I always reboot all the time in order to test the loaded modules whether | it's working or not. It seems I need to restart all the time to test this | setup (and to see the error messages).. Ron suggested to point you to our documentation about using Qemu for L4, which can be found here: http://wiki.tudos.org/QEmu Bjoern -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHmcn8P5ijxgQLUNkRAjs2AJ9GW/Mdbubt1CiDrxlHnMkQ10ZL9QCfenOB pZvgZRhTaj5+fEF2i0aqqPA= =ajZs -----END PGP SIGNATURE-----

1 0

How to log the text when fiasco bootup?
by wira 25 Jan '08

25 Jan '08

HI all, When I boot up my fiasco and all its modules, how can I collect all the text/logs that appears on my screen for later debugging purpose? Thanks, karipap.

3 2

Re: How to log the text when fiasco bootup?
by Björn Döbel 25 Jan '08

25 Jan '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, | I see. My setup here, I only use one machine, loaded with Debian Etch, which | I always reboot all the time in order to test the loaded modules whether | it's working or not. It seems I need to restart all the time to test this | setup (and to see the error messages).. In this case you should definitely consider using something like Qemu for running Fiasco inside a virtual machine. This will really increase your development speed. Bjoern -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHmZ21P5ijxgQLUNkRAtawAJ9Fs5lQsUOjtXa+gQ+1PElI2ZwmwwCff2Ld SMwzhtzd7jrvh7MJx/BIHxw= =vdUL -----END PGP SIGNATURE-----

1 0

happy hacking yr 2008
by Chirikure Kuda 24 Jan '08

24 Jan '08

1 0

No netwrking
by fang zhengshu 24 Jan '08

24 Jan '08

hi all > today,I've download the newst l4 and l4linux, > I compile the fiasco ,and use the given hello program in /l4/build/../l4v2/hello to test it > the fiasco work well > then I compile the l4linux,and also the l4linux start > but when use the commd "ifconfig",there is no IP. > I compile l4linux use the given config in /arch/l4/configs/x86-native...what's the problem? > anyone help me,thanks! fang

3 2

Re: BID-coding an encapsulate
by Björn Döbel 24 Jan '08

24 Jan '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, | | 1st - why do you build as root? | | Owh, I didn't realize it could affect me more of this privilege. There is no need to build as root and it's usually security risk. | | Ok. So aes_aes256_init is a function defined by your wrapper library? In | this case you should also link your wrapper lib to your application. | This can be done by adding | | | LIBS += -laesclient | | | to the example client's Makefile. | | I did this, but still no clue :( | I attach the archive, thank you. Ok, builds for me after some fixes: * your package dir is called aes, so all include files need to be included through something like <l4/aes/...> * the IDL file somehow needs to know about your aes_context type, so either include it from a header or define it inside the IDL file - I did so by uncommenting your stuff. And this was probably your problem: - ---> * The aes-client.h file should be included using ~ #include "aes-client.h" ~ without any directory prefixes. It is a generated header file which ~ does not end up in the L4 include dir, but resides inside the ~ package's IDL build dir. This is path is different from the usual ~ include paths and is added to your compile run automatically by BID. <--- Regards, Bjoern - -- Dipl.-Inf. Bjoern Doebel Mail: doebel(a)tudos.org TU Dresden, OS Chair Phone: +49 351 463 38 799 Noethnitzer Str. 46 Fax: +49 351 463 38 284 01187 Dresden, Germany -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHmG3aP5ijxgQLUNkRApYXAJ0TMW3ic1bPGVp7UAFRF1QrV0MiagCeJVs/ GZhEKQfn0Eqt60XTaOVCEIU= =keed -----END PGP SIGNATURE-----

1 0

Trouble with l4rm_region_cache slab
by Marc CHALAND 24 Jan '08

24 Jan '08

Hi, I got an application which crashes into slab_alloc (slab.c:358). After some investigation, I've found the faulty slab : l4rm_region_cache. slabs_part != NULL, free_objs == NULL and num_free == 2. My first question is : do you agree this state should not happen ? If yes, I've got the following solutions : 1. there's a bug in slab library, 2. there's a bug in l4rm grow function, 3. synchro problem. It don't believe in 1 or 3. But, in fact, I don't understand l4rm grow mechanism. Another info : one of the analysed crash happened into l4thread_create. Regards Marc

3 6

menu.lst for running flips in L4
by wira 24 Jan '08

24 Jan '08

Hi all, I have already running fiasco and the flips package. But it seems that it stuck after booting up, and panic happens. Here's my menu.lst: title my_assignment root (hd0,0) kernel /boot/fiasco/bootstrap modaddr 0x02000000 module /boot/fiasco/fiasco -nokb module /boot/fiasco/sigma0 module /boot/fiasco/roottask module /boot/fiasco/flips-ore module /boot/fiasco/mini_ifconfig Is my settings correct? what area other modules that I need to load up? Thanks, karipap.

2 1

Re: BID-coding an encapsulate
by Björn Döbel 24 Jan '08

24 Jan '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, |> | The function name in the generated code is always prefixed with the interface and library |> names. In your case, this means that your function is called |> a_aes256_init_call()- as you can also see from the generated - -client.c file. | | I believe this function a_aes256_init_call() is used in the wrapper. I didn't get any | error while compiling my wrapper as well as my server code. Yes I did call | a_aes256_init_call() by it's name in it. However the error that I | received happened while I'm compiling my client code which I call | my function as aes_aes256_init(). I also have included my header | which declared aes_aes256_init(). Here is my error: | - ---------------------------------------------------------------------------- | root@lucy-ubuntu:/home/fiasco/l4/pkg/aes_1/examples/client# make O=/home/fiasco/build/ 1st - why do you build as root? | PWD=/home/fiasco/build/pkg/aes_1/examples/client/OBJ-x86_586-l4v2 make -C /home/fiasco/build/pkg/aes_1/examples/client/OBJ-x86_586-l4v2 -f Makefile | make[1]: Entering directory `/home/fiasco/build/pkg/aes_1/examples/client/OBJ-x86_586-l4v2' | ... Compiling main.o | LD_PRELOAD=/home/fiasco/build/tool/gendep/libgendep.so GENDEP_TARGET=main.o GENDEP_BINARY=cc1 gcc -m32 -c -DUSE_UCLIBC=y - -DRAM_BASE=0x0 -DSYSTEM_x86_586_l4v2 -DARCH_x86 -DCPUTYPE_586 - -DL4API_l4v2 -DCONFIG_L4_CALL_SYSCALLS -DCONFIG_L4_ABS_SYSCALLS - -I/home/fiasco/build/pkg/aes_1/idl/OBJ-x86-l4v2 - -I/home/fiasco/build/include/x86/l4v2 -I/home/fiasco/build/include/l4v2 - -I/home/fiasco/build/include/x86 -I/home/fiasco/build/include - -I/home/fiasco/l4/../dice/include -I/home/drops/include/x86/l4v2 - -I/home/drops/include/l4v2 -I/home/drops/include/x86 - -I/home/drops/include -nostdinc -I/home/fiasco/build/include/x86/uclibc - -I/home/fiasco/build/include/uclibc - -I/home/fiasco/build/include/uclibc++ -I/home/drops/include/x86/uclibc - -I/home/drops/include/uclibc -I/home/drops/include/uclibc++ - -I/usr/lib/gcc/i486-linux-gnu/3.4.6/include -gstabs+ -g -O2 - -fno-strict-aliasing -march=i586 -Wall -Wstrict-prototypes - -Wmissing-prototypes -Wmissing-declarations -fno-common /home/fiasco/l4/pkg/aes_1/examples/client/main.c -o main.o | ==> Linking aesclient | LD_PRELOAD=/home/fiasco/build/tool/gendep/libgendep.so GENDEP_TARGET=aesclient GENDEP_BINARY=ld GENDEP_BINARY_ALT1=ld ld -m elf_i386 -o aesclient /home/fiasco/build/lib/x86_586/crt0.o main.o aes256-client.o -Ttext=0x1100000 --hash-style=sysv - -L/home/fiasco/build/lib/x86_586/l4v2 -L/home/fiasco/build/lib/x86_586 - -L/home/fiasco/build/lib -L/home/drops/lib/x86_586/l4v2 - -L/home/drops/lib/x86_586 -L/home/drops/lib - -T/home/fiasco/build/lib/x86_586/main_stat.ld -laes256 -static - -lgeneric_ts -ll4env -ll4rm -ldm_generic -ldm_mem -lthread -lsemaphore - -llogserver_capsule -lnames -ll4util_root -ll4util -lsigma0 -lroot - -ll4env -ll4env_err -ll4rm -ldm_generic -ldm_mem -lthread -lslab -ll4sys - -nostdlib -luc_c -luclibc_support -u mmap_anon -lc_be_simple_mem - -lc_be_mmap -lc_be_mmap_util -lc_be_l4env_start_stop - -lc_be_minimal_log_io -luc_be_simple_sleep -ll4env -llogserver_capsule - -ll4rm -ldm_generic -ldm_mem -lthread -lgeneric_ts -luc_c /usr/lib/gcc/i486-linux-gnu/3.4.6/libgcc.a -luc_c -ll4sys - -Ttext=0x1100000 --warn-common -gc-sections | main.o: In function `main': | /home/fiasco/l4/pkg/aes_1/examples/client/main.c:20: undefined reference to `aes_aes256_init' | make[1]: *** [aesclient] Error 1 | make[1]: Leaving directory `/home/fiasco/build/pkg/aes_1/examples/client/OBJ-x86_586-l4v2' | make: *** [/home/fiasco/build/pkg/aes_1/examples/client/OBJ-x86_586-l4v2] Error 2 | - ---------------------------------------------------------------------------- Ok. So aes_aes256_init is a function defined by your wrapper library? In this case you should also link your wrapper lib to your application. This can be done by adding LIBS += -laesclient to the example client's Makefile. If this still does not solve your error, please send a archive of your full pkg/aes directory. Bjoern - -- Dipl.-Inf. Bjoern Doebel Mail: doebel(a)tudos.org TU Dresden, OS Chair Phone: +49 351 463 38 799 Noethnitzer Str. 46 Fax: +49 351 463 38 284 01187 Dresden, Germany -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHmEQJP5ijxgQLUNkRArD6AJ0eyDqlC89qSNQNGseyfz/HPIaewwCgmgBp SfYplS6VQbBFANWWsrmcFYo= =KFOv -----END PGP SIGNATURE-----

1 0

L4 env have error when compile
by wira 22 Jan '08

22 Jan '08

Hi all, I checkout the hello package and compile it with gcc and g++-3.4, and it seems fine. But after I checkout the l4env package, and compile everything back, this error appears: o/build/include/uclibc -I/home/fiasco/build/include/uclibc++ -I/home/drops/include/x86/uclibc -I/home/drops/include/uclibc -I/home/drops/include/uclibc++ -I/usr/lib/gcc/i486-linux-gnu/3.4.6/include -gstabs+ -g -O2 -fno-strict-aliasing -march=i586 -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -fno-common -fPIC -U__PIC__ -D__PIC__=1 /home/fiasco/l4/pkg/loader/lib/runtime/helper_dyn.c -o helper_dyn.s.o ==> Linking to shared libloader.s.so LD_PRELOAD=/home/fiasco/build/tool/gendep/libgendep.so GENDEP_TARGET= libloader.s.so GENDEP_BINARY=ld ld -m elf_i386 \ -o libloader.s.so -shared -T/home/fiasco/build/lib/x86_586/main_rel.ld /home/fiasco/build/lib/x86_586/crt0.s.o helper_dyn.s.o -L/home/fiasco/build/lib/x86_586/l4v2 -L/home/fiasco/build/lib/x86_586 -L/home/fiasco/build/lib -L/home/drops/lib/x86_586/l4v2 -L/home/drops/lib/x86_586 -L/home/drops/lib --whole-archive -lsemaphore.p - lthread.p -ldm_generic.p -ldm_mem.p -lslab.p -ll4env_err.p -ll4rm.p - ll4env.p -llogserver.p -lnames.p -lroot.p -lc_be_l4env_start_stop.p -lc_be_minimal_log_io.p -lc_be_simple_mem.p -lc_be_mmap.p -lc_be_mmap_util.p -luclibc_support.p -lgeneric_ts.p -lgeneric_fprov.p -lloaderif.p-ll4util_root.p - lsigma0.p --no-whole-archive -ll4sys.p -ll4util.p -ul4util_reboot -ugetopt_long /usr/lib/gcc/i486-linux-gnu/3.4.6/libgcc.a ld: cannot find -lgeneric_fprov.p make[5]: *** [libloader.s.so] Error 1 make[5]: Leaving directory `/home/fiasco/build/pkg/loader/lib/runtime/OBJ-x86_586-l4v2' make[4]: *** [/home/fiasco/build/pkg/loader/lib/runtime/OBJ-x86_586-l4v2] Error 2 make[4]: Leaving directory `/home/fiasco/l4/pkg/loader/lib/runtime' make[3]: *** [runtime] Error 2 make[3]: Leaving directory `/home/fiasco/l4/pkg/loader/lib' make[2]: *** [lib] Error 2 make[2]: Leaving directory `/home/fiasco/l4/pkg/loader' make[1]: *** [loader.lib] Error 2 make[1]: Leaving directory `/home/fiasco/l4/pkg' make: *** [pkg] Error 2 My question is, is there any different in using the 3.4 and 4.1 version of gcc/g++? It seems that the hello package compiled fine with both of the compiler version, but the l4env package have some error on my machine. Advice needed.. Thanks, karipap

4 3

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

l4-hackers