On Wed Mar 18, 2009 at 09:49:32 -0700, Sid Yu wrote:
Ok. With the fault at 0 it's a bit tricky. At the jdb-prompt could you issue a bttd.2 and see if it yields something useful. It should give a backtrace which you can lookup in objdump then.
By bttd.2, do you mean jdb: bt thread = 2 as shown below:
I really meant d.2 and not 2.0.
Looking closer, please start vmlinuz instead of vmlinux.
fprov-l4 is a normal Linux program, it's linked against the host libraries (and a few l4 libs), it's also shared. So the libz.so must be available somewhere for the linking to succeed.
I have already got libz.so in my host library path, I don't know why every time when I compile L4Env, the same error occurred repeatedly.
fprov-l4 is being built statically, so libz.a is needed.
By the way, how could I use the example programs such as fprov-l4 in Fiasco? Could you pls kindly provide some materials or information about it? Thank you very much. Of course, I'd like to have L4Linux run on my machine first.
fprov-l4 is special in the sense that it's a Linux program to be run on L4Linux. fprov-l4 itself is offering the fprov service using the Linux filesystem to get the files. It basically can replace bmodfs after L4Linux is up.
Adam