Bug 1444427

Summary:	[icu] libicudata.so.57.1.debug lacks debug info
Product:	[Fedora] Fedora	Reporter:	Joachim Frieben <jfrieben>
Component:	icu	Assignee:	Eike Rathke <erack>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	26	CC:	denis.arnaud_fedora, erack
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-04-24 11:16:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Joachim Frieben 2017-04-21 10:13:31 UTC

Description of problem:
Debug info file /var/cache/abrt-di/usr/lib/debug/usr/lib64/libicudata.so.57.1.debug has been built without debug info as can be verified by querying its file properties.

Version-Release number of selected component (if applicable):
libicu-57.1-4.fc26

How reproducible:
Always

Steps to Reproduce:
1. run 'file /var/cache/abrt-di/usr/lib/debug/usr/lib64/libicudata.so.57.1.debug'.

Actual results:
The output of 'file' is missing attribute "with debug_info".

Expected results:
The output of 'file' contains attribute "with debug_info".

Additional info:
As a consequence, any backtrace invoking the latter is unusable for the problem reporting tool.

Comment 1 Eike Rathke 2017-04-21 11:06:51 UTC

As the name may suggest it is a data library, what calls do you expect to appear in a backtrace?

% readelf -s /usr/lib64/libicudata.so

Symbol table '.dynsym' contains 13 entries:
   Num:    Value          Size Type    Bind   Vis      Ndx Name
     0: 0000000000000000     0 NOTYPE  LOCAL  DEFAULT  UND 
     1: 00000000000004f0     0 SECTION LOCAL  DEFAULT    8 
     2: 0000000000000000     0 NOTYPE  WEAK   DEFAULT  UND _ITM_deregisterTMCloneTab
     3: 0000000000000000     0 NOTYPE  WEAK   DEFAULT  UND __gmon_start__
     4: 0000000000000000     0 NOTYPE  WEAK   DEFAULT  UND _Jv_RegisterClasses
     5: 0000000000000000     0 NOTYPE  WEAK   DEFAULT  UND _ITM_registerTMCloneTable
     6: 0000000000000000     0 FUNC    WEAK   DEFAULT  UND __cxa_finalize.5 (2)
     7: 00000000019e4000     0 NOTYPE  GLOBAL DEFAULT   21 _edata
     8: 00000000019e4008     0 NOTYPE  GLOBAL DEFAULT   21 _end
     9: 00000000019e4000     0 NOTYPE  GLOBAL DEFAULT   21 __bss_start
    10: 0000000000000640     0 OBJECT  GLOBAL DEFAULT   13 icudt56_dat
    11: 00000000000004f0     0 FUNC    GLOBAL DEFAULT    8 _init
    12: 0000000000000630     0 FUNC    GLOBAL DEFAULT   12 _fini

Comment 2 Joachim Frieben 2017-04-22 07:15:53 UTC

Reporting bug 1442680 suffers from an unusable backtrace, both using the retrace server and installing debuginfo files locally on the affected system. A likely reason for this failure appears to be the absence of debugging info in file libicudata.so.57.1.debug which might mislead abrt:

From                To                  Syms Read   Shared Object Library
..
0x00007ffa75f3c510  0x00007ffa75f3c610  Yes (*)     /lib64/libicudata.so.57
..
(*): Shared library is missing debugging information.

Comment 3 Eike Rathke 2017-04-24 10:39:19 UTC

"Backtrace is unusable because libicudata.so.57.1.debug has been built without debug info" is a rather broad claim in the bug linked. libicudata isn't even involved in the backtrace, it's only listed as it happened to be memory mapped at that point of time (which it ~always is because of its low level nature). If the backtrace would be unusable because of that then ~every backtrace would. Since ages and generations. This claim is an assumption without evidence.