[valgrind] [Bug 470244] mremap() call not fully implemented and when attempting to resize the same address to a larger size the mremap() call responded with MAP_FAILED.

https://bugs.kde.org/show_bug.cgi?id=470244 Tom Hughes changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|

[valgrind] [Bug 470244] mremap() call not fully implemented and when attempting to resize the same address to a larger size the mremap() call responded with MAP_FAILED.

https://bugs.kde.org/show_bug.cgi?id=470244 Simon changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|R

[valgrind] [Bug 470244] mremap() call not fully implemented and when attempting to resize the same address to a larger size the mremap() call responded with MAP_FAILED.

https://bugs.kde.org/show_bug.cgi?id=470244 --- Comment #9 from Tom Hughes --- Actually I can see the problem there - the following segment is an SkResvn not SkFree. Now VG_(am_get_advisory_client_simple) will allow a reservation to be used so will accept the request, but VG_(am_covered_by_singl

[valgrind] [Bug 470244] mremap() call not fully implemented and when attempting to resize the same address to a larger size the mremap() call responded with MAP_FAILED.

https://bugs.kde.org/show_bug.cgi?id=470244 --- Comment #8 from Simon --- It is a strange one.. The segment dump I attached shows nothing in the memory ahead.. But code walking through the do_mremap() function its not obvious to me why its returning MAP_FAILED. Something Subtle no doubt.. :-

[valgrind] [Bug 470244] mremap() call not fully implemented and when attempting to resize the same address to a larger size the mremap() call responded with MAP_FAILED.

https://bugs.kde.org/show_bug.cgi?id=470244 --- Comment #7 from Simon --- I'd already tried outputting those segments before but I'm not sure why they failed.. My guess was that valgrind had used some of the space itself and was blocking the expansion of the existing memory segment. -- You are

[valgrind] [Bug 470244] mremap() call not fully implemented and when attempting to resize the same address to a larger size the mremap() call responded with MAP_FAILED.

https://bugs.kde.org/show_bug.cgi?id=470244 --- Comment #6 from Simon --- Created attachment 159243 --> https://bugs.kde.org/attachment.cgi?id=159243&action=edit Additional output from debug enabled valgrind mremap() overload The additional output from the valgrind overload of mremap(). --

[valgrind] [Bug 470244] mremap() call not fully implemented and when attempting to resize the same address to a larger size the mremap() call responded with MAP_FAILED.

https://bugs.kde.org/show_bug.cgi?id=470244 --- Comment #5 from Tom Hughes --- This is the call: SYSCALL[157805,1](25) sys_mremap ( 0xac, 8192, 16384, 0x0 ) --> [pre-fail] Failure(0xc) so it's being rejected by valgrind with ENOMEM without being passed to the kernel. Given the flags we

[valgrind] [Bug 470244] mremap() call not fully implemented and when attempting to resize the same address to a larger size the mremap() call responded with MAP_FAILED.

https://bugs.kde.org/show_bug.cgi?id=470244 --- Comment #4 from Simon --- Created attachment 159241 --> https://bugs.kde.org/attachment.cgi?id=159241&action=edit strace of the example programs running without issues -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 470244] mremap() call not fully implemented and when attempting to resize the same address to a larger size the mremap() call responded with MAP_FAILED.

https://bugs.kde.org/show_bug.cgi?id=470244 --- Comment #3 from Simon --- Created attachment 159240 --> https://bugs.kde.org/attachment.cgi?id=159240&action=edit --trace-syscalls trace output of valgrind valgrind -v --trace-syscalls=yes --tool=memcheck ./a.out ==157805== Memcheck, a memory err

[valgrind] [Bug 470244] mremap() call not fully implemented and when attempting to resize the same address to a larger size the mremap() call responded with MAP_FAILED.

https://bugs.kde.org/show_bug.cgi?id=470244 --- Comment #2 from Simon --- Its a bug because its not fully implementing the mmap() functionality.. However yes we are using mmap/mremap so that we don't change the base address of the mmap(). That appears to be in conflict with valgrind which is

[valgrind] [Bug 470244] mremap() call not fully implemented and when attempting to resize the same address to a larger size the mremap() call responded with MAP_FAILED.

https://bugs.kde.org/show_bug.cgi?id=470244 Tom Hughes changed: What|Removed |Added CC||t...@compton.nu --- Comment #1 from Tom Hughes --

[valgrind] [Bug 470244] mremap() call not fully implemented and when attempting to resize the same address to a larger size the mremap() call responded with MAP_FAILED.

https://bugs.kde.org/show_bug.cgi?id=470244 Simon changed: What|Removed |Added CC||victor.unitie...@icloud.com -- You are receiving this

[valgrind] [Bug 470244] mremap() call not fully implemented and when attempting to resize the same address to a larger size the mremap() call responded with MAP_FAILED.

https://bugs.kde.org/show_bug.cgi?id=470244 Simon changed: What|Removed |Added Summary|mremap() call not fully |mremap() call not fully |implemented