Bug 176343 - rg_test fails on x86_64
Summary: rg_test fails on x86_64
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Cluster Suite
Classification: Retired
Component: rgmanager
Version: 4
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Lon Hohberger
QA Contact: Cluster QE
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-12-21 16:44 UTC by Corey Marthaler
Modified: 2009-04-16 20:19 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2006-05-12 17:11:13 UTC


Attachments (Terms of Use)
Fixes behavior (644 bytes, patch)
2005-12-21 17:02 UTC, Lon Hohberger
no flags Details | Diff


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2006:0557 normal SHIPPED_LIVE rgmanager bug fix update 2006-08-10 04:00:00 UTC

Description Corey Marthaler 2005-12-21 16:44:02 UTC
Description of problem:
It failed to detect that I had IPs being used for different services (user
error) which then allowed the services to fail to relocate.

Version-Release number of selected component (if applicable):
[root@taft-02 ~]# rpm -q rgmanager
rgmanager-1.9.44-0

Comment 1 Lon Hohberger 2005-12-21 17:00:54 UTC
Heh, actually, the stock version with 1.9.44 fails to run - it segfaults on
startup. ;)

The version I installed works ;)


Comment 2 Lon Hohberger 2005-12-21 17:02:49 UTC
Created attachment 122498 [details]
Fixes behavior

Preliminary patch.  This makes it work, but reduces the usefulness of
liblalloc's stack checking.  The correct fix is to figure out why accessing
__builtin_return_address(x) causes a segfault on x86_64.

Comment 3 Lon Hohberger 2006-01-04 17:05:56 UTC
The liblalloc's stack checking is architecture dependent. 
__builtin_return_address(x) for x>0 is never guaranteed to work on any
architecture; that it has in the past should be no indication of future performance.


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