Bug 1510735 - Missing symbols in regression core
Summary: Missing symbols in regression core
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: project-infrastructure
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Nigel Babu
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-08 06:30 UTC by Nigel Babu
Modified: 2018-08-29 03:36 UTC (History)
2 users (show)

Fixed In Version: glusterfs-4.1.3 (or later)
Clone Of:
Environment:
Last Closed: 2018-08-29 03:36:14 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Nigel Babu 2017-11-08 06:30:39 UTC
Pasting in Shyam's analysis so we can fix it:

> Problem is due to (2) below, but (1) also needs addressing I think.
>       
> Failed regression that Nigel pointed me to: https://build.gluster.org/job/regression-test-with-multiplex/438/console
> 
> 2 bugs:
> 1) this line https://github.com/gluster/glusterfs-patch-acceptance-tests/blob/master/regression.sh#L27 should have "set pagination off" as follows,
> 
> gdb -c <path to core> -q -ex "set pagination off" -ex "info sharedlibrary" -ex q 2>/dev/null
> 
> 2) this line https://github.com/gluster/glusterfs-patch-acceptance-tests/blob/master/regression.sh#L109 can be changed to:
> 
> gdb -ex 'core-file <path to core>' -ex 'set pagination off' -ex 'info proc exe' -ex q 2>/dev/null | tail -1
> 
> Alternative to the above would be to extract the executable name from,
file <corefile>, but I am not certain the output would be similar on all systems.

Comment 1 Nigel Babu 2017-11-13 05:05:08 UTC
Pushed a patch to fix this based on Shyam's suggestion: https://github.com/gluster/glusterfs-patch-acceptance-tests/pull/103

Comment 2 Amar Tumballi 2018-08-29 03:36:14 UTC
This update is done in bulk based on the state of the patch and the time since last activity. If the issue is still seen, please reopen the bug.


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