- l4-hackers - example.com Site

some newbie questions
by cyberspas＠narod.ru 05 Nov '03

05 Nov '03

Hello l4-hackers, I run my small program as root task on top of Pistachio 0.3 microkernel and receive some errors when it run. All works fine, but when in KDB i try to use change verbose level of sigma0 once and again (about 5-6 times) I receive Assertion: Assertion !tcb->queue_state.is_set(queue_state_t::ready) failed in file /home/tosha/pistachio-0.3/kernel/include/api/v4/schedule.h, line 296 (fn=f010099b2) Can you explain me where is the problem ? Code: #include <l4io.h> #include <l4/kip.h> #include <l4/ipc.h> #include <l4/message.h> #include <l4/kdebug.h> #include <l4/thread.h> int main (void) { printf("Myself: %x\n", L4_Myself().raw); L4_Msg_t msg; L4_ThreadId_t tid; tid = L4_Pager(); L4_MsgClear(&msg); L4_MsgAppendWord(&msg, 1); L4_MsgAppendWord(&msg, 9); L4_Set_Label(&msg.tag, -1001<<4); L4_MsgLoad(&msg); L4_Send(tid); printf("aaa\n"); L4_MsgClear(&msg); L4_MsgAppendWord(&msg, 1); L4_MsgAppendWord(&msg, 9); L4_Set_Label(&msg.tag, -1001<<4); L4_MsgLoad(&msg); L4_Send(tid); while(true) { printf("root\n"); L4_KDB_Enter("enter kdb"); } } -- Best regards, Anton mailto:cyberspas@narod.ru

1 0

Re: AW: L4/Linux communciation with another L4 thread
by Dominik Gummel 16 Oct '03

16 Oct '03

Hi, > I am working on the Perseus (www.perseus-os.org) project > and we are currently using an l4ka kernel. At the moment, we still use L4 V2. Greets, Dominik -- Universität des Saarlandes Department for Computer Science, Security and Cryptography Dominik Gummel email: bofh(a)krypt.cs.uni-sb.de Building 45, Room 536 Im Stadtwald,D-66123 Saarbrücken Tel.: +49(681)302-5608 Fax.: +49(681)302 5636 public key http://www-krypt.cs.uni-sb.de/~bofh Fingerprint 8BED E39C 711C 3ECA B35F E5E7 846D 6661 C091 51AE

1 0

L4/Linux communciation with another L4 thread
by perseus 16 Oct '03

16 Oct '03

@postmaster: Sorry for any inconvenience. had problems with my email application Hi, I am quite new to L4 and I did succeed in writing a server task for L4 and to call this with another L4 thread/program. (Did start them by modifying menu.lst). But I did not find out how I could communicate with an L4/Linux program and another L4 server. I want to send/receive data. Is there any code around that copes with this feature? Thanks, Gerhard

2 2

L4/Linux communication with another L4 Thread
by GLeibrock 15 Oct '03

15 Oct '03

Hi, I am quite new to L4 and I did succeed in writing a server task for L4 and to call this with another L4 thread/program. (Did start them by modifying menu.lst). But I did not find out how I could communicate with an L4/Linux program and another L4 server. I want to send/receive data. Is there any code around that copes with this feature? Thanks, Gerhard

1 0

L4 & Ada
by Frederic BOYER 03 Oct '03

03 Oct '03

Hello I'm plan with a friend (Antoine) to port the L4lib from C to Ada. So, it will be possible to write L4 server in Ada. I'd like to know if someone have already try to do a such thing, and I'd like advices from L4 guru to begin the work. Thanks, Frédéric. "This message, including any attachments may contain confidential and privileged material; it is intended only for the person to whom it is addressed. Its contents do not constitute a commitment by Crédit Agricole Indosuez Cheuvreux except where provided for in a written agreement. Crédit Agricole Indosuez Cheuvreux assumes no liability or responsibility for the consequences arising out of a delay and/or loss in transit of this message, or for corruption or other error(s) arising in its transmission and for any misuse or fraudulent use which may be made thereof. If you are not the intended recipient, please contact us and abstain from any disclosure, use or dissemination. To the extent that this message contains research information and/or recommendations, these are provided on the same basis as Crédit Agricole Indosuez Cheuvreux's published research and the recipient must have regard to all disclosures and disclaimers contained therein."

1 0

about L4 tables
by Yu Neil 29 Sep '03

29 Sep '03

hello: after l4 booted, it will allocate some tables in address, How many memory it will ocuppied ? Neil Yu _________________________________________________________________ 与联机的朋友进行交流，请使用 MSN Messenger: http://messenger.msn.com/cn

2 1

Multiple Test Environments
by David Denny 21 Sep '03

21 Sep '03

Hello L4 There seemed to be a sentiment that your group might appreciate having the Fiasco installation process tested under a variety of Linux distributions. I've had to swap the machine I'd originally acquired for this project, because of video issues with Fiasco (onboard card, Compaq mobo, say no more), so I have a bit more disk space and with careful use of the server I can probably compile/install for between 4 and 6 distributions. Those I have in mind are Debian (as a basic sync point with yourselves). SuSE as an RPM distro, Slackware because it's different, and the two DIY distros LFS and Gentoo. What I envisage is coming back to yourselves _only_ if I have Debian issues, and for the other distros I'm happy to hack my way through and send you back the completed "Expedition Log" for each of them. That is, if you'd like to have something as a resource for other external users to use. I would not expect to ask for help outside Debian. My time is limited so I would tend to go for a major hacking event, from time to time, rather than keeping up with things as they happen At The Centre as it were. I run other free *nixes but my feeling is that at present, as an evaluation envelope, Linux is sufficient for your needs. Looking forward to this, rather

1 0

RE: build error
by "Wen, Jun (溫軍 IAC-N)" 11 Sep '03

11 Sep '03

Hi, thanks,now I am using i386-elf-gcc,but also has some error. would you please give a advise which compiler and which enviroment could compile them pass? i am using fiasco-1.0.tar.gz and fiasco-1.0-oskit.tar.gz BRS john -----Original Message----- From: Volkmar Uhlig [mailto:volkmar@ira.uka.de] Sent: Wednesday, September 10, 2003 11:59 AM To: Wen, Jun (? ? IAC-N) Cc: l4-hackers(a)os.inf.tu-dresden.de Subject: RE: build error Using the native cygwin compiler will quite likely make you pulling your hair out. Try building a cross compiler for linux and elf and use that instead. The PE standard the cygwin gcc spits out conflicts with many assumptions in asm code and linker files, such as naming conventions of sections, symbols, etc. - Volkmar

1 0

RE: build error
by Volkmar Uhlig 10 Sep '03

10 Sep '03

Using the native cygwin compiler will quite likely make you pulling your hair out. Try building a cross compiler for linux and elf and use that instead. The PE standard the cygwin gcc spits out conflicts with many assumptions in asm code and linker files, such as naming conventions of sections, symbols, etc. - Volkmar

1 0

RE: build error
by "Wen, Jun (溫軍 IAC-N)" 10 Sep '03

10 Sep '03

Hi thanks for reply quickly.follow advise it shows below. BRS john make -I../src -f ../src/Makefile \ srcdir=../src "all" Reading specs from /usr/lib/gcc-lib/i686-pc-cygwin/3.2/specs make[1]: Entering directory `/cygdrive/f/fiasco-1.0/l4/kernel/fiasco/build' ... Making context-ia32-ux.o g++ -v -c -MD -I../src/types/ia32 -I../src/types -I../src/drivers/ia32 -I../src/ drivers -I../src/kern/ia32 -I../src/kern/shared -I../src/kern -I../src/boot -I.. /src/lib/libk/ia32 -I../src/lib/libk -I../src/lib/kern/include -I../src/lib/amm -I../src/lib/lmm -I../src/lib/gzip -I../src/lib/disasm -I../src/lib/minilibc/ia3 2/include -I../src/lib/minilibc/include -I. -Iauto -fno-rtti -fno-exceptions - march=i586 -fomit-frame-pointer -mpreferred-stack-boundary=2 -fno-defer-pop -fr eg-struct-return -g -Wall -W -finline-limit=2000 -O3 auto/context-ia32-ux. cc - o context-ia32-ux.o Reading specs from /usr/lib/gcc-lib/i686-pc-cygwin/3.2/specs Configured with: /netrel/src/gcc-3.2-3/configure --enable-languages=c,c++,f77,ja va --enable-libgcj --enable-threads=posix --with-system-zlib --enable-nls --with out-included-gettext --enable-interpreter --disable-sjlj-exceptions --disable-ve rsion-specific-runtime-libs --enable-shared --build=i686-pc-linux --host=i686-pc -cygwin --target=i686-pc-cygwin --enable-haifa --prefix=/usr --exec-prefix=/usr --sysconfdir=/etc --libdir=/usr/lib --includedir=/nonexistent/include --libexecd ir=/usr/sbin Thread model: posix gcc version 3.2 20020927 (prerelease) /usr/lib/gcc-lib/i686-pc-cygwin/3.2/cc1plus.exe -v -I../src/types/ia32 -I.. /src /types -I../src/drivers/ia32 -I../src/drivers -I../src/kern/ia32 -I../src/kern/s hared -I../src/kern -I../src/boot -I../src/lib/libk/ia32 -I../src/lib/libk -I../ src/lib/kern/include -I../src/lib/amm -I../src/lib/lmm -I../src/lib/gzip -I../sr c/lib/disasm -I../src/lib/minilibc/ia32/include -I../src/lib/minilibc/include -I . -Iauto -MD context-ia32-ux.d -MQ context-ia32-ux.o -D__GNUC__=3 -D__GNUC_MINOR __=2 -D__GNUC_PATCHLEVEL__=0 -D__GXX_ABI_VERSION=102 -D_X86_=1 -D_X86_=1 -Asyste m=winnt -D__OPTIMIZE__ -D__STDC_HOSTED__=1 -Acpu=i386 -Amachine=i386 -Di386 -D__ i386 -D__i386__ -D__i586 -D__i586__ -D__pentium -D__pentium__ -D__tune_i586__ -D __tune_pentium__ -D__stdcall=__attribute__((__stdcall__)) -D__fastcall=__attribu te__((__fastcall__)) -D__cdecl=__attribute__((__cdecl__)) -D_stdcall=__attribute __((__stdcall__)) -D_fastcall=__attribute__((__fastcall__)) -D_cdecl=__attribute __((__cdecl__)) -D__declspec(x)=__attribute__((x)) -D__i386__ -D__i386 -D__CYGWI N32__ -D__CYGWIN__ -Dunix -D__unix__ -D__unix -isystem /usr/lib/gcc-lib/i686-pc- cygwin/3.2/../../../../include/w32api -isystem /usr/lib/gcc-lib/i686-pc-cygwin/3 .2/../../../../i686-pc-cygwin/lib/../../include/w32api auto/context-ia32-ux. cc - D__GNUG__=3 -D__DEPRECATED -quiet -dumpbase context-ia32-ux.cc -march=i586 -mpre ferred-stack-boundary=2 -g -O3 -Wall -W -version -fno-rtti -fno-exceptions -fomi t-frame-pointer -fno-defer-pop -freg-struct-return -finline-limit=2000 -o /cygdr ive/c/DOCUME~1/INC970~1/LOCALS~1/Temp/ccNnjfaX.s GNU CPP version 3.2 20020927 (prerelease) (cpplib) (80386, BSD syntax) GNU C++ version 3.2 20020927 (prerelease) (i686-pc-cygwin) compiled by GNU C version 3.2 20020927 (prerelease). ignoring nonexistent directory "/usr/local/include" ignoring nonexistent directory "/usr/i686-pc-cygwin/include" ignoring duplicate directory "/usr/i686-pc-cygwin/lib/../../include/w32api" #include "..." search starts here: #include <...> search starts here: ../src/types/ia32 ../src/types ../src/drivers/ia32 ../src/drivers ../src/kern/ia32 ../src/kern/shared ../src/kern ../src/boot ../src/lib/libk/ia32 ../src/lib/libk ../src/lib/kern/include ../src/lib/amm ../src/lib/lmm ../src/lib/gzip ../src/lib/disasm ../src/lib/minilibc/ia32/include ../src/lib/minilibc/include . auto /usr/include/w32api /usr/include/c++/3.2 /usr/include/c++/3.2/i686-pc-cygwin /usr/include/c++/3.2/backward /usr/lib/gcc-lib/i686-pc-cygwin/3.2/include /usr/include End of search list. /usr/lib/gcc-lib/i686-pc-cygwin/3.2/../../../../i686-pc-cygwin/bin/as.exe --tra ditional-format -o context-ia32-ux.o /cygdrive/c/DOCUME~1/INC970~1/LOCALS~1/Temp /ccNnjfaX.s /cygdrive/c/DOCUME~1/INC970~1/LOCALS~1/Temp/ccNnjfaX.s: Assembler messages: /cygdrive/c/DOCUME~1/INC970~1/LOCALS~1/Temp/ccNnjfaX.s:826: Error: unknown pseud o-op: `.previous' make[1]: *** [context-ia32-ux.o] Error 1 make[1]: Leaving directory `/cygdrive/f/fiasco-1.0/l4/kernel/fiasco/build' make: *** [all] Error 2 -----Original Message----- From: Udo A. Steinberg [mailto:us15@os.inf.tu-dresden.de] Sent: Wednesday, September 10, 2003 9:24 AM To: l4-hackers(a)os.inf.tu-dresden.de Subject: Re: build error _______________________________________________ l4-hackers mailing list l4-hackers(a)os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers

1 0