AIX

As Valgrind announced, 3.3.0 and 3.3.1 version can support AIX 5.3.
But I met a block issue when I used Valgrind on AIX
After installing Valgrind3.3.1 successfully on AIX5.3, I typed the following command of Valgrind:
valgrind -d --tool=memcheck ls
Then, the following result from Valgrind is displayed:
*****************************
-606352:1:debuglog DebugLog system started by Stage 1, level 1 logging requested
--606352:1:launcher tool 'memcheck' requested
--606352:1:launcher searching for client in $PATH
--606352:1:launcher found /usr/bin/ls
--606352:1:launcher client is an XCOFF32 executable
--606352:1:launcher looking for the tool file
--606352:1:launcher doing putenv("AIXTHREAD_SCOPE=S")
--606352:1:launcher doing putenv("MP_SHARED_MEMORY=no")
--606352:1:launcher doing putenv("VALGRIND_STARTUP_PWD_606352_XYZZY=/usr/local/lib/valgrind/ppc32-aix5")
--606352:1:launcher doing fork()
--1569002:1:launcher child: before ptrace
--1569002:1:launcher child: before execve
--1569002:1:launcher child: launcher = /usr/local/lib/valgrind/../../bin/valgrind
--606352:1:launcher parent: waitpid-ing for child
--606352:1:launcher parent: waitpid got pid 1569002
--606352:1:launcher parent: waitpid got status 0x57f
--606352:1:launcher parent: size of bootblock is 888
--606352:1:launcher parent: reading child's /proc/../sysent
--606352:1:launcher parent: reading child's int registers
--606352:1:launcher parent: creating bootblock code ..
--606352:1:launcher parent: .. 50 instructions emitted
--606352:1:launcher parent: ptrace PT_LDINFO got 0
--606352:1:launcher parent: text 0x10000000-0x10006fb2 data 0x300005dc-0x3000154c
--606352:1:launcher parent: text 0xd01450f8-0xd014593e data 0xf032b508-0xf032b630
--606352:1:launcher parent: text 0xd035e380-0xd06084c4 data 0xf02853a0-0xf032acf8
--606352:1:launcher parent: candidate first 0x300005dc last 0x3000154b
--606352:1:launcher parent: page 0x30000000 has 1386 usable bytes
--606352:1:launcher parent: reading page at 0x30000000
--606352:1:launcher parent: adler32 of unz page is 0x32001c4e
--606352:1:launcher parent: free space starts at 0x30000a96 in child
--606352:1:launcher parent: bootblock will be at 0x30000c88 in child
--606352:1:launcher parent: writing page at 0x30000000
--606352:1:launcher parent: set child's pc to 0x30000dd0
--606352:1:launcher parent: set child's r31 to 0x30000c88
--606352:1:launcher parent: detaching child
--1569002:1:debuglog DebugLog system started by Stage 2 (main), level 1 logging requested
--1569002:1:main Welcome to Valgrind version 3.3.1 debug logging
--1569002:1:main aix5: registering syscalls ..
--606352:1:launcher parent: detach got 0
--606352:1:launcher parent: waiting for child to finish
--606352:1:launcher parent: child exited on signal 11
**************************************

Is there Anyone met this issue before? Could you please share your expeirence with me?

My email is -censored-

edit by bakunin: soliciting e-mail responses is against the rules. The reason is that answers given in private are not contributing to the knowledge base.