summaryrefslogtreecommitdiff
path: root/Hurd
diff options
context:
space:
mode:
authorThomas Schwinge <tschwinge@gnu.org>2007-02-16 17:30:00 +0000
committerThomas Schwinge <tschwinge@gnu.org>2007-02-16 17:30:00 +0000
commitf9a4aa9af2977a5862461c683290f5b5cf39d5ab (patch)
treedd88ce7601c4f8592fef8ed95aac59e9f64b2154 /Hurd
parentdb16a76032ed5bde03f08724fbcebb3278a18363 (diff)
none
Diffstat (limited to 'Hurd')
-rw-r--r--Hurd/DebuggingGlibc.mdwn31
1 files changed, 28 insertions, 3 deletions
diff --git a/Hurd/DebuggingGlibc.mdwn b/Hurd/DebuggingGlibc.mdwn
index 71573b0b..251e64c0 100644
--- a/Hurd/DebuggingGlibc.mdwn
+++ b/Hurd/DebuggingGlibc.mdwn
@@ -12,17 +12,42 @@ First step is having the build a glibc complete. This involves at one point that
If building glibc succeeds, the next thing to try is running the test suite, or parts of it.
+Here is a list of known failures:
+
+[TODO].
+
----
-Make sure static linking is working ok at all. The _elf/sln_ program in the glibc build ought to test that.
+Make sure static linking is working ok at all. The _elf/sln_ program (a stripped-down _ln_ that is statically linked) in the glibc build ought to test that. Also, static linking under various conditions will already have been tested when running the test suite, especially in _elf/_ and _dlfcn/_.
+
+Make sure static linking with cthreads is working. If you can get an _ext2fs.static_ compiled and linked against the new glibc, that is good.
+
+[TODO].
+
+Then debug its startup as a normal program on your working hurd.
+
+ $ [...]/ext2fs.static --help
+ [...]
-Make sure static linking with cthreads is working. If you can get an _ext2fs.static_ compiled and linked against the new glibc, 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_.
+Then try its full server startup.
+
+ $ settrans -ca node [...]/ext2fs.static <BACKEND>
+ $ cd node/
+ [...]
Make sure dynamic linking for servers is working. If you haven't broken the ABI, you can just use an existing _/hurd/foobar_ binary, started the way glibc's _testrun.sh_ does it.
+[TODO]: Is this the correct way to do that?
+
+ $ settrans -ca node [glibc]/build/testrun.sh /hurd/ext2fs <BACKEND>
+ $ cd node/
+ [...]
+
----
-Test it in a subhurd.
+Test it in a subhurd. See [[SubhurdHowto]] for the basics about subhurds.
+
+<http://lists.gnu.org/archive/html/bug-hurd/2007-02/msg00030.html>
----