Messages in this thread | | | From | "Bloch, Jack" <> | Subject | RE: your mail | Date | Wed, 3 Dec 2003 08:19:51 -0800 |
| |
Thanks,
I found the problem. I do have errno.h included. I was doing a read of errno after calling perror. If I read it directly after getting the neagtive 0ne back, it contains the right value.
Jack Bloch Siemens ICN phone (561) 923-6550 e-mail jack.bloch@icn.siemens.com
-----Original Message----- From: Linus Torvalds [mailto:torvalds@osdl.org] Sent: Wednesday, December 03, 2003 11:04 AM To: Bloch, Jack Cc: linux-kernel@vger.kernel.org Subject: Re: your mail
On Wed, 3 Dec 2003, Bloch, Jack wrote: > > I try to open a non-existan device driver node file. The Kernel returns a > value of -1 (expected). However, when I read the value of errno it contains > a value of 29. A call to the perror functrion does print out the correct > error message (a value of 2). Why does this happen?
Because you forgot a "#include <errno.h>"? Or you have something else wrong in your program that makes "errno" mean the wrong thing?
Linus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |