> > You might turn on some of the libc debugging stuff when starting pfinet.
>
> Can you be more specific?
I meant the malloc debugging stuff. There are some environment variables.
Look in the libc sources.
> Attached. Hope it helps.
That backtrace definitely looks bogus.
> esp
On Wed, Jan 17, 2001 at 12:06:51AM -0500, Roland McGrath wrote:
> > Seriously, I think this is some trouble with the condition_wait/select
> > stuff. Pending bytes don't seem to be delivered or wake a waiting select.
>
> Well, we know that much. We need to get more specific. That's why I
> want
> I didn't follow that track, because it was coming from libwrap (tcp
> wrapper), and I was not set up to debug there. Instead, I let inetd start
> telnetd directly, and attached gdb to pfinet before doing so.
tcpd just execs telnetd after doing the access check. So when you have an
open connect
On Tue, Jan 16, 2001 at 05:59:47AM -0500, Roland McGrath wrote:
> The IP options are bogus--they are not really there. Figure out how it is
> that telnetd thinks it is getting IP options. Whatever is returning an
> indication of IP options must be a bug (in libc or pfinet).
I didn't follow that
The IP options are bogus--they are not really there. Figure out how it is
that telnetd thinks it is getting IP options. Whatever is returning an
indication of IP options must be a bug (in libc or pfinet).
F_SETOWN might in fact not work, I guess it should. That translates to
io_mod_owner. Is
