This is the mail archive of the
mailing list for the elfutils project.
Re: Build IDs for finding packages
- From: Mark Wielaard <mjw at redhat dot com>
- To: elfutils-devel at lists dot fedorahosted dot org
- Date: Fri, 25 Jan 2013 23:08:18 +0100
- Subject: Re: Build IDs for finding packages
On Fri, Jan 25, 2013 at 06:20:08PM +0000, Bruce Dawson wrote:
> That looks like it is just what I'm looking for -- but it failed on the
> first build ID I tried it on. I'm running a recent Fedora build
> (3.6.10-4.fc18.i686) on a VM with libc-2.16.so version 2.16 (compiled
> with gcc version 4.7.2 20121109). The Build ID for libc-2.16.so is
> cf7bdd994de74c7d4a0cff6a0293d96b64681e06, but when I navigate to this URL:
> I get a page that just contains .
> In this particular case I found the .rpm file at
BTW. All packages/versions can be found in koji for fedora. e.g. for glibc:
> but I'm curious as to why darkserver does not seem to be working in this
I admit I don't know. I poked a bit and even for fc17 not all glibc rpms
seem to have been imported. But for example this one is:
Which then gives you lots of buildids to play with like:
with which you can then find the correct .debug file, etc.
But yeah, it is less usefull if it doesn't contain all packages of the
distro. Kushal probably knows more what it will take to get it "complete".
BTW. The source code of darkserver is here:
In case you want to setup your own with other packages imported.