Bug 1545629

Summary:	libreoffice-debuginfo doesn't contain debug info
Product:	Red Hat Enterprise Linux 7	Reporter:	Stephan Bergmann <sbergman>
Component:	libreoffice	Assignee:	Stephan Bergmann <sbergman>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.5	CC:	jkoten, lmiksik, mkrajnak
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-10 12:05:57 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:
Bug Depends On:
Bug Blocks:	1545262

Description Stephan Bergmann 2018-02-15 11:38:26 UTC

Description of problem:
gdb does not show file/line debug info for LibreOffice code.  It appears that libreoffice-5.3.6.1-8.el7 and earlier are erroneously not built with -g.  That makes it hard to track down issues like bug 1545262 (that can only be reproduced sporadically, and for which all we have is a backtrace).

Version-Release number of selected component (if applicable):
libreoffice-5.3.6.1-8.el7

How reproducible:
always

Steps to Reproduce:
1. yum install libreoffice-debuginfo
2. readelf -S /usr/lib/debug/usr/lib64/libreoffice/program/soffice.bin.debug | grep -Fw .debug_info  # resp. .../debug/usr/lib/libreoffice/... on 32-bit systems

Actual results:
no line matching ".debug_info"

Expected results:
a line matching ".debug_info"

Additional info:
For Fedora, this had been fixed with <https://src.fedoraproject.org/rpms/libreoffice/c/9c31acd7ea06a4a32f6c4f49f1a053447f6030ce> "Don't strip -g from RPM_OPT_FLAGS".

Comment 3 Martin Krajnak 2018-02-19 09:46:28 UTC

Verified by reproducer mentioned in Description with:

libreoffice-debuginfo-5.3.6.1-10.el7.x86_64

Comment 6 errata-xmlrpc 2018-04-10 12:05:57 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://access.redhat.com/errata/RHBA-2018:0751