Messages in this thread | | | Date | Fri, 7 May 1999 13:07:28 -0400 (EDT) | From | Greg Zornetzer <> | Subject | Re: SIGIO on socket disconnect |
| |
On Fri, 7 May 1999 davem@redhat.com wrote:
> Date: Fri, 7 May 1999 13:04:28 +1000 (EST) > From: Stephen Rothwell <Stephen.Rothwell@canb.auug.org.au> > > $ uname -a > Linux col100 2.2.1 #1 Fri Mar 5 14:19:27 EST 1999 i686 unknown > $ ./sigtest > No signal received. > > These are all basically unpatched kernels from source downloaded > from kernel.org. > > please try to reproduce with 2.2.7, 2.2.1 had a terrible number of > networking bugs, some of which had to deal with SIGIO delivery On a redhat 5.2 machine. program compiled with egcs, kernel by gcc:
[gaz ~]$ cat /proc/version Linux version 2.2.7 (root@REMOVED) (gcc version 2.7.2.3) #1 SMP Sat May 1 22:19:31 EDT 1999 [gaz ~]$ uname -a Linux localhost 2.2.7 #1 SMP Sat May 1 22:19:31 EDT 1999 i686 unknown [gaz ~]$ ./test No signal received.
I can also give an strace, but it doesn't look like its much of a help. The SIGIO just doesn't appear to the process. Running glibc 2.0.7-29 from Redhat
Greg Zornetzer - gaz+@andrew.cmu.edu "Light shines brightest in the darkest night" http://www.contrib.andrew.cmu.edu/~gaz
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |