I have been able to compile and install Valgrind 3.4.1 on an AIX 5.3
system, but when I attempt to run it, I get a segmentation fault and
this output (using the -d option):
--831682:1:debuglog DebugLog system started by Stage 1, level 1 logging
requested
--831682:1:launcher tool 'memcheck' requested
--831682:1:launcher searching for client in $PATH
--831682:1:launcher found .//a.out
--831682:1:launcher client is an XCOFF64 executable
--831682:1:launcher looking for the tool file
--831682:1:launcher doing putenv("AIXTHREAD_SCOPE=S")
--831682:1:launcher doing putenv("MP_SHARED_MEMORY=no")
--831682:1:launcher doing
putenv("VALGRIND_STARTUP_PWD_831682_XYZZY=/opt/sas/msd/cm/projects/videre/JB/valgrind")
--831682:1:launcher doing fork()
--827552:1:launcher child: before ptrace
--827552:1:launcher child: before execve
--827552:1:launcher child: launcher =
/opt/sas/msd/cm/projects/videre/JB/valgrind/lib/valgrind/../../bin/valgrind
--831682:1:launcher parent: waitpid-ing for child
--831682:1:launcher parent: waitpid got pid 827552
--831682:1:launcher parent: waitpid got status 0x57f
--831682:1:launcher parent: size of bootblock is 888
--831682:1:launcher parent: reading child's /proc/../sysent
--831682:1:launcher parent: reading child's int registers
--831682:1:launcher parent: creating bootblock code ..
--831682:1:launcher parent: .. 57 instructions emitted
--831682:1:launcher parent: ptrace PT_LDINFO got 0
--831682:1:launcher parent: text 0x100000000-0x1000008ad data
0x11000054b-0x110000668
--831682:1:launcher parent: text 0x9fffffff0000000-0x9fffffff000b30a data
0x9fffffff000b30a-0x9fffffff000b30a
--831682:1:launcher parent: text 0x900000000129280-0x900000000129cab data
0x9001000a00d4760-0x9001000a00d4900
--831682:1:launcher parent: text 0x90000000032cd00-0x90000000061151c data
0x9001000a0000db8-0x9001000a00d3ee8
--831682:1:launcher parent: candidate first 0x11000054b last 0x110000667
--831682:1:launcher parent: page 0x110000000 has 2759 usable bytes
--831682:1:launcher parent: reading page at 0x110000000
--831682:1:launcher parent: adler32 of unz page is 0x49910a42
--831682:1:launcher parent: free space starts at 0x110000539 in child
--831682:1:launcher parent: bootblock will be at 0x110000c88 in child
--831682:1:launcher parent: writing page at 0x110000000
--831682:1:launcher parent: set child's pc to 0x110000dd0
--831682:1:launcher parent: set child's r31 to 0x110000c88
--831682:1:launcher parent: detaching child
--831682:1:launcher parent: detach got 0
--831682:1:launcher parent: waiting for child to finish
--827552:1:debuglog DebugLog system started by Stage 2 (main), level 1 logging
requested
--827552:1:main Welcome to Valgrind version 3.4.1 debug logging
--827552:1:main aix5: registering syscalls ..
--831682:1:launcher parent: child exited on signal 11
Any ideas?
Thanks in advance
------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
