[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Debugging glibc / startup stuff via a subhurd
From: |
Roland McGrath |
Subject: |
Re: Debugging glibc / startup stuff via a subhurd |
Date: |
Sun, 11 Feb 2007 12:37:30 -0800 (PST) |
Before you start trying a subhurd, you should try that libc for running
an individual hurd server. Then you can debug the cthreads/hurd-server
issues first without dealing with all the bootstrap issues.
First, make sure static linking is working ok at all. The elf/sln program
in the libc build ought to test that.
Second, make sure static linking with cthreads is working. If you can get
an ext2fs.static compiled/linked against the new libc, that is good. Then
debug its startup as a normal program on your working hurd, i.e. just run
it with --help. Then try its full server startup, i.e. settrans -a.
Next, make sure dynamic linking for servers is working. If we haven't
broken the ABI, you can just use an existing /hurd/foobar binary,
started the way libc's testrun.sh does it.
Only after all that is going, would I recommend trying an actual subhurd.
The bootstrap is the harder way to debug all the component issues involved.