> They indicate that valgrind's memory manager was asked to
> handle a block (actually a single contiguous address
> interval, which could be a block or a non-block) of more
> than 100,000,000 bytes ... on x86_64 with 64-bit addresses
> and much more latitude for placement of PT_LOAD, this
> might be OK. Where are your PT_LOAD?
I don't know what PT_LOAD means. Output of readelf --segments
for the executable is:
Elf file type is EXEC (Executable file)
Entry point 0x431280
There are 9 program headers, starting at offset 64
Program Headers:
Type Offset VirtAddr PhysAddr
FileSiz MemSiz Flags Align
PHDR 0x0000000000000040 0x0000000000400040
0x0000000000400040
0x00000000000001f8 0x00000000000001f8 R E 8
INTERP 0x0000000000000238 0x0000000000400238
0x0000000000400238
0x000000000000001c 0x000000000000001c R 1
[Requesting program interpreter: /lib64/ld-linux-x86-64.so.2]
LOAD 0x0000000000000000 0x0000000000400000
0x0000000000400000
0x000000000031c544 0x000000000031c544 R E 100000
LOAD 0x000000000031d000 0x000000000081d000
0x000000000081d000
0x0000000000012fe8 0x000000000005ac20 RW 100000
DYNAMIC 0x000000000031d028 0x000000000081d028
0x000000000081d028
0x0000000000000230 0x0000000000000230 RW 8
NOTE 0x0000000000000254 0x0000000000400254
0x0000000000400254
0x0000000000000020 0x0000000000000020 R 4
NOTE 0x0000000000000274 0x0000000000400274
0x0000000000400274
0x0000000000000018 0x0000000000000018 R 4
GNU_EH_FRAME 0x00000000002e8098 0x00000000006e8098
0x00000000006e8098
0x0000000000009efc 0x0000000000009efc R 4
GNU_STACK 0x0000000000000000 0x0000000000000000
0x0000000000000000
0x0000000000000000 0x0000000000000000 RWE 8
Section to Segment mapping:
Segment Sections...
00
01 .interp
02 .interp .note.ABI-tag .note.SuSE .hash .dynsym .dynstr
.gnu.version .g
nu.version_r .rela.dyn .rela.plt .init .plt .text .fini .rodata
.eh_frame_hdr .e
h_frame
03 .ctors .dtors .jcr .dynamic .got .got.plt .data .bss
04 .dynamic
05 .note.ABI-tag
06 .note.SuSE
07 .eh_frame_hdr
08
and the same for the shared library that is probably the cause -
because I've never seen this from any of our other shared libraries,
in running all our tests through them - goes:
Elf file type is DYN (Shared object file)
Entry point 0x10fe60
There are 5 program headers, starting at offset 64
Program Headers:
Type Offset VirtAddr PhysAddr
FileSiz MemSiz Flags Align
LOAD 0x0000000000000000 0x0000000000000000
0x0000000000000000
0x00000000003d0d2d 0x00000000003d0d2d R E 100000
LOAD 0x00000000003d1000 0x00000000004d1000
0x00000000004d1000
0x0000000000004d2c 0x0000000000005b30 RW 100000
DYNAMIC 0x00000000003d4308 0x00000000004d4308
0x00000000004d4308
0x0000000000000210 0x0000000000000210 RW 8
GNU_EH_FRAME 0x0000000000352ba4 0x0000000000352ba4
0x0000000000352ba4
0x000000000001313c 0x000000000001313c R 4
GNU_STACK 0x0000000000000000 0x0000000000000000
0x0000000000000000
0x0000000000000000 0x0000000000000000 RW 8
Section to Segment mapping:
Segment Sections...
00 .hash .dynsym .dynstr .gnu.version .gnu.version_r .rela.dyn
.rela.plt
.init .plt .text .fini .rodata .eh_frame_hdr .eh_frame .gcc_except_table
01 .ctors .dtors .jcr .data.rel.ro .dynamic .got .got.plt .data
.bss
02 .dynamic
03 .eh_frame_hdr
04
--
John Dallman
Parasolid Porting Engineer
Siemens PLM Software
46 Regent Street, Cambridge, CB2 1DP
United Kingdom
Tel: +44-1223-371554
[email protected]
www.siemens.com/plm
> -----Original Message-----
> From: John Reiser [mailto:[email protected]]
> Sent: Wednesday, March 04, 2009 1:44 PM
> To: Valgrind Users
> Subject: Re: [Valgrind-users] Puzzling warning messages from memcheck
>
> > I'm running Valgrind-3.3.1 on x86-64 on SLES10sp1
>
> > ==4213== Warning: set address range perms: large range 102130360
> (undefined)
> > ==4213== Warning: set address range perms: large range 102130392
> (noaccess)
>
> These messages are internal to valgrind, but they have some utility
for
> users.
> They indicate that valgrind's memory manager was asked to handle a
> block (actually
> a single contiguous address interval, which could be a block or a non-
> block)
> of more than 100,000,000 bytes. Such a large interval is unusual and
> might
> indicate an error, especially on a system with 32-bit addresses. But
> on
> x86_64 with 64-bit addresses and much more latitude for placemement of
> PT_LOAD,
> this might be OK. Where are your PT_LOAD? [readelf --segments
> <executable>]
>
> When I was working in this area of valgrind, then I improved the
> message
> to include the actual address values as well as the length. Often
this
> made it easy to determine whether to be concerned.
>
> --
>
>
-----------------------------------------------------------------------
> -------
> Open Source Business Conference (OSBC), March 24-25, 2009, San
> Francisco, CA
> -OSBC tackles the biggest issue in open source: Open Sourcing the
> Enterprise
> -Strategies to boost innovation and cut costs with open source
> participation
> -Receive a $600 discount off the registration fee with the source
code:
> SFAD
> http://p.sf.net/sfu/XcvMzF8H
> _______________________________________________
> Valgrind-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/valgrind-users
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
