On Tuesday 06 January 2009, Matthew Clark wrote: > I'm trying to build valgrind 3.4.x (both the official release and the > svn repository) on a PPC 7447A running a 2.6 kernel.
3.4.0 certainly does work on a 7447; I tested it myself on a PPC Mac Mini running openSuSE 10.3. Viewing from the log, it seems as if there's some permissions problem with the main executable. The faulting address (0x38162EA8) is within the mapped-in text segment of /usr/local/lib/valgrind/ppc32-linux/none --15861:1:aspacem ( 0) /usr/local/lib/valgrind/ppc32-linux/none --15861:1:aspacem 15: FILE 0038012000-00381a3fff 1646592 r-x-- d=0x00c i=4567528 o=73728 (0) but exactly what is going on isn't obvious to me. Can you re-run with --trace-signals=yes? In particular the line ==15861== Process terminating with default action of signal 11 (SIGSEGV) ==15861== Bad permissions for mapped region at address 0x38162EA8 might have some further details printed immediately before it, indicating why the thing faulted. J ------------------------------------------------------------------------------ Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
