From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1237 invoked by alias); 10 Mar 2006 17:12:24 -0000 Received: (qmail 1223 invoked by uid 48); 10 Mar 2006 17:12:20 -0000 Date: Fri, 10 Mar 2006 17:12:00 -0000 Message-ID: <20060310171220.1222.qmail@sourceware.org> From: "decimal at us dot ibm dot com" To: glibc-bugs@sources.redhat.com In-Reply-To: <20060305165257.2417.aurelien@aurel32.net> References: <20060305165257.2417.aurelien@aurel32.net> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug libc/2417] getcwd() uses ENAMETOOLONG instead of ERANGE X-Bugzilla-Reason: CC Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org X-SW-Source: 2006-03/txt/msg00051.txt.bz2 List-Id: ------- Additional Comments From decimal at us dot ibm dot com 2006-03-10 17:12 ------- When you say "on all architectures but ia64" do you mean this is true for the generic kernel or is this Debian specific? On OpenSUSE x86 10.0 I get ERANGE. I do not see why glibc should put in a patch to work around a bug in the kernel. This bug should be fixed in the kernel only. If glibc put in a workaround for every simple kernel bug which code be fixed the code would quickly become unmanageable. -- http://sourceware.org/bugzilla/show_bug.cgi?id=2417 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.