On 30.05.2012 16:00, Jiri Svoboda wrote: > Stefan Kalkowski wrote: >> Assuming it doesn't get executed at all, please find out what needs to >> be done, that your example is used as roottask. Is it just a naming >> convention, e.g. the binary has to be named init, or has it to do with >> some special elf-section of the binary, or does it need to be relocated >> to a special address, or something else? > All initial binaries get executed, with the exception of 'loader'. This is > currently > not based on name, however, rather loader is identified by virtue of having > a PT_INTERP header. So, there is nothing special which needs to be done > to get it started. > > I suppose you are able to use the kernel console, so simply using the 'tasks' > command > will show you which taks (a.k.a. processes) are running.
That's exactly what I did, but there is neither another task than the kernel's one, nor another thread than the three ones starting with 'k' - indicating they are kernel-threads I guess. Also building the 'hello' example from Tobias in a way, that it has exactly the same elf-layout (starting with the .init section with the trampoline code in it, at the same address, followed by the .text section etc.) didn't succeeded. I think the only way to get ahead (as long as nobody has another idea) is to instrument the kernel at the point where it loads the elf-binaries, and looking what exactly wents wrong. Regards Stefan > > Cheers > -Jiri > > _______________________________________________ > HelenOS-devel mailing list > [email protected] > http://lists.modry.cz/cgi-bin/listinfo/helenos-devel _______________________________________________ HelenOS-devel mailing list [email protected] http://lists.modry.cz/cgi-bin/listinfo/helenos-devel
