Bug 1426891

Summary:	script to resolve function name and line number from backtrace
Product:	[Community] GlusterFS	Reporter:	Milind Changire <mchangir>
Component:	unclassified	Assignee:	Milind Changire <mchangir>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.11.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-05-30 18:45:26 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 Milind Changire 2017-02-26 06:07:23 UTC

Description of problem:
STACK_WINDs in a gluster backtrace dumped in a log file are
undecipherable with only the hex addresses of the location
leaving us without a clue.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
Script should resolve function names and line numbers either using debuginfo or directly from a source install.

Additional info:

Comment 1 Worker Ant 2017-02-26 06:12:14 UTC

REVIEW: https://review.gluster.org/16763 (extras/devel-tools: script to resolve bt addresses) posted (#1) for review on master by Milind Changire (mchangir)

Comment 2 Worker Ant 2017-02-27 05:25:00 UTC

REVIEW: https://review.gluster.org/16763 (extras/devel-tools: script to resolve bt addresses) posted (#2) for review on master by Milind Changire (mchangir)

Comment 3 Worker Ant 2017-02-27 08:04:00 UTC

REVIEW: https://review.gluster.org/16763 (extras/devel-tools: script to resolve bt addresses) posted (#3) for review on master by Milind Changire (mchangir)

Comment 4 Worker Ant 2017-02-28 05:09:15 UTC

REVIEW: https://review.gluster.org/16763 (extras/devel-tools: script to resolve bt addresses) posted (#4) for review on master by Milind Changire (mchangir)

Comment 5 Worker Ant 2017-03-05 16:24:19 UTC

REVIEW: https://review.gluster.org/16763 (extras/devel-tools: script to resolve bt addresses) posted (#5) for review on master by Milind Changire (mchangir)

Comment 6 Worker Ant 2017-03-08 03:52:20 UTC

COMMIT: https://review.gluster.org/16763 committed in master by Vijay Bellur (vbellur) 
------
commit 6ffce4d698a2c9d61820aa31148671b0653fd4c6
Author: Milind Changire <mchangir>
Date:   Tue Feb 28 10:38:19 2017 +0530

    extras/devel-tools: script to resolve bt addresses
    
    Problem:
    STACK_WINDs in a gluster backtrace dumped in a log file are
    undecipherable with only the hex addresses of the location
    leaving us without a clue.
    
    Solution:
    This utility uses the undeciphered lines in the backtrace and the
    associated debuginfo rpm to generate the function name and the file and
    line number associated with the stack frame.
    
    Passing "none" as the debuginfo rpm name will make the script assume
    that you want to resolve against a source install and not a debuginfo
    rpm.
    
    You would need to copy the unresolved lines from the backtrace into a
    file and pass the name of this file to the utility as the input file.
    
    Change-Id: I4d8bc1ae205af37688d03298de49654018bdba9d
    BUG: 1426891
    Signed-off-by: Milind Changire <mchangir>
    Reviewed-on: https://review.gluster.org/16763
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Vijay Bellur <vbellur>

Comment 7 Shyamsundar 2017-05-30 18:45:26 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.11.0, please open a new bug report.

glusterfs-3.11.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://lists.gluster.org/pipermail/announce/2017-May/000073.html
[2] https://www.gluster.org/pipermail/gluster-users/