|
From: t. <358...@qq...> - 2014-10-22 12:03:44
|
4. Does valgrind support cpu-arm9 ? ( tupeng ) hello, everybody, I've got the trueth, post it : how to run valgrind at android with ARMv6 http://bbs.chinaunix.net/thread-3606946-1-1.html Thanks you all !~ ------------------ Original ------------------ From: "valgrind-developers-request"<val...@li...>; Date: 2014年10月22日(星期三) 凌晨1:24 To: "valgrind-developers"<val...@li...>; Subject: Valgrind-developers Digest, Vol 101, Issue 107 Send Valgrind-developers mailing list submissions to val...@li... To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/valgrind-developers or, via email, send a message with subject or body 'help' to val...@li... You can reach the person managing the list at val...@li... When replying, please edit your Subject line so it is more specific than "Re: Contents of Valgrind-developers digest..." Today's Topics: 1. Valgrind: r14646 - in /trunk: ./ coregrind/m_syswrap/ include/vki/ memcheck/tests/linux/ (sv...@va...) 2. Re: DRD test failures. (Bart Van Assche) 3. Valgrind: r14647 - in /trunk: helgrind/hg_intercepts.c shared/vg_replace_strmem.c (sv...@va...) 4. Does valgrind support cpu-arm9 ? ( tupeng ) ---------------------------------------------------------------------- Message: 1 Date: Tue, 21 Oct 2014 07:20:20 -0000 From: sv...@va... Subject: [Valgrind-developers] Valgrind: r14646 - in /trunk: ./ coregrind/m_syswrap/ include/vki/ memcheck/tests/linux/ To: val...@li... Message-ID: <201...@sq...> Content-Type: text/plain; charset="utf-8" Author: florian Date: Tue Oct 21 08:20:20 2014 New Revision: 14646 Log: Add support for ioctl(fd, TIOCSIG, signal_number) which used to issue a false complaint. Fixes BZ #339706 Source patch by David Herrmann (dh....@gm...). Testcase by myself. Added: trunk/memcheck/tests/linux/ioctl-tiocsig.c trunk/memcheck/tests/linux/ioctl-tiocsig.stderr.exp trunk/memcheck/tests/linux/ioctl-tiocsig.vgtest Modified: trunk/NEWS trunk/coregrind/m_syswrap/syswrap-linux.c trunk/include/vki/vki-linux.h trunk/memcheck/tests/linux/ (props changed) trunk/memcheck/tests/linux/Makefile.am Modified: trunk/NEWS ============================================================================== --- trunk/NEWS (original) +++ trunk/NEWS Tue Oct 21 08:20:20 2014 @@ -42,6 +42,7 @@ 339688 Mac-specific ASM does not support .version directive (cpuid, tronical and pushfpopf tests) +339706 Fix false positive for ioctl(TIOCSIG) on linux 339721 assertion 'check_sibling == sibling' failed in readdwarf3.c ... 339789 Fix none/tests/execve test on Mac OS X 10.9 339808 Fix none/tests/rlimit64_nofile test on Mac OS X 10.9 Modified: trunk/coregrind/m_syswrap/syswrap-linux.c ============================================================================== --- trunk/coregrind/m_syswrap/syswrap-linux.c (original) +++ trunk/coregrind/m_syswrap/syswrap-linux.c Tue Oct 21 08:20:20 2014 @@ -5481,6 +5481,7 @@ case VKI_TCXONC: case VKI_TCSBRKP: case VKI_TCFLSH: + case VKI_TIOCSIG: /* These just take an int by value */ break; case VKI_TIOCGWINSZ: @@ -8270,6 +8271,7 @@ case VKI_TCXONC: case VKI_TCSBRKP: case VKI_TCFLSH: + case VKI_TIOCSIG: break; case VKI_TIOCGWINSZ: POST_MEM_WRITE( ARG3, sizeof(struct vki_winsize) ); Modified: trunk/include/vki/vki-linux.h ============================================================================== --- trunk/include/vki/vki-linux.h (original) +++ trunk/include/vki/vki-linux.h Tue Oct 21 08:20:20 2014 @@ -2955,6 +2955,10 @@ #define VKI_FIOQSIZE 0x5460 /* Value differs on some platforms */ #endif +#ifndef VKI_TIOCSIG +#define VKI_TIOCSIG _VKI_IOW('T', 0x36, int) /* Value differs on some platforms */ +#endif + //---------------------------------------------------------------------- // From kernel/common/include/linux/ashmem.h //---------------------------------------------------------------------- Modified: trunk/memcheck/tests/linux/Makefile.am ============================================================================== --- trunk/memcheck/tests/linux/Makefile.am (original) +++ trunk/memcheck/tests/linux/Makefile.am Tue Oct 21 08:20:20 2014 @@ -6,6 +6,7 @@ EXTRA_DIST = \ brk.stderr.exp brk.vgtest \ capget.vgtest capget.stderr.exp capget.stderr.exp2 \ + ioctl-tiocsig.vgtest ioctl-tiocsig.stderr.exp \ lsframe1.vgtest lsframe1.stdout.exp lsframe1.stderr.exp \ lsframe2.vgtest lsframe2.stdout.exp lsframe2.stderr.exp \ rfcomm.vgtest rfcomm.stderr.exp \ @@ -24,6 +25,7 @@ check_PROGRAMS = \ brk \ capget \ + ioctl-tiocsig \ getregset \ lsframe1 \ lsframe2 \ Added: trunk/memcheck/tests/linux/ioctl-tiocsig.c ============================================================================== --- trunk/memcheck/tests/linux/ioctl-tiocsig.c (added) +++ trunk/memcheck/tests/linux/ioctl-tiocsig.c Tue Oct 21 08:20:20 2014 @@ -0,0 +1,7 @@ +#include <sys/ioctl.h> + +int main() +{ + ioctl(9, TIOCSIG, 9); + return 0; +} Added: trunk/memcheck/tests/linux/ioctl-tiocsig.stderr.exp ============================================================================== (empty) Added: trunk/memcheck/tests/linux/ioctl-tiocsig.vgtest ============================================================================== --- trunk/memcheck/tests/linux/ioctl-tiocsig.vgtest (added) +++ trunk/memcheck/tests/linux/ioctl-tiocsig.vgtest Tue Oct 21 08:20:20 2014 @@ -0,0 +1,2 @@ +prog: ioctl-tiocsig +vgopts: -q ------------------------------ Message: 2 Date: Tue, 21 Oct 2014 15:53:48 +0200 From: Bart Van Assche <bva...@ac...> Subject: Re: [Valgrind-developers] DRD test failures. To: Anmol Paralkar <An...@fr...>, "val...@li..." <val...@li...> Message-ID: <544...@ac...> Content-Type: text/plain; charset=windows-1252; format=flowed On 10/21/14 01:36, Anmol Paralkar wrote: > I see failures in my armv7 valgrind-3.10.0 run that I am guessing have > to do with missing glibc debug packages and/or having a stripped glibc. > > Just thought I?d run this past you folks just in case someone?s seen > this before: > > root@ls1021aqds:/home/anmol/valgrind-trunk-ls1021aqds# uname -a > > Linux ls1021aqds 3.12.0+ #1 SMP Thu Oct 16 17:22:18 CDT 2014 armv7l > GNU/Linux > > root@ls1021aqds:/home/anmol/valgrind-trunk-ls1021aqds# cat > drd/tests/annotate_barrier.stderr.diff > > --- annotate_barrier.stderr.exp 2014-10-17 16:11:30.557529158 +0000 > > +++ annotate_barrier.stderr.out 2014-10-20 22:25:27.965963442 +0000 > > @@ -24,8 +24,6 @@ > > Thread 2: > > Conflicting store by thread 2 at 0x........ size 4 > > at 0x........: threadfunc (annotate_barrier.c:?) > > - by 0x........: vgDrd_thread_wrapper (drd_pthread_intercepts.c:?) > > - by 0x........: (within libpthread-?.?.so) > > Address 0x........ is at offset 0 from 0x......... Allocation context: > > at 0x........: malloc (vg_replace_malloc.c:...) > > bys1021aqds:/home/anmol/valgrind-trunk-ls1021aqds# .c:?) > > root@ls1021aqds:/home/anmol/valgrind-trunk-ls1021aqds# file > /lib/libc-2.18-2013.10.so > > /lib/libc-2.18-2013.10.so: ELF 32-bit LSB shared object, ARM, EABI5 > version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux > 2.6.16, stripped > > root@ls1021aqds:/home/anmol/valgrind-trunk-ls1021aqds# > > If it is not the above, I?d next try to debug drd/drd_error.c around > line 201: > > print_err_detail("%sConflicting %s by thread %d at 0x%08lx size > %ld%s\n", > > what_prefix, dri->access_type == eStore ? "store" : > "load", > > dri->tid, dri->addr, dri->size, what_suffix); > > VG_(pp_ExeContext)(VG_(get_error_where)(err)); // Fails? > > Am I on the right track? Hello Ammol, As you can see in the nightly build output produced on various servers DRD in general and this test case in particular run reliably on x86 and PPC systems. I'm not sure what makes it fail on ARM. But I think that the Valgrind stack backtrace code might be a better place to start than the DRD source code. Bart. ------------------------------ Message: 3 Date: Tue, 21 Oct 2014 17:15:15 -0000 From: sv...@va... Subject: [Valgrind-developers] Valgrind: r14647 - in /trunk: helgrind/hg_intercepts.c shared/vg_replace_strmem.c To: val...@li... Message-ID: <201...@sq...> Content-Type: text/plain; charset="utf-8" Author: florian Date: Tue Oct 21 18:15:14 2014 New Revision: 14647 Log: Rewritten to avoid cast that drops const qualification. Modified: trunk/helgrind/hg_intercepts.c trunk/shared/vg_replace_strmem.c Modified: trunk/helgrind/hg_intercepts.c ============================================================================== --- trunk/helgrind/hg_intercepts.c (original) +++ trunk/helgrind/hg_intercepts.c Tue Oct 21 18:15:14 2014 @@ -136,7 +136,7 @@ #define DO_PthAPIerror(_fnnameF, _errF) \ do { \ - char* _fnname = (char*)(_fnnameF); \ + const char* _fnname = (_fnnameF); \ long _err = (long)(int)(_errF); \ const char* _errstr = lame_strerror(_err); \ DO_CREQ_v_WWW(_VG_USERREQ__HG_PTH_API_ERROR, \ Modified: trunk/shared/vg_replace_strmem.c ============================================================================== --- trunk/shared/vg_replace_strmem.c (original) +++ trunk/shared/vg_replace_strmem.c Tue Oct 21 18:15:14 2014 @@ -1327,8 +1327,6 @@ void* VG_REPLACE_FUNCTION_EZU(20290,soname,fnname) \ ( void *dst, const void *src, SizeT len ) \ { \ - register HChar *d; \ - register HChar *s; \ SizeT len_saved = len; \ \ if (len == 0) \ @@ -1338,14 +1336,14 @@ RECORD_OVERLAP_ERROR("mempcpy", dst, src, len); \ \ if ( dst > src ) { \ - d = (char *)dst + len - 1; \ - s = (char *)src + len - 1; \ + register HChar *d = (char *)dst + len - 1; \ + register const HChar *s = (const char *)src + len - 1; \ while ( len-- ) { \ *d-- = *s--; \ } \ } else if ( dst < src ) { \ - d = (char *)dst; \ - s = (char *)src; \ + register HChar *d = dst; \ + register const HChar *s = src; \ while ( len-- ) { \ *d++ = *s++; \ } \ ------------------------------ Message: 4 Date: Wed, 22 Oct 2014 01:23:41 +0800 From: " tupeng " <358...@qq...> Subject: [Valgrind-developers] Does valgrind support cpu-arm9 ? To: " valgrind-developers " <val...@li...> Message-ID: <ten...@qq...> Content-Type: text/plain; charset="utf-8" As I complied valgrind, then run it on my arm board, found this: # ./valgrind Illegal instruction # ? Because my arm cpu is not armv7, but the params for arm-linux-gcc contented : #AM_CFLAGS_ARM_LINUX = $(AM_CFLAGS_BASE) -marm -mcpu=cortex-a8 #AM_CFLAGS_PSO_ARM_LINUX = $(AM_CFLAGS_BASE) -marm -mcpu=cortex-a8 $(AM_CFLAGS_PSO_BASE) #AM_CCASFLAGS_ARM_LINUX = -marm -mcpu=cortex-a8 -g? I commented those above, then complied the source code again but found these: m_dispatch/dispatch-arm-linux.S: Assembler messages: m_dispatch/dispatch-arm-linux.S:103: Error: selected processor does not support ARM mode `movw r1,#47' m_dispatch/dispatch-arm-linux.S:104: Error: selected processor does not support ARM mode `movw r2,#0' m_dispatch/dispatch-arm-linux.S:156: Error: selected processor does not support ARM mode `movw r1,#:lower16:vgPlain_stats__n_xindirs_32' m_dispatch/dispatch-arm-linux.S:157: Error: selected processor does not support ARM mode `movt r1,#:upper16:vgPlain_stats__n_xindirs_32' m_dispatch/dispatch-arm-linux.S:164: Error: selected processor does not support ARM mode `movw r1,#(((1<<15))-1)' m_dispatch/dispatch-arm-linux.S:165: Error: selected processor does not support ARM mode `movw r4,#:lower16:vgPlain_tt_fast' m_dispatch/dispatch-arm-linux.S:168: Error: selected processor does not support ARM mode `movt r4,#:upper16:vgPlain_tt_fast' m_dispatch/dispatch-arm-linux.S:172: Error: selected processor does not support ARM mode `ldrd r4,r5,[r1,#0]' m_dispatch/dispatch-arm-linux.S:181: Error: selected processor does not support ARM mode `movw r1,#:lower16:vgPlain_stats__n_xindir_misses_32' m_dispatch/dispatch-arm-linux.S:182: Error: selected processor does not support ARM mode `movt r1,#:upper16:vgPlain_stats__n_xindir_misses_32' make[3]: *** [m_dispatch/libcoregrind_arm_linux_a-dispatch-arm-linux.o] Error 1 ? I am not familiar with ArmV7's disassembly code, could you help to modify the instruction movw, movt to mov ? or some which can run on ArmV9. Thank you very very much. ? -------------- next part -------------- An HTML attachment was scrubbed... ------------------------------ ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho ------------------------------ _______________________________________________ Valgrind-developers mailing list Val...@li... https://lists.sourceforge.net/lists/listinfo/valgrind-developers End of Valgrind-developers Digest, Vol 101, Issue 107 ***************************************************** |
|
From: Tom H. <to...@co...> - 2014-10-22 13:01:16
|
On 22/10/14 13:03, tupeng wrote: > 4. Does valgrind support cpu-arm9 ? ( tupeng ) > hello, everybody, I've got the trueth, post it : > > > how to run valgrind at android with ARMv6 > <http://bbs.chinaunix.net/thread-3606946-1-1.html> The supported platforms are listed on the web site: http://valgrind.org/info/platforms.html As you will see ARM support starts with ARMv7 so no, earlier architectures are not supported. Tom -- Tom Hughes (to...@co...) http://compton.nu/ |