RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 903009 - .debug_line CU does not fit into section
Summary: .debug_line CU does not fit into section
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: rpm
Version: 6.4
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Packaging Maintenance Team
QA Contact: Karel Srot
URL:
Whiteboard:
Depends On:
Blocks: 1075802
TreeView+ depends on / blocked
 
Reported: 2013-01-22 22:29 UTC by Orion Poplawski
Modified: 2018-12-03 18:11 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-07-22 07:02:36 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
libNX_SM.so.6.0 (45.00 KB, application/octet-stream)
2013-05-01 02:55 UTC, Orion Poplawski
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:1452 0 normal SHIPPED_LIVE rpm bug fix and enhancement update 2015-07-20 18:43:47 UTC

Description Orion Poplawski 2013-01-22 22:29:41 UTC
Description of problem:

Trying to build an rpm and I'm getting:

/usr/lib/rpm/debugedit: /builddir/build/BUILDROOT/nx-libs-3.5.0.17-1.20130115gitc8a5fdd.el6.x86_64/usr/lib64/nx/X11/libNX_SM.so.6.0: .debug_line CU does not fit into section

Version-Release number of selected component (if applicable):
rpm-build-4.8.0-27.el6.x86_64

How reproducible:
Seems to happen all the time now.  I was able to build an earlier version of this package fine.

Comment 2 RHEL Program Management 2013-01-26 06:47:30 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 3 Florian Festi 2013-04-04 13:23:35 UTC
This looks like the creation of the debuginfo package fails due to some unexpected data format in the binary library file. With RHEL 6.4 support for the DWARF4 format got added (#858731). May be this solves the problem. Can you please try out the newer version of rpm.

If this doesn't help we need more precise information about the package and most likely about the compiler and build chain used.

Comment 4 Orion Poplawski 2013-05-01 02:55:13 UTC
Created attachment 742085 [details]
libNX_SM.so.6.0

Still the same with rpm-4.8.0-32.el6.x86_64.  I've attached the so, hopefully helpful.

Source is compiled like:
gcc -c -g -O3 -fno-strict-aliasing -g -ansi -Wall -Wpointer-arith -Wundef    -I../.. -I../../exports/include   -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L                                 -D_POSIX_SOURCE -D_XOPEN_SOURCE                             -D_BSD_SOURCE -D_SVID_SOURCE                                 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64                       -D_GNU_SOURCE                             -DFUNCPROTO=15 -DNARROWPROTO -DXTHREADS  -D_REENTRANT -DXUSE_MTSAFE_API         -fPIC sm_client.c

gcc -o ./libNX_SM.so.6.0~ -shared -Wl,-soname,libNX_SM.so.6 sm_client.o sm_genid.o sm_manager.o sm_process.o sm_error.o sm_misc.o sm_auth.o -L../../exports/lib -lNX_ICE -lc

Hmm, not honoring the rpm optflags.  I'll see if I can fix that.

Comment 5 Orion Poplawski 2013-05-01 14:58:33 UTC
There appears to be an associated debugedit segfault:

Core was generated by `/usr/lib/rpm/debugedit -b /builddir/build/BUILD -d /usr/src/debug -i -l /buildd'.
Program terminated with signal 11, Segmentation fault.
#0  buf_read_ule32 (data=0x0) at tools/debugedit.c:111
111     {
(gdb) bt
#0  buf_read_ule32 (data=0x0) at tools/debugedit.c:111
#1  0x0000000000402024 in edit_dwarf2_line (dso=0x1942d00, off=<value optimized out>,
    comp_dir=0x1943f10 "/builddir/build/BUILD/nx-libs-3.5.0.20/nx-X11/lib/X11/xlibi18n/lc/xlocale", phase=<value optimized out>) at tools/debugedit.c:490
#2  0x0000000000402fbb in edit_attributes (dso=0x1942d00) at tools/debugedit.c:948
#3  edit_dwarf2 (dso=0x1942d00) at tools/debugedit.c:1260
#4  0x0000000000404748 in main (argc=<value optimized out>, argv=<value optimized out>)
    at tools/debugedit.c:1593
(gdb) up
#1  0x0000000000402024 in edit_dwarf2_line (dso=0x1942d00, off=<value optimized out>,
    comp_dir=0x1943f10 "/builddir/build/BUILD/nx-libs-3.5.0.20/nx-X11/lib/X11/xlibi18n/lc/xlocale", phase=<value optimized out>) at tools/debugedit.c:490
490       endcu += read_32 (ptr);
(gdb) print ptr
$1 = (unsigned char *) 0x0

475       unsigned char *ptr = debug_sections[DEBUG_LINE].data, *dir;

In edit_dwarf2_line() it looks like debug_sections[DEBUG_LINE].data and hence "ptr" is null.

Comment 6 Susi Lehtola 2013-09-11 18:13:52 UTC
I'm also experiencing the same issue when trying to build json-c-0.11-4.

[Thread debugging using libthread_db enabled]

Program received signal SIGSEGV, Segmentation fault.
buf_read_ule32 (data=0x0) at tools/debugedit.c:111
111	{

(gdb) bt
#0  buf_read_ule32 (data=0x0) at tools/debugedit.c:111
#1  0x0000000000402024 in edit_dwarf2_line (dso=0x60ad80, off=<value optimized out>, comp_dir=0x60bff0 "/builddir/build
/BUILD/json-c-json-c-0.11-20130402", phase=<value optimized out>)
    at tools/debugedit.c:490
#2  0x0000000000402fbb in edit_attributes (dso=0x60ad80) at tools/debugedit.c:948
#3  edit_dwarf2 (dso=0x60ad80) at tools/debugedit.c:1260
#4  0x0000000000404748 in main (argc=<value optimized out>, argv=<value optimized out>) at tools/debugedit.c:1593

(gdb) up
#1  0x0000000000402024 in edit_dwarf2_line (dso=0x60ad80, off=<value optimized out>, comp_dir=0x60bff0 "/builddir/build/BUILD/json-c-json-c-0.11-20130402", phase=<value optimized out>)
    at tools/debugedit.c:490
490	  endcu += read_32 (ptr);

(gdb) print ptr 
$1 = (unsigned char *) 0x0

Comment 7 Susi Lehtola 2013-10-23 17:49:01 UTC
FYI, my issue is on ppc64.

Comment 8 Michel Lind 2014-02-10 04:44:43 UTC
Cc:ing myself, the blocked update to json-c 0.11 is preventing an update of the bti Twitter client (and the previous version no longer works thanks to Twitter changes)

Comment 9 Ľuboš Kardoš 2015-01-05 12:33:19 UTC
The cause of the segmentation fault is the same as in bug 929365. The problem is already fixed upstream: http://rpm.org/gitweb?p=rpm.git;a=commit;h=ea47e7a8169187f87a70ff0c1059e99b0d09e659

Comment 10 Ľuboš Kardoš 2015-03-03 16:16:33 UTC
Devel_ack for adding fix from upstream.

Comment 15 errata-xmlrpc 2015-07-22 07:02:36 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-1452.html


Note You need to log in before you can comment on or make changes to this bug.