On 09/24/2010 04:39 AM, Denys Vlasenko wrote:
On Thu, 2010-09-23 at 17:38 +0200, Jan Kratochvil wrote:
> On Thu, 23 Sep 2010 17:30:48 +0200, Denys Vlasenko wrote:
>> ABRT already can use external debuginfo store:
>> /etc/abrt/plugins/CCpp.conf has ReadonlyLocalDebugInfoDirs = DIR1:DIR2
>> directive.
>>
>> There is no need to reinvent a special fs for that.
>
> There can be more effective selective download over network by some special
> protocol than just what posix seek/read provides.
Possibly. Is developing a new protocol just for this single use case
worthwhile?
I think HTTP provides all the functionality required via content-length
and range headers.
>> I realize that gdb currently will read entire debuginfo
file,
>> not only some parts of it, but Jan and other tools people
>> know about this inefficiency and this will be improved.
>
> With F14 GDB already only small parts should be read in. Still it is far from
> perfect.
Thanks!
>> It's a bit more complex that simply firing up a wget or yum -
>> "yum install /usr/lib/debug/.build-id/*" wouldn't work -
>> but should be doable.
>
> FYI you cannot currently install two debuginfo rpms for different versions
> and/or architectures of the same package as their
> /usr/lib/debug/usr/bin/*.debug and other files will conflict.
Yes, I know. This is not a problem for this usage case.
In this case, user doesn't want or need to *install* debuginfos per se,
he just needs to download them all. Since their names are unique,
there are no collisions. All debuginfos ever released can coexist
in unpacked form in the same tree.
is there a reason why you can't install multiple debuginfos for the same
package? We've also looked at the direct extraction method, but I'd
rather do something non-special/custom if possible.
thanks,
Andrew
--
Andrew Hecox
Supervisor, Software Engineering
Subscriber Platforms