On Sat, Jan 20, 2001 at 05:44:13PM -0500, Roland McGrath wrote:
> This is pretty confusing to me, but it's hard to see much without being
> able to debug it myself.
>
> First, please check whether the scenario you are trying does or doesn't
> exhibit the same bug in a vanilla system without your changes.
The exact same error.
> Next, here are some things to try. When you attach gdb, look around at the
> state before giving settrans any input. See exactly what is going on in
> the filesystem. It ought to be blocked in diskfs_startup_diskfs's call to
> the fsys_startup RPC. The process state of the filesystem ought to be
> completely set up at that point (before main was called). Look at the libc
> variables _hurd_init_portarray, _hurd_ports, which should by that time
> already show the proc port.
It is blocked in the correct spot. I cannot acces_hurd_init_portarray
(it does not exist?) and _hurd_ports is just a data glob.
> Try attaching gdb, doing something simple like "bt", and then just
> detaching gdb. Then resume settrans and see how the filesystem behaves.
> If that alone makes the filesystem behave funny, then we need to suspect
> that gdb is somehow screwing things up.
On both the vanilla and my hacked up system, I get the same errors.
PGP signature
