Red Hat Bugzilla – Bug 445413
device-mapper-multipath-debuginfo package incomplete
Last modified: 2010-01-11 21:31:58 EST
Description of problem:
Does not have full source and so installation does not help with debugging much.
# rpm -ql device-mapper-multipath-debuginfo-0.4.5-31.el4
[root@rhel4u5-node1-dwysocha scripts]# gdb
GNU gdb Red Hat Linux (188.8.131.52-1.153.el4_6.2rh)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu"...Using host libthread_db
1096 main.c: No such file or directory.
Version-Release number of selected component (if applicable):
Some of the Makefiles were stripping the binaries. Now all binaries are compiled
with debugging enabled, and are not stripped by the Makefiles
Where is this package? I still do not see the source. I'm looking in:
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
Release note added. If any revisions are required, please set the
"requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly.
All revisions will be proofread by the Engineering Content Services team.
* the Makefiles for some of the multipath tools were stripping the binaries, which would make debugging impossible. Now all binaries are compiled with debugging enabled.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.