Hi Julian
Thanks for the reply (and indeed all of your work on Valgrind!). The output
from readelf is below, as you'll see there is a .eh_frame section. Is there any
dependency on how the Valgrind applications and libraries are compiled? This
was done as part of a Yocto Project build so I would need to double-check
exactly which compile options were used.
Thanks again
Simon
# readelf -S /usr/lib/valgrind/vgpreload_memcheck-arm-linux.so
There are 23 section headers, starting at offset 0xd064:
Section Headers:
[Nr] Name Type Addr Off Size ES Flg Lk Inf Al
[ 0] NULL 00000000 000000 000000 00 0 0 0
[ 1] .note.gnu.build-i NOTE 000000d4 0000d4 000024 00 A 0 0 4
[ 2] .gnu.hash GNU_HASH 000000f8 0000f8 0008f4 04 A 3 0 4
[ 3] .dynsym DYNSYM 000009ec 0009ec 000c70 10 A 4 3 4
[ 4] .dynstr STRTAB 0000165c 00165c 0019fb 00 A 0 0 1
[ 5] .rel.dyn REL 00003058 003058 000048 08 A 3 0 4
[ 6] .rel.plt REL 000030a0 0030a0 000048 08 AI 3 17 4
[ 7] .init PROGBITS 000030e8 0030e8 00000c 00 AX 0 0 4
[ 8] .plt PROGBITS 000030f4 0030f4 000080 04 AX 0 0 4
[ 9] .text PROGBITS 00003174 003174 0098a0 00 AX 0 0 4
[10] .fini PROGBITS 0000ca14 00ca14 000008 00 AX 0 0 4
[11] .rodata PROGBITS 0000ca1c 00ca1c 000400 01 AMS 0 0 4
[12] .eh_frame PROGBITS 0000ce1c 00ce1c 000004 00 A 0 0 4
[13] .init_array INIT_ARRAY 0001ce20 00ce20 000008 00 WA 0 0 4
[14] .fini_array FINI_ARRAY 0001ce28 00ce28 000004 00 WA 0 0 4
[15] .jcr PROGBITS 0001ce2c 00ce2c 000004 00 WA 0 0 4
[16] .dynamic DYNAMIC 0001ce30 00ce30 0000c8 08 WA 4 0 4
[17] .got PROGBITS 0001cef8 00cef8 000044 04 WA 0 0 4
[18] .data PROGBITS 0001cf3c 00cf3c 000004 00 WA 0 0 4
[19] .bss NOBITS 0001cf40 00cf40 000090 00 WA 0 0 4
[20] .ARM.attributes ARM_ATTRIBUTES 00000000 00cf40 00003d 00 0 0 1
[21] .gnu_debuglink PROGBITS 00000000 00cf7d 000024 00 0 0 1
[22] .shstrtab STRTAB 00000000 00cfa1 0000c3 00 0 0 1
Key to Flags:
W (write), A (alloc), X (execute), M (merge), S (strings)
I (info), L (link order), G (group), T (TLS), E (exclude), x (unknown)
O (extra OS processing required) o (OS specific), p (processor specific)
-----Julian Seward <jsew...@acm.org> wrote: -----
To: simon.g...@doulos.com, valgrind-users@lists.sourceforge.net
From: Julian Seward <jsew...@acm.org>
Date: 07/21/2016 03:22PM
Subject: Re: [Valgrind-users] Difference in Behaviour between 3.10 and 3.11
This is most likely a problem caused by missing unwind info on the 3.11
vgpreload_memcheck-arm-linux.so. What does
readelf -S vgpreload_memcheck-arm-linux.so
say about them? In particular, do they both have .eh_frame, .extab and
.exidx sections? Basically you need either .eh_frame or (.extab and .exidx)
in order to unwind on arm32.
J
> ==1027== 28 (12 direct, 16 indirect) bytes in 1 blocks are definitely lost in
> loss record 2 of 7
> ==1027== at 0x4847FE4: realloc (in
> /usr/lib/valgrind/vgpreload_memcheck-arm-linux.so)
> ==1027==
> ==1027== 352 (304 direct, 48 indirect) bytes in 14 blocks are definitely lost
> in loss record 4 of 7
> ==1027== at 0x48457E4: malloc (in
> /usr/lib/valgrind/vgpreload_memcheck-arm-linux.so)
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
