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:
REVIEW: https://review.gluster.org/16763 (extras/devel-tools: script to resolve bt addresses) posted (#1) for review on master by Milind Changire (mchangir)
REVIEW: https://review.gluster.org/16763 (extras/devel-tools: script to resolve bt addresses) posted (#2) for review on master by Milind Changire (mchangir)
REVIEW: https://review.gluster.org/16763 (extras/devel-tools: script to resolve bt addresses) posted (#3) for review on master by Milind Changire (mchangir)
REVIEW: https://review.gluster.org/16763 (extras/devel-tools: script to resolve bt addresses) posted (#4) for review on master by Milind Changire (mchangir)
REVIEW: https://review.gluster.org/16763 (extras/devel-tools: script to resolve bt addresses) posted (#5) for review on master by Milind Changire (mchangir)
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>
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/