Octavio Alvarez wrote:
> Well, Valgrind says "timer_create(evp)", not timerid and the problem
> apparently relies *inside* eglibc.
Hmm... Regarding valgrind... The coreutils gets run through valgrind
routinely. There are always lots of false positives. Often people
report false positives to us
On 10/05/2013 01:47 PM, Michael Stone wrote:
> Looks like a noise result. Definition of timer_create is:
>
> int timer_create(clockid_t clockid, struct sigevent *sevp, timer_t
> *timerid);
>
> coreutils has:
>
> timer_t timerid;
> if (timer_create (CLOCK_REALTIME, NULL, &timerid) == 0)
> ...
>
On Sat, Oct 05, 2013 at 01:32:25PM -0700, Octavio Alvarez wrote:
Without -dbg, this is what I get in valgrind:
==32492== Syscall param timer_create(evp) points to uninitialised byte(s)
==32492==at 0x4E36E1A: timer_create@@GLIBC_2.3.3 (timer_create.c:83)
==32492==by 0x402607: ??? (in /usr
On 10/05/2013 12:30 PM, Michael Stone wrote:
> On Sat, Oct 05, 2013 at 10:21:55AM -0700, you wrote:
>> I'd like to ask if there is any updates on this bug.
>
> I see a big downside in potential complexity and fragility for the
> system without much upside. The only use case cited ended up being a
On Sat, Oct 05, 2013 at 10:21:55AM -0700, you wrote:
I'd like to ask if there is any updates on this bug.
I see a big downside in potential complexity and fragility for the
system without much upside. The only use case cited ended up being a
library problem rather than a coreutils problem. Is
Hi.
I'd like to ask if there is any updates on this bug.
Thanks.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
6 matches
Mail list logo
