Bug 761983 (GLUSTER-251)

Summary: Improve booster debugging through ld-preload testing tool
Product: [Community] GlusterFS Reporter: Shehjar Tikoo <shehjart>
Component: boosterAssignee: Shehjar Tikoo <shehjart>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: mainlineCC: gluster-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: RTNR Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Shehjar Tikoo 2009-09-08 11:01:49 UTC 
There are often reports of booster not working. As a first step we try to investigate whether the syscall in an application is being redirected into booster. This is a hard task because it requires the use of a combination of tools like gdb, compilers and the right libc. This still does not help us determine whether the LD_PRELOAD mechanism works at all for booster on the user's machine.

WE need a tool that the user can execute on his machine, send us the output so we can determine which calls can be handled by booster and which ones are handled by libc. Of course, this is only the first step in debugging booster but it helps a lot in avoiding the effort needed for gdb-based debugging of booster and libglusterfsclient right away.
Comment 1 Anand Avati 2009-09-15 04:01:53 UTC 
PATCH: http://patches.gluster.com/patch/1352 in master (extras: Add LD_PRELOAD test tool)
Comment 2 Anand Avati 2009-09-15 04:02:00 UTC 
PATCH: http://patches.gluster.com/patch/1353 in release-2.0 (extras: Add LD_PRELOAD test tool)