|
From: Julian S. <js...@ac...> - 2010-09-08 17:15:47
|
The ARM port can run multi-million-line C++ applications without problems, so it must be some initial statup/configuration problem. Please file a bug report about this using the form at https://bugs.kde.org/enter_valgrind_bug.cgi It is much better to have bug reports in the bug tracker than on the mailing list. Include, in the bug report, all the info in your email below. J On Wednesday, September 08, 2010, Alexander Stohr wrote: > i knew its still experimental but it seemed the only option for me... > i gave valgrinds experimental arm support a go. > i used svn sources from this afternoon. > i used a natively compiled version on this platform: > > Processor : ARMv7 Processor rev 3 (v7l) > BogoMIPS : ***** > Features : swp half thumb fastmult vfp edsp > CPU implementer : 0x41 > CPU architecture: 7 > CPU variant : 0x1 > CPU part : 0xc08 > CPU revision : 3 > L1 I cache :VIPT > > it is supposed to be some TI OMAP3 chip, meaning the Cortex-A8 core design. > > the used compiler has this version information; > > gcc (GCC) 4.3.1 > Copyright (C) 2008 Free Software Foundation, Inc. > > when running it the normal way it simply segfaults. > when running it in gdb it reports the lines appended below. > (for other reasons i am just updating to latest stable gdb.) > > as i really want to use your tooling i would be keen on providing you > more information. please instruct me what i should do in this case > to improve the situation for the test reports i can provide to you. > > regards, Alex. > > PS: i have a long term programming experience - its just a blockage > that i am seeing right now because the segfault is in-between nowhere. > > > user@machine# gdb valgrind > GNU gdb 6.8 > Copyright (C) 2008 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later > <http://gnu.org/licenses/gpl.html> This is free software: you are free to > change and redistribute it. There is NO WARRANTY, to the extent permitted > by law. Type "show copying" and "show warranty" for details. > This GDB was configured as "arm-angstrom-linux-gnueabi"... > (gdb) run ls -l > Starting program: /usr/local/bin/valgrind ls -l > Executing new program: /usr/local/lib/valgrind/memcheck-arm-linux > ==6437== Memcheck, a memory error detector > ==6437== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al. > ==6437== Using Valgrind-3.6.0.SVN and LibVEX; rerun with -h for copyright > info ==6437== Command: ls -l > ==6437== > > Program received signal SIGSEGV, Segmentation fault. > 0x625ce9f4 in ?? () > (gdb) bt > #0 0x625ce9f4 in ?? () > Cannot access memory at address 0x0 > (gdb) |