l4-hackers

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

2827 discussions

Debugging an L4 task
by Derick Swanepoel 02 Jun '05

02 Jun '05

Hi, I am trying to debug an L4 task that double pagefaults before reaching the main function. How should one use the debugger to run a task so it can be debugged without having to break into the debugger later? The backtrace doesn't seem very useful because it looks like a stack overflow due to infinite recursion. Here is the loader output: exec | testtask: Loading exec | testtask: Has no dynamic info exec | testtask: Saved 50936 bytes of symbols exec | testtask: "libloader.s.so" not in library list loader | testtask: Starting sigma0-style application exec | testtask: Packed 37981 bytes of symbols exec | testtask: Packed 60324 bytes of lines loader | testtask,#11: Entry at 00009c7c => 01600000 loader | testtask,#11: Started loader | testtask,#11: Double PF (w) at 0c776bec eip 016290bf (11.00) Here is the backtrace: backtrace (thread 11.00, fp=01629068, pc=016290bf): #1 016290bf : capdigits + 0x12 #2 01604a4f : printchar + 0xcf /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:71 #3 01604c56 : LOG_fputs + 0x26 /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:148 #4 01604dca : outs + 0x2a /home/derick/DROPS/l4/pkg/log/lib/src/logliblinux.c:22 #5 01604970 : flush + 0x20 /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:47 #6 01604a4f : printchar + 0xcf /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:71 #7 01604c56 : LOG_fputs + 0x26 /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:148 #8 01604dca : outs + 0x2a /home/derick/DROPS/l4/pkg/log/lib/src/logliblinux.c:22 #9 01604970 : flush + 0x20 /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:47 #10 01604a4f : printchar + 0xcf /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:71 #11 01604c56 : LOG_fputs + 0x26 /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:148 #12 01604dca : outs + 0x2a /home/derick/DROPS/l4/pkg/log/lib/src/logliblinux.c:22 #13 01604970 : flush + 0x20 /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:47 #14 01604a4f : printchar + 0xcf /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:71 #15 01604c56 : LOG_fputs + 0x26 /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:148 #16 01604dca : outs + 0x2a /home/derick/DROPS/l4/pkg/log/lib/src/logliblinux.c:22 #17 01604970 : flush + 0x20 /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:47 #18 01604a4f : printchar + 0xcf /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:71 #19 01604c56 : LOG_fputs + 0x26 /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:148 #20 01604dca : outs + 0x2a /home/derick/DROPS/l4/pkg/log/lib/src/logliblinux.c:22 #21 01604970 : flush + 0x20 /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:47 #22 01604a4f : printchar + 0xcf /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:71 #23 01604c56 : LOG_fputs + 0x26 /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:148 #24 01604dca : outs + 0x2a /home/derick/DROPS/l4/pkg/log/lib/src/logliblinux.c:22 #25 01604970 : flush + 0x20 /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:47 #26 01604a4f : printchar + 0xcf /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:71 #27 01604c56 : LOG_fputs + 0x26 /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:148 #28 01604dca : outs + 0x2a /home/derick/DROPS/l4/pkg/log/lib/src/logliblinux.c:22 #29 01604970 : flush + 0x20 /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:47 #30 01604a4f : printchar + 0xcf /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:71 #31 01604c56 : LOG_fputs + 0x26 /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:148 #32 01604dca : outs + 0x2a /home/derick/DROPS/l4/pkg/log/lib/src/logliblinux.c:22 #33 01604970 : flush + 0x20 /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:47 #34 01604a4f : printchar + 0xcf /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:71 #35 01604c56 : LOG_fputs + 0x26 /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:148 #36 01604dca : outs + 0x2a /home/derick/DROPS/l4/pkg/log/lib/src/logliblinux.c:22 #37 01604970 : flush + 0x20 /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:47 #38 01604a4f : printchar + 0xcf /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:71 #39 01604c56 : LOG_fputs + 0x26 /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:148 --kernel-bt-follows-- (don't trust w/o frame pointer!!) #1 f0005950 #2 f0004c7e #3 f0009e01 #4 f0009e01 #5 f00053ee #6 f0009a65 #7 f000b3fa #8 f00049ce #9 f000b767 #10 f00086e3 #11 f0004084 #12 f0006931 #13 f00253a2 Thanks in advance, Derick

2 3

IPCs
by Andrew Davenport 02 Jun '05

02 Jun '05

Hello, I am trying to make a simple IPC logger in L4 (by modifying the kernel). I want to eventually log src, dest, and contents of the message. Where would be most effective place in the l4 kernel to do this, and how should I go about getting the message contents -- eg registers, flex pages or strings ? Thanks, Andrew -- Andrew Winter Davenport Georgia Institute of Technology College of Computing www.prism.gatech.edu/~gtg259m

2 1

Thread Class in the kernel
by Andrew Davenport 31 May '05

31 May '05

when I am modifying the L4 fiasco kernel, how do I tell what a Thread's task-id and thread-id are ?

2 1

malloc in tftp server
by Leon Brits 31 May '05

31 May '05

Hi all, I am adding a bit of extra code to the TFTP server and I found that if I malloc() memory that I get the error: ../com/register.c:78: failed assertion `global_registry' I've added the following line... l4_ssize_t l4libc_heapsize = 4*1024; ...to the main file but I still get the error. Any suggestions! Thanks Leon

2 1

Issues on L4linux
by Tiago Jorge 30 May '05

30 May '05

hello... I've been running l4linux in l4env mode for some time, but some errors never ceased to exist. The first error consists on page faulting. The error consists on the dm_phys saying it page faulted correctly, but the task i was running blocks... to what values must or wich commands sould i use in order to increase the memory so that i can proceed with the tasks? The other error happens when i try to reboot. When i halt the system, no problem arises. bue when i try to reboot, the systems always pagefaults... what's the problem with that? thanks for the help Tiago

2 1

Using run with bmodfs as file-provider
by Stefan Kalkowski 27 May '05

27 May '05

Hi, i have a problem with using 'run' and bmodfs as file-provider. When i used tftp everything went fine. But now i have to use bmodfs, because i also need flips and that clashs with tftp. So i gave 'run' the argument '--fprov=BMODFS'. But after a short while it exits: run | our_exit(): Exiting with rc=-2 run | Return reboots, "s" sleeps, "e" kills task, "k" enters L4 kdbg full debugger output can you find here: http://www.inf.tu-dresden.de/~sk852421/fiasco/run.out Here is my menu.lst entry: title=L4Linux-2.6 with DOpE root (nd) kernel /drops/l4/bin/x86_586/l4v2/rmgr -sigma0 task modname "L4Linux task" task modname "l4dope" boot_priority 0xB2 task modname "l4io" boot_priority 0xc0 task modname "bmodfs" module module module module modaddr 0x02000000 vbeset 0x114 module /drops/l4/kernel/fiasco/build/main -nowait -nokdb -serial_esc -comspeed 115200 -comport 1 module /drops/l4/bin/x86_586/l4v2/sigma0 module /drops/l4/bin/x86_586/l4v2/names --events module /drops/l4/bin/x86_586/l4v2/log module /drops/l4/bin/x86_586/l4v2/events module /drops/l4/bin/x86_586/l4v2/dm_phys --events module /drops/l4/bin/x86_586/l4v2/simple_ts --events module /drops/l4/bin/x86_586/l4v2/rtc module /drops/l4/bin/x86_586/l4v2/bmodfs module /drops/l4/bin/x86_586/l4v2/run module /drops/l4/bin/x86_586/l4v2/libloader.s.so module /drops/l4linux-2.6/vmlinuz26 module /drops/scripts/l4linux26-dope module /drops/l4/bin/x86_586/l4v2/l4exec module /drops/l4/bin/x86_586/l4v2/l4dope --l4io --events module /drops/l4/bin/x86_586/l4v2/proxygon module /drops/l4/bin/x86_586/l4v2/l4io --noirq module /drops/l4/bin/x86_586/l4v2/name_server module /drops/l4/bin/x86_586/l4v2/flips-lxdrv module /drops/l4/bin/x86_586/l4v2/mini_ifconfig eth0 192.168.0.2 255.255.255.0 192.168.0.3 module /drops/l4/bin/x86_586/l4v2/webproxy module /drops/l4/bin/x86_586/l4v2/loader --events --fprov=BMODFS run --fprov=BMODFS l4linux26-dope so is it at present possible to use run in combination with bmodfs? For me it looks like that it should be possible. a backtrace of that thread: (c.02) jdb: bt thread=c.02 backtrace (thread c.02, fp=00afff6c, pc=01306ef1): #1 01306ef1 : our_exit + 0x81 /drops/l4/pkg/oskit10_support_l4env/lib/src/exit.c:56 #2 01307bd7 : _exit + 0x17 #3 01307406 : exit + 0x16 #4 00013a17 : __startup_main + 0x37 /drops/l4/pkg/loader/lib/runtime/main.c:83 #5 00015c23 : l4th_thread_start + 0x73 /drops/l4/pkg/thread/lib/src/create.c:72 #6 00018e28 : l4th_thread_entry + 0x18 /drops/l4/pkg/thread/lib/src/l4.c:113 --kernel-bt-follows-- (don't trust w/o frame pointer!!) #1 f0005a70 #2 f0004d8e #3 f000a7b6 #4 f00054fe #5 f0016aad #6 f0006572 #7 f00051a2 #8 f0005c1d #9 f0005a5c #10 f0006335 #11 f0007443 #12 f002683c thank you in advance Stefan -- Stefan Kalkowski GNU PGP-Key: https://www.inf.tu-dresden.de/~sk852421

2 2

Linking a C++ program using pthreads fails
by Derick Swanepoel 26 May '05

26 May '05

Hi, I am busy porting a C++ program that uses pthreads to L4. I am using the l4env_freebsd mode to link against oskit10's thread library. The program compiles fine but linking fails as follows: LD_PRELOAD=/home/derick/DROPS/l4/tool/gendep/libgendep.so GENDEP_TARGET=pthreadtest GENDEP_BINARY=ld gcc -o pthreadtest ../../../../../lib/x86_586/crt0.o Thread.o ../../../lib/framework/OBJ-x86_586-l4v2/{Event,Mutex}.o -loskit_threads -Ttext=0x01600000 -L../../../../../lib/x86_586/l4v2 -L/home/derick/DROPS/drops/lib/x86_586/l4v2 -L../../../../../lib/x86_586 -L/home/derick/DROPS/drops/lib/x86_586 -L../../../../../lib -L/home/derick/DROPS/drops/lib -L../../../../../../oskit10/lib -L../../../../../lib/c++/3.3 -L/home/derick/DROPS/drops/lib/oskit10 -L/home/derick/DROPS/drops/lib/c++/3.3 -T../../../../../lib/x86_586/main_stat.ld -lstdc++ /usr/lib/gcc-lib/i486-linux/3.3.5/libgcc.a -static -loskit10_support_l4env_freebsd.o -ll4env -ll4rm -ldm_generic -ldm_mem -lthread -lsemaphore -lnames -ll4util -lrmgr -ll4env -lomega0 -llogserver -ll4env_err -ll4rm -ldm_generic -ldm_mem -lthread -lslab -ll4sys -nostdlib -Wl,--nostdlib -loskit_freebsd_c -loskit_freebsd_net -loskit_startup -loskit_clientos -loskit_bootp -loskit_linux_fs -loskit_fsnamespace -loskit_diskpart -loskit_linux_dev -loskit10_support_l4env_freebsd_dev -loskit_kern -loskit_lmm -loskit_amm -loskit_freebsd_c -loskit_com /usr/lib/gcc-lib/i486-linux/3.3.5/libgcc.a /usr/lib/gcc-lib/i486-linux/3.3.5/libgcc_eh.a -loskit_freebsd_c -Ttext=0x01600000 -Wl,-gc-sections Thread.o(.text+0x30): In function `Thread::start()': /home/derick/DROPS/l4/pkg/ibridge/server/pthreadtest/OBJ-x86_586-l4v2/../Thread.cpp:15: undefined reference to `pthread_attr_init(pthread_attr*)' Thread.o(.text+0x43):/home/derick/DROPS/l4/pkg/ibridge/server/pthreadtest/OBJ-x86_586-l4v2/../Thread.cpp:17: undefined reference to `pthread_create(void**, pthread_attr const*, void* (*)(void*), void*)' Thread.o(.text+0xb0): In function `SyncedThread::start()': /home/derick/DROPS/l4/pkg/ibridge/server/pthreadtest/OBJ-x86_586-l4v2/../Thread.cpp:36: undefined reference to `pthread_attr_init(pthread_attr*)' Thread.o(.text+0xc3):/home/derick/DROPS/l4/pkg/ibridge/server/pthreadtest/OBJ-x86_586-l4v2/../Thread.cpp:38: undefined reference to `pthread_create(void**, pthread_attr const*, void* (*)(void*), void*)' Thread.o(.text+0x140): In function `Manager::selectWorker()': /home/derick/DROPS/l4/pkg/ibridge/server/pthreadtest/OBJ-x86_586-l4v2/../../../lib/framework/Mutex.h:26: undefined reference to `pthread_mutex_lock(pthread_mutex*)' Thread.o(.text+0x15c):/home/derick/DROPS/l4/pkg/ibridge/server/pthreadtest/OBJ-x86_586-l4v2/../../../lib/framework/Mutex.h:27: undefined reference to `pthread_mutex_unlock(pthread_mutex*)' Thread.o(.text+0x16f): In function `Manager::selectWorker()': /home/derick/DROPS/l4/pkg/ibridge/server/pthreadtest/OBJ-x86_586-l4v2/../Thread.h:33: undefined reference to `sched_yield()' Thread.o(.text+0x1af): In function `Manager::selectWorker()': /home/derick/DROPS/l4/pkg/ibridge/server/pthreadtest/OBJ-x86_586-l4v2/../../../lib/framework/Mutex.h:27: undefined reference to `pthread_mutex_unlock(pthread_mutex*)' ... I manually added -loskit_threads to my LDFLAGS. Am I linking against the right libraries? Thanks in advance. Derick

2 1

running C++ function as THREADCONTROL thread
by Jayesh Salvi 25 May '05

25 May '05

Hi, I looked at the pingpong code and found how a thread is created and activated using THREADCONTROL system call. It uses C function pointers and typecasts them to L4_Word_t which are then passed to threadcontrol system call to run this function as thread. I want to use a C++ function as the thread. But C++ member function pointer seem not to be as simple as C function pointers. Their size changes as well, with the compiler or compiler-options, because of inheritance. Is their any example code that does this? Thanks. -- Jayesh

2 1

Porting C++ apps to L4
by Derick Swanepoel 24 May '05

24 May '05

Hi, I'm busy porting a C++ application to L4. From various comments on the mailing list I know that I cannot make use of exceptions and RTTI, but unfortunately the program links against a library that makes heavy use of both. What should I do? Is there any documentation or guidelines on porting C++ apps to L4? Thanks, Derick

3 3

ANNOUNCE: Pre-virtualization project
by Joshua LeVasseur 20 May '05

20 May '05

The L4Ka team is pleased to announce the release of a new approach to building virtual machines, which we call pre-virtualization. Pre- virtualization is a technique to automate para-virtualization, and is thus a more trustworthy alternative to L4Linux, and yet with the same performance that L4Linux has always achieved on the L4Ka microkernels. Since the virtualization is automated, the final binary (whether Linux 2.6, Linux 2.4, FreeBSD, etc.) can execute on raw hardware, and on a variety of hypervisors. At load time, the binary's virtualization-sensitive instructions are rewritten, and the OS is dynamically linked against an architectural emulation layer. The project has been co-developed with UNSW/NICTA. The project web page is located at: http://l4ka.org/projects/virtualization/afterburn/ The current release supports the L4Ka::Pistachio microkernel and the Xen hypervisor, on x86 hardware. We currently release support only for Linux 2.6 as a guest OS. Other operating systems are under test. This project obsoletes our prior L4Ka L4Linux work. We thus stop support for our L4Linux-2.4 project, and will not publicly release our L4Linux 2.6 project. Enjoy, The L4Ka Development Team

1 0

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