CentOS - Feb 2015 - debuginfo versioning tools?

On Tue, February 17, 2015 15:20, Les Mikesell wrote:
> Are there any tools to help assemble libraries and debuginfo to
> examine core dumps that happened on another host where the versions
> don't match?  Something like mock but build-version specific and with
> the debuginfo packages pulled in?
>
I am not sure that I understand your question so if this answer is
totally irrelevant then please forgive me.

But, in case this might help, you can configure mock to use locally
provided repos and different architectures via the --configdir
parameter. You provide an architecture specific config file like
epel-6-x86_64.cfg in the specified directory and alter it to require
packages to suit a specific build requirement.

One of mine looks like this:

config_opts['root'] = 'epel-6-x86_64'
config_opts['target_arch'] = 'x86_64'
config_opts['legal_host_arches'] = ('x86_64',)
config_opts['chroot_setup_cmd'] = 'groupinstall buildsys-build'
config_opts['dist'] = 'el6'  # only useful for --resultdir
variable subst

config_opts['yum.conf'] = """
[main]
cachedir=/var/cache/yum
debuglevel=1
reposdir=/dev/null
logfile=/var/log/yum.log
retries=20
obsoletes=1
gpgcheck=0
assumeyes=1
syslog_ident=mock
syslog_device
# repos
[base]
name=BaseOS
enabled=1
mirrorlist=http://mirrorlist.centos.org/?release=6&arch=x86_64&repo=os
failovermethod=priority
exclude=http*

[updates]
name=updates
enabled=1
mirrorlist=http://mirrorlist.centos.org/?release=6&arch=x86_64&repo=updates
failovermethod=priority
exclude=http*

[epel]
name=epel
mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=epel-6&arch=x86_64
failovermethod=priority
exclude=http*

[testing]
name=epel-testing
enabled=0
mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=testing-epel6&arch=x86_64
failovermethod=priority

[local]
name=local
baseurl=file:///home/byrnejb/mock/repos/x86_64/
cost=0
enabled=1

[koji]
name=koji
baseurl=http://kojipkgs.fedoraproject.org/repos/dist-6E-epel-build/latest/x86_64/
cost=2000
enabled=0

[epel-debug]
name=epel-debug
mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=epel-debug-6&arch=x86_64
failovermethod=priority
enabled=0
"""


and one calls it like this:

mock --rebuild --root=epel-6-x86_64 --configdir=/home/byrnejb/mock   
/home/byrnejb/rpmbuild/SRPMS/httpd-2.4.9-1.el6.src.rpm



-- 
***          E-Mail is NOT a SECURE channel          ***
James B. Byrne                mailto:ByrneJB at Harte-Lyne.ca
Harte & Lyne Limited          http://www.harte-lyne.ca
9 Brockley Drive              vox: +1 905 561 1241
Hamilton, Ontario             fax: +1 905 561 0757
Canada  L8E 3C3

On Wed, Feb 18, 2015 at 8:29 AM, James B. Byrne <byrnejb at harte-lyne.ca>
wrote:
>
> On Tue, February 17, 2015 15:20, Les Mikesell wrote:
>> Are there any tools to help assemble libraries and debuginfo to
>> examine core dumps that happened on another host where the versions
>> don't match?  Something like mock but build-version specific and
with
>> the debuginfo packages pulled in?
>>
>
> I am not sure that I understand your question so if this answer is
> totally irrelevant then please forgive me.
I don't think I could actually use mock for this.  It might come close
if I rebuilt all of the libraries and debuginfo packages at the
versions that existed on the host that produced the core dump and ran
gdb in the chroot environment.   But, I don't believe such a rebuild
would be an exact binary match for the builds in the CentOS build
environment and getting all the src rpms at the right versions would
be just as hard as assembling all of the binary rpms and debuginfo
from the vault versions.   I was just hoping that there was some
similar high-level framework to do the tedious work of assembling
everything you need in the right places.

-- 
   Les Mikesell
     lesmikesell at gmail.com