bug-gnulib
[Top][All Lists]
Advanced

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

Re: test-utimens.h:105: assertion failed


From: Simon Josefsson
Subject: Re: test-utimens.h:105: assertion failed
Date: Mon, 02 Nov 2009 12:04:28 +0100
User-agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.1 (gnu/linux)

Eric Blake <address@hidden> writes:

> According to Simon Josefsson on 10/30/2009 2:32 AM:
>> A (f)utimens test fail on Ubuntu 8.04 LTS:
>
> Thanks for the report.  Which kernel and which version of glibc?  Is it a
> machine I might have access to, like the gcc compile farm?

Send me your SSH public key and preferred username and I'll give you
access to it, it is a virtual Ubuntu 8.04 LTS instance on slicehost.
Info:

Linux gaggia 2.6.24-23-xen #1 SMP Mon Jan 26 03:09:12 UTC 2009 x86_64 GNU/Linux
GNU C Library stable release version 2.7, by Roland McGrath et al.
Copyright (C) 2007 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Compiled by GNU CC version 4.2.4 (Ubuntu 4.2.4-1ubuntu4).
Compiled on a Linux >>2.6.24-23-server<< system on 2009-08-17.
Available extensions:
        crypt add-on version 2.1 by Michael Glad and others
        GNU Libidn by Simon Josefsson
        Native POSIX Threads Library by Ulrich Drepper et al
        BIND-8.2.3-T5B
For bug reporting instructions, please see:
<http://www.gnu.org/software/libc/bugs.html>.

>> I can't reproduce on current debian testing, so it is likely an old bug.
>
> The Linux man pages are explicit that older kernels had a bug where
> UTIME_OMIT with a non-zero seconds field failed with EINVAL instead of
> working, but I thought my code path already worked around this.  Can you
> check what errno was set to?  Or even better, single-step through
> utimens.c at that point to see why validate_timespec() doesn't seem to be
> doing the trick.

Errno is EINVAL.  I can single-step if the other information in this
e-mail isn't sufficient, let me know.

> Also, an strace run would be invaluable, to see what actual arguments were
> passed to the syscall.

Attached.

/Simon

Attachment: utimens-strace.txt.gz
Description: Binary data


reply via email to

[Prev in Thread] Current Thread [Next in Thread]