Re: glibc broken

[Roland McGrath]

It is important to be clear about what works and what doesn't:

* statically linked user programs
* statically linked user programs that use cthreads
* dynamically linked hurd servers not used in boot (e.g. try some filesytem)
* dynamically linked hurd servers used in boot
  (i.e., update everything but ext2fs.static)

Also test whether running a program via ld.so works,
i.e. /lib/ld.so.1 /bin/foo arg1 arg2

This is how exec gets run.  Try /lib/ld.so.1 /hurd/exec --help.

Chances are that one of these other permutations has the same problem,
whatever the problem is.  Then we can debug a problem case that is less
annoying to debug than the hurd boot.


As to debugging a hurd boot problem, is there a reason you haven't done
this under a sub-hurd and given more detailed information?
i.e. when the machine hangs, did one of the initial tasks die?
Can you use gdb from the main hurd and catch some exception?
etc.