[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
RE: setsockopt() compat issue
My point was to try seeing if that was the cause of the bug, or if there is
something else wrong with setsockopt() on Alpha builds in 4.0. If the
function works fine with a 32bit value vs. a 64bit value, then we can start
looking at that for the problem. If both 32bit values and 64bit values give
the error, then we'll know to look at something else.
I've tested on an 80x86 machine, and both 32bit and 64bit values are
accepted fine, but I do not have an Alpha machine to test with.
Behalf Of Manuel Bouyer
Sent: Thursday, October 16, 2008 10:05 AM
To: Bryce Simonds
Subject: Re: setsockopt() compat issue
On Thu, Oct 16, 2008 at 09:41:18AM -0500, Bryce Simonds wrote:
> Have you tried using a 32bit integer instead of a 64bit integer?
No and it's not the point: this binary runs fine with a 3.1 kernel,
it should run with a -current one.
Manuel Bouyer, LIP6, Universite Paris VI.
NetBSD: 26 ans d'experience feront toujours la difference
No virus found in this incoming message.
Checked by AVG - http://www.avg.com
Version: 8.0.173 / Virus Database: 270.8.1/1728 - Release Date: 10/16/2008
Main Index |
Thread Index |