|
From: Javier C. <jca...@sb...> - 2005-10-14 12:21:56
|
Here it is. Thanks root@10.70.0.222:/valgrind# valgrind --tool=none -d -d -v -v /bin/ls -l --12266:1:debuglog DebugLog system started by Stage 1, level 2 logging requested --12266:1:launcher tool 'none' requested --12266:1:launcher launching /usr/local/lib/valgrind/none --12266:1:debuglog DebugLog system started by Stage 2 (main), level 2 logging re quested --12266:1:main Welcome to Valgrind version 3.1.SVN debug logging --12266:1:main Checking current stack is plausible --12266:1:main Checking initial stack was noted --12266:1:main Starting the address space manager --12266:2:aspacem sp_at_startup = 0x007FFFFD40 (supplied) --12266:2:aspacem minAddr = 0x0004000000 (computed) --12266:2:aspacem maxAddr = 0x007FFFEFFF (computed) --12266:2:aspacem cStart = 0x0004000000 (computed) --12266:2:aspacem vStart = 0x0042000000 (computed) --12266:2:aspacem suggested_clstack_top = 0x007EFFFFFF (computed) --12266:2:aspacem <<< SHOW_SEGMENTS: Initial layout (5 segments, 0 segnames) --12266:2:aspacem 0: RSVN 0000000000-0003FFFFFF 64m ----- SmFixed --12266:2:aspacem 1: 0004000000-0041FFFFFF 992m --12266:2:aspacem 2: RSVN 0042000000-0042000FFF 4096 ----- SmFixed --12266:2:aspacem 3: 0042001000-007FFFEFFF 991m --12266:2:aspacem 4: RSVN 007FFFF000-00FFFFFFFF 2048m ----- SmFixed --12266:2:aspacem >>> --12266:2:aspacem Reading /proc/self/maps --12266:2:aspacem <<< SHOW_SEGMENTS: With contents of /proc/self/maps (11 seg ments, 1 segnames) --12266:2:aspacem ( 0) /usr/local/lib/valgrind/none --12266:2:aspacem 0: RSVN 0000000000-0003FFFFFF 64m ----- SmFixed --12266:2:aspacem 1: 0004000000-0041FFFFFF 992m --12266:2:aspacem 2: RSVN 0042000000-0042000FFF 4096 ----- SmFixed --12266:2:aspacem 3: 0042001000-006FFFFFFF 735m --12266:2:aspacem 4: FILE 0070000000-0070138FFF 1282048 r-x-- d=0x00A i=125 02998 o=0 (0) --12266:2:aspacem 5: 0070139000-0070148FFF 65536 --12266:2:aspacem 6: FILE 0070149000-0070149FFF 4096 rwx-- d=0x00A i=125 02998 o=1282048 (0) --12266:2:aspacem 7: ANON 007014A000-007079AFFF 6623232 rwx-- --12266:2:aspacem 8: 007079B000-007FFEAFFF 248m --12266:2:aspacem 9: ANON 007FFEB000-007FFFFFFF 86016 rw--- --12266:2:aspacem 10: RSVN 0080000000-00FFFFFFFF 2048m ----- SmFixed --12266:2:aspacem >>> --12266:1:main Address space manager is running --12266:1:main Starting the dynamic memory manager --12266:1:mallocfr newSuperblock at 0x42001000 (pszB 1048560) owner VALGRIND/too l --12266:1:main Dynamic memory manager is running --12266:1:main Getting stage1's name --12266:1:main Split up command line --12266:1:main Preprocess command line opts --12266:1:main Loading client --12266:1:main Setup client env --12266:2:main preload_string: --12266:2:main "/usr/local/lib/valgrind/vgpreload_core.so" --12266:1:main Setup client stack --12266:2:main PPC32 cache line size 32 (type 19) --12266:2:main PPC32 cache line size 32 (type 20) --12266:2:main PPC32 hwcaps: 0x84000000 --12266:2:main PPC32 AltiVec support: 0 --12266:2:main Client info: initial_IP=0x4010984 initial_SP=0x7EFFFD80 brk _base=0x1002A000 --12266:1:main Setup client data (brk) segment --12266:1:main Setup file descriptors --12266:1:main Create fake /proc/<pid>/cmdline --12266:1:main Initialise the tool part 1 (pre_clo_init) --12266:1:main Print help and quit, if requested --12266:1:main Process Valgrind's command line options, setup logging --12266:1:main Print the preamble... ==12266== Nulgrind, a binary JIT-compiler. ==12266== Copyright (C) 2002-2005, and GNU GPL'd, by Nicholas Nethercote. ==12266== Segmentation fault root@10.70.0.222:/valgrind# -----Original Message----- From: val...@li... [mailto:val...@li...] On Behalf Of Julian Seward Sent: Wednesday, October 12, 2005 8:18 PM To: val...@li... Subject: Re: [Valgrind-users] Valgrind 3.0 repository on ppc32 > The code repository page mentions the 3.0 line is not ready for ppc32 > yet but the posting dated June 2005. It's been three months since then, > so what is the status of the ppc support? Improving and under active development. The main shortcoming is that Altivec is not really usable yet. There are also performance issues. Both of these are being worked on. Apart from that all the tools work (cachegrind, massif, memcheck) and work well enough to be usable. It gets worked on regularly on a G5 and on a Mac Mini, both running YDL4, and it also works on an old iMac running SuSE 10.0. > I am trying on an amcc 440gp machine running a 2.6.10 kernel but getting > a segmentation fault as shown below: Hmm. Can you send the result of valgrind --tool=none -d -d -v -v /bin/ls -l J ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Valgrind-users mailing list Val...@li... https://lists.sourceforge.net/lists/listinfo/valgrind-users |