This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: trying to understand what's going on with timers and boot process
- From: "Carlos O'Donell" <carlos at systemhalted dot org>
- To: "Mark Seger" <Mark dot Seger at hp dot com>
- Cc: libc-help at sourceware dot org
- Date: Tue, 1 Jul 2008 10:26:19 -0400
- Subject: Re: trying to understand what's going on with timers and boot process
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=by6vVVcy9ws5094y3w7O34kUC9eR5iQ1GQ7YZl5P+Pw=; b=S+JpApOQ7LWd8G9qQRIK3NZ0HyQ7QlUo/7k25BRzVnD35m2CvG8lTrVlFSXp/GV/25 VpICjwODiG42iJ1jNUXv7tJmIMEUUeNWsJPbOUNyb7svhi+ywjfeQ85wreXxAU80TkTN 6h8TFYv62fb+lEuoa2muVyc1jn4LGOIrB9NPY=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=WHFF42qEQs/yOKPbGJplfQikmvcvaX9aM9+xzGGzUVGgR0DCH1ZKLBHygm/QdnmsPO RgiYA9HuNxNO/F7wqIWrY6tjjK1i8OnMMcHWgXmFAo97fG3YnbEb5teka8Nyj/Mc3PUh 5P5I1IE3c2IwHnzf9Kyr6dJwkafUW05N8s4r4=
- References: <486A2C72.9080903@hp.com>
On Tue, Jul 1, 2008 at 9:09 AM, Mark Seger <Mark.Seger@hp.com> wrote:
> My issue is I have an open source program that is dependent on HiRes and is
> being distributed on Fedora 10 and I fear I'm going to start getting a lot
> of support requests over this. I do intend to release a new version that
> checks the version of glibc (I recently discovered I could just run
> /lib/libc.6.so and it tells me its version) and warn people when there is a
> problem, but I'm still stumped with the fact that I've only seen errors on
> 2.5 systems during boot. Can someone shed any light on what I'm seeing?
> Should I be worrying about ALL versions of glibc > 2.3?
The first step is to develop a pure-C test case. Without a test case
it's going to be very hard to debug your problem.
Do you have a test case?
Cheers,
Carlos.