[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#355109: marked as done (libc6.1: ia64 build failure for coreutils)

Your message dated Sun, 02 Apr 2006 23:58:30 +0200
with message-id <44304906.7000306@aurel32.net>
and subject line Bug#355109: libc6.1: ia64 build failure for coreutils
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: libc6.1
Severity: important

http://buildd.debian.org/fetch.php?&pkg=coreutils&ver=5.94-1&arch=ia64&stamp=1141336896&file=log&as=raw

>From the build log:

pwd: ../sysdeps/unix/sysv/linux/getcwd.c:130: __getcwd: Assertion `__libc_errno != 34 || buf != ((void *)0) || size != 0' failed.
pwd: /build/buildd/coreutils-5.94/build-tree/coreutils-5.94/tests/misc/pwd.tmp/25528/zzzzzzzzzzzzzzzzzzzzzzzzzzzzz[...]

The above is part of the build tests. For some reason this assertion
occurs on ia64, but every other architecture builds fine, suggesting a
problem in the ia64 toolchain.

This build failure is going to keep coreutils out of testing, so I'd
really like to get some kind of response. My next step is to disable
build tests on ia64, but I'd really rather fix the bug rather than hide
it (and ignore other potential problems by skipping the tests).

--- End Message ---
--- Begin Message --- 
LaMont Jones wrote:

tags 355109 + patch
--


pwd: ../sysdeps/unix/sysv/linux/getcwd.c:130: __getcwd: Assertion `__libc_errno != 34 || buf != ((void *)0) || size != 0' failed.
pwd: /build/buildd/coreutils-5.94/build-tree/coreutils-5.94/tests/misc/pwd.tmp/25528/zzzzzzzzzzzzzzzzzzzzzzzzzzzzz[...]



The above is part of the build tests. For some reason this assertion
occurs on ia64, but every other architecture builds fine, suggesting a
problem in the ia64 toolchain.


Actually, it will occur on any machine that has PAGE_SIZE >> PATH_MAX

Possible workarounds for coreutils:  Use a path of more than 16384
bytes in length for the test, rather than just more than 4096. :-)

For glibc:  The assertion is bogus.  In fact, the path in question from
this test is more than PATH_MAX bytes in length.  Because
PAGE_SIZE==PATH_MAX, sys_getcwd returns ENAMETOOLONG (since it can't
construct the path in the buffer it's using internally), while ia64 has
enough room to build a path (up to 16K), but not enough room to return
it in the malloced buffer from getcwd(3).
Thanks for all this explanations, I have forwarded them to upstream and he has been convinced to do something. I have just check his patch in the SVN.
As the bug with coreutils has been already fixed in 2.3.6-4 by removing the assertion, I am closing it now. 

--
  .''`.  Aurelien Jarno	            | GPG: 1024D/F1BCDB73
 : :' :  Debian developer           | Electrical Engineer
 `. `'   aurel32@debian.org         | aurelien@aurel32.net
   `-    people.debian.org/~aurel32 | www.aurel32.net

--- End Message ---
Reply to: