[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: getsockopt() hurd/glibc mismatch

Marcus Brinkmann <Marcus.Brinkmann@ruhr-uni-bochum.de> writes:

> So the linux code should be compiled with glibcs idea of these constants
> already.

I probably jumped to the wrong conclusion, then.

> Now, if you have identified the problem as such by debugging it, [...]

No, I am operating from another machine, and debugging the IP stack one
is using is probably a bad idea.

Can I start another stack with some dummy device? How would I do that,
and how do I instruct client and server to use that instead?

> I suggest to step through pfinet for the getsockopt call. You can
> debug translators just like other programs (set breakpoints, step
> through).

I'll try doing that tonight, when/if I get at the machine.
Because getsockopt(sock, 0, ...) is definitely horked, it always
returns the same bogus data, without flagging an error.


Attachment: signature.ng
Description: PGP signature

Reply to: