Date: Sat, 25 Oct 2008 18:29:54 +1030 From: en0f <en0f@bokey.mine.nu> To: Jeremy Chadwick <koitsu@FreeBSD.org> Cc: freebsd-hackers <freebsd-hackers@freebsd.org> Subject: Re: neophyte: tcsetattr() gives 22 error in i386, not in amd64? Message-ID: <4902D1FA.3070003@bokey.mine.nu> In-Reply-To: <20081025075648.GB55339@icarus.home.lan> References: <539c60b90810241534l6bedc5e3s1c2e3162c2a7ff38@mail.gmail.com> <Pine.GSO.4.64.0810241626430.16737@zeno.ucsd.edu> <4902CC86.8030408@bokey.mine.nu> <20081025075648.GB55339@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
Jeremy Chadwick wrote: > On Sat, Oct 25, 2008 at 06:06:38PM +1030, en0f wrote: >> Nate Eldredge wrote: >>> On Fri, 24 Oct 2008, Steve Franks wrote: >>> >>>> Hi, >>>> >>>> I'm getting a 22 errno from tcsetattr() on 7-STABLE i386 in code which >>>> was working under 7-STABLE amd64. Serial device is a ucom (silabs >>>> cp2103). Permissions on /dev/cuaU0 look fine. Cutecom/Minicom >>>> appears to open the port without error... >>> I don't see anything obviously wrong, but I'd bet a bug related to >>> 32/64-bit types. Can you post a complete piece of code that can be >>> compiled and run and demonstrates the problem? Also, try compiling with >>> -Wall -W and investigate any warnings that are produced. >>> >>> By the way, errno 22 is EINVAL, "Invalid argument". perror() is your >>> friend. >> Strange freebsd doesnt document error numbers. On POSIX, errno 22 is >> EINVAL as well (documented in errno(3)). Is this applicable to freebsd? > > /usr/include/errno.h isn't documentation of error numbers? Gahhhhh! But Jeremy, I dont have magic brains to work me way out of source code :) -- en0f
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4902D1FA.3070003>