diff options
author | V3n3RiX <venerix@redcorelinux.org> | 2020-06-13 10:39:22 +0100 |
---|---|---|
committer | V3n3RiX <venerix@redcorelinux.org> | 2020-06-13 10:39:22 +0100 |
commit | 9452a6e87b6c2c70513bc47a2470bf9f1168920e (patch) | |
tree | 8ac67e26b45f34d71c5aab3621813b100a0d5f00 /dev-util/valgrind | |
parent | f516638b7fe9592837389826a6152a7e1b251c54 (diff) |
gentoo resync : 13.06.2020
Diffstat (limited to 'dev-util/valgrind')
6 files changed, 0 insertions, 238 deletions
diff --git a/dev-util/valgrind/Manifest b/dev-util/valgrind/Manifest index 28a4d5326fd5..6689be387134 100644 --- a/dev-util/valgrind/Manifest +++ b/dev-util/valgrind/Manifest @@ -1,9 +1,4 @@ -AUX valgrind-3.13.0-accept-read-only-PT_LOAD-segments-and-rodata.patch 3765 BLAKE2B afce6e0e939040a76213733a4e3cb1ac0a26841fc9101d9fb8d74875861d8e5fb51f1813b2e377d15ea53a36166743c32550f00d1021bf4882fd8e2c4b43a127 SHA512 08c7db66502538f2dfa795b12dcbdfef6dc1f379da93af61f4a54fa48016be98a079c7ba4cc000d2972a2a1863ea01ce3d7c643ff993dfc3bc96d874b097473e -AUX valgrind-3.13.0-ignore-further-mappings-after-read-all-debuginfo.patch 3340 BLAKE2B 344519d755c875acfd70eb7fd475057eacb1321401bafeffb2f632e1edfb01e88db9fef2cf6541db0cae9a7d11cd2d2eb1f00429561a22f96621242c696c9112 SHA512 28bc64b5157738302aee97cbaf0b57ca6f17166de1e63167fe879560f493510b2db17478847519731004f72f87904e0647f593a53d88aa8638b1e1738310954d -AUX valgrind-3.13.0-test-fixes.patch 929 BLAKE2B cf0316cc3637785bfa57cd2277ad7669ab968b28424bdcf56c47219c90d00915f51293bfc90f5319785752bcebbde7b011dbac964f9538ac2f4208ec7709047f SHA512 1cff77e987e2d20ce1563c96d76431c60c142c42afa978e32d3a8c8dda17d0f3c1ba29fe3d0fcf0e7445fa5ca9558690ecdaad259fb9d23f435dcdc0baa9175d -AUX valgrind-3.13.0-xml-socket.patch 934 BLAKE2B 151db92f36623a27a6798eb0e559211613fb70e6847985446f4d3cd2a31f9930377e66efc46ae86116f8bcec855cfef2640111bce543ecd3a3e92914f0fa04cb SHA512 a250d6c395a6a02f3898ca94edab92785a720024ce0555c0b48cfe6c96c3bfcc088c5c67242019cb7d89f68066cffde18efe2c74f9b7f8e068b012173c3ec189 AUX valgrind-3.15.0-Build-ldst_multiple-test-with-fno-pie.patch 650 BLAKE2B ffb545d6af214a5bd43ff800d52e0d7cfc03feac8d2466da8d4935db659172cd50cf3e2d63b3aff46d81b21846b304671506cd235b710037218fc16e0ef66438 SHA512 7cb5a46c2d8ed4360053289994014b334e32d48b0608ed58662486bd432c31835ef16e2cdfd734f3e4d720e272d2507ec76f0b77e1364237e9f6dbbd97a8abb6 -AUX valgrind-3.7.0-fno-stack-protector.patch 554 BLAKE2B cd87e1bbf86b82face9dbbaddbbbb2773c6f1223e725898dfd5d0ae9078948642c4f2b9deca2bded676230bcfa20d39071f69e640a64dc254759115971374a82 SHA512 4f9573fd68a0e1e209518fb4100c27b697ccd28e7a39abaa921f1949cd87ffb79a6784d2d1f6e006d68a08c7217cee77cba378c18aab48b87a3824eedb53ed5e AUX valgrind-3.7.0-respect-flags.patch 360 BLAKE2B 020b9e3af2c6393193edd8be99ff2309f4b138915bd0315090cebd902747678a5b655a8178a8ec8e88782286470922aed505d2a69d6da4d295fd2053d640b035 SHA512 efdb017283b6a5829d1a5acc31b42ddd177a3ab468eb062b8c4fd90b2dbd06679e8d8bc2d6f813e3001efdda831d4410cc8da3a3e42ee2e49efea0423e4b3ca3 DIST valgrind-3.14.0.tar.bz2 16602858 BLAKE2B 00d601593388180cc874cf2f0c78e79f705f145e45ea82996117cb91ba881e7888ef241fb7e45927f82f99666d76ed35cb5d451e9a3ef123c04a0dff233b2269 SHA512 68e548c42df31dc2b883a403e0faff7480c49b3054841870f5d2f742141ba199eca5d83c96bbf283115f0633f2bdb0860161d422f98e3ec720ec65760d250f97 DIST valgrind-3.15.0.tar.bz2 20241437 BLAKE2B a1bd46d46b3cd9f963773d011e7c74bf5e09e59be13afe38229a3c66a89eeb416498faed67d6ec21489b630b55ac73cc212e17ba515884f8b6374849a60e3720 SHA512 5695d1355226fb63b0c80809ed43bb077b6eed4d427792d9d7ed944c38b557a84fe3c783517b921e32f161228e10e4625bea0550faa4685872bb4454450cfa7f diff --git a/dev-util/valgrind/files/valgrind-3.13.0-accept-read-only-PT_LOAD-segments-and-rodata.patch b/dev-util/valgrind/files/valgrind-3.13.0-accept-read-only-PT_LOAD-segments-and-rodata.patch deleted file mode 100644 index 41f73b43f351..000000000000 --- a/dev-util/valgrind/files/valgrind-3.13.0-accept-read-only-PT_LOAD-segments-and-rodata.patch +++ /dev/null @@ -1,95 +0,0 @@ -See https://bugs.gentoo.org/664882 - -From 64aa729bfae71561505a40c12755bd6b55bb3061 Mon Sep 17 00:00:00 2001 -From: Mark Wielaard <mark@klomp.org> -Date: Thu, 12 Jul 2018 13:56:00 +0200 -Subject: [PATCH] Accept read-only PT_LOAD segments and .rodata. - -The new binutils ld -z separate-code option creates multiple read-only -PT_LOAD segments and might place .rodata in a non-executable segment. - -Allow and keep track of separate read-only segments and allow a readonly -page with .rodata section. - -Based on patches from Tom Hughes <tom@compton.nu> and -H.J. Lu <hjl.tools@gmail.com>. - -https://bugs.kde.org/show_bug.cgi?id=395682 ---- - coregrind/m_debuginfo/debuginfo.c | 2 -- - coregrind/m_debuginfo/readelf.c | 34 +++++++++++++++++++++++-------- - 3 files changed, 27 insertions(+), 10 deletions(-) - ---- a/coregrind/m_debuginfo/debuginfo.c -+++ b/coregrind/m_debuginfo/debuginfo.c -@@ -957,9 +957,7 @@ - # error "Unknown platform" - # endif - --# if defined(VGP_x86_darwin) && DARWIN_VERS >= DARWIN_10_7 - is_ro_map = seg->hasR && !seg->hasW && !seg->hasX; --# endif - - # if defined(VGO_solaris) - is_rx_map = seg->hasR && seg->hasX && !seg->hasW; ---- a/coregrind/m_debuginfo/readelf.c -+++ b/coregrind/m_debuginfo/readelf.c -@@ -1785,7 +1785,7 @@ - Bool loaded = False; - for (j = 0; j < VG_(sizeXA)(di->fsm.maps); j++) { - const DebugInfoMapping* map = VG_(indexXA)(di->fsm.maps, j); -- if ( (map->rx || map->rw) -+ if ( (map->rx || map->rw || map->ro) - && map->size > 0 /* stay sane */ - && a_phdr.p_offset >= map->foff - && a_phdr.p_offset < map->foff + map->size -@@ -1816,6 +1816,16 @@ - i, (UWord)item.bias); - loaded = True; - } -+ if (map->ro -+ && (a_phdr.p_flags & (PF_R | PF_W | PF_X)) -+ == PF_R) { -+ item.exec = False; -+ VG_(addToXA)(svma_ranges, &item); -+ TRACE_SYMTAB( -+ "PT_LOAD[%ld]: acquired as ro, bias 0x%lx\n", -+ i, (UWord)item.bias); -+ loaded = True; -+ } - } - } - if (!loaded) { -@@ -2083,17 +2093,25 @@ - } - } - -- /* Accept .rodata where mapped as rx (data), even if zero-sized */ -+ /* Accept .rodata where mapped as rx or rw (data), even if zero-sized */ - if (0 == VG_(strcmp)(name, ".rodata")) { -- if (inrx && !di->rodata_present) { -- di->rodata_present = True; -+ if (!di->rodata_present) { - di->rodata_svma = svma; -- di->rodata_avma = svma + inrx->bias; -+ di->rodata_avma = svma; - di->rodata_size = size; -- di->rodata_bias = inrx->bias; - di->rodata_debug_svma = svma; -- di->rodata_debug_bias = inrx->bias; -- /* NB was 'inrw' prior to r11794 */ -+ if (inrx) { -+ di->rodata_avma += inrx->bias; -+ di->rodata_bias = inrx->bias; -+ di->rodata_debug_bias = inrx->bias; -+ } else if (inrw) { -+ di->rodata_avma += inrw->bias; -+ di->rodata_bias = inrw->bias; -+ di->rodata_debug_bias = inrw->bias; -+ } else { -+ BAD(".rodata"); -+ } -+ di->rodata_present = True; - TRACE_SYMTAB("acquiring .rodata svma = %#lx .. %#lx\n", - di->rodata_svma, - di->rodata_svma + di->rodata_size - 1); diff --git a/dev-util/valgrind/files/valgrind-3.13.0-ignore-further-mappings-after-read-all-debuginfo.patch b/dev-util/valgrind/files/valgrind-3.13.0-ignore-further-mappings-after-read-all-debuginfo.patch deleted file mode 100644 index 5b47512c1553..000000000000 --- a/dev-util/valgrind/files/valgrind-3.13.0-ignore-further-mappings-after-read-all-debuginfo.patch +++ /dev/null @@ -1,70 +0,0 @@ -Follow up for valgrind-3.13.0-accept-read-only-PT_LOAD-segments-and-rodata.patch. - -From e752326cc050803c3bcfde1f8606bead66ff9642 Mon Sep 17 00:00:00 2001 -From: Julian Seward <jseward@acm.org> -Date: Tue, 14 Aug 2018 10:13:46 +0200 -Subject: [PATCH] VG_(di_notify_mmap): once we've read debuginfo for an object, - ignore all further mappings. n-i-bz. - -Once we've read debuginfo for an object, ignore all further mappings. If we -don't do that, applications that mmap in their own objects to inspect them for -whatever reason, will cause "irrelevant" mappings to be recorded in the -object's fsm.maps table. This can lead to serious problems later on. - -This has become necessary because 64aa729bfae71561505a40c12755bd6b55bb3061 of -Thu Jul 12 2018 (the fix for bug 395682) started recording readonly segments -in the fsm.maps table, where before they were ignored. ---- - coregrind/m_debuginfo/debuginfo.c | 29 ++++++++++++++++++++++++++++- - 1 file changed, 28 insertions(+), 1 deletion(-) - -diff --git a/coregrind/m_debuginfo/debuginfo.c b/coregrind/m_debuginfo/debuginfo.c -index c36d498..55c05cb 100644 ---- a/coregrind/m_debuginfo/debuginfo.c -+++ b/coregrind/m_debuginfo/debuginfo.c -@@ -1200,6 +1200,32 @@ ULong VG_(di_notify_mmap)( Addr a, Bool allow_SkFileV, Int use_fd ) - di = find_or_create_DebugInfo_for( filename ); - vg_assert(di); - -+ /* Ignore all mappings for this filename once we've read debuginfo for it. -+ This avoids the confusion of picking up "irrelevant" mappings in -+ applications which mmap their objects outside of ld.so, for example -+ Firefox's Gecko profiler. -+ -+ What happens in that case is: the application maps the object "ro" for -+ whatever reason. We record the mapping di->fsm.maps. The application -+ later unmaps the object. However, the mapping is not removed from -+ di->fsm.maps. Later, when some other (unrelated) object is mapped (via -+ ld.so) into that address space, we first unload any debuginfo that has a -+ mapping intersecting that area. That means we will end up incorrectly -+ unloading debuginfo for the object with the "irrelevant" mappings. This -+ causes various problems, not least because it can unload the debuginfo -+ for libc.so and so cause malloc intercepts to become un-intercepted. -+ -+ This fix assumes that all mappings made once we've read debuginfo for -+ an object are irrelevant. I think that's OK, but need to check with -+ mjw/thh. */ -+ if (di->have_dinfo) { -+ if (debug) -+ VG_(printf)("di_notify_mmap-4x: " -+ "ignoring mapping because we already read debuginfo " -+ "for DebugInfo* %p\n", di); -+ return 0; -+ } -+ - if (debug) - VG_(printf)("di_notify_mmap-4: " - "noting details in DebugInfo* at %p\n", di); -@@ -1220,7 +1246,8 @@ ULong VG_(di_notify_mmap)( Addr a, Bool allow_SkFileV, Int use_fd ) - di->fsm.have_ro_map |= is_ro_map; - - /* So, finally, are we in an accept state? */ -- if (di->fsm.have_rx_map && di->fsm.have_rw_map && !di->have_dinfo) { -+ vg_assert(!di->have_dinfo); -+ if (di->fsm.have_rx_map && di->fsm.have_rw_map) { - /* Ok, so, finally, we found what we need, and we haven't - already read debuginfo for this object. So let's do so now. - Yee-ha! */ --- -2.9.3 - diff --git a/dev-util/valgrind/files/valgrind-3.13.0-test-fixes.patch b/dev-util/valgrind/files/valgrind-3.13.0-test-fixes.patch deleted file mode 100644 index 9bdd29013ba7..000000000000 --- a/dev-util/valgrind/files/valgrind-3.13.0-test-fixes.patch +++ /dev/null @@ -1,29 +0,0 @@ -See: -https://bugs.gentoo.org/637488 -https://bugs.kde.org/show_bug.cgi?id=387686 - -commit 2b5eab6a8db1b0487a3ad7fc4e7eeda6d3513626 -Author: Mark Wielaard <mark@klomp.org> -Date: Thu Jun 29 15:26:30 2017 +0000 - - memcheck/tests: Use ucontext_t instead of struct ucontext - - glibc 2.26 does not expose struct ucontext anymore. - - Signed-off-by: Khem Raj <raj.khem@gmail.com> - - git-svn-id: svn://svn.valgrind.org/valgrind/trunk@16457 - -diff --git a/memcheck/tests/linux/stack_changes.c b/memcheck/tests/linux/stack_changes.c -index a978fc2b0..7f97b90a5 100644 ---- a/memcheck/tests/linux/stack_changes.c -+++ b/memcheck/tests/linux/stack_changes.c -@@ -10,7 +10,7 @@ - // This test is checking the libc context calls (setcontext, etc.) and - // checks that Valgrind notices their stack changes properly. - --typedef struct ucontext mycontext; -+typedef ucontext_t mycontext; - - mycontext ctx1, ctx2, oldc; - int count; diff --git a/dev-util/valgrind/files/valgrind-3.13.0-xml-socket.patch b/dev-util/valgrind/files/valgrind-3.13.0-xml-socket.patch deleted file mode 100644 index 56039c48bc27..000000000000 --- a/dev-util/valgrind/files/valgrind-3.13.0-xml-socket.patch +++ /dev/null @@ -1,27 +0,0 @@ -From: Ivo Raisr <ivosh@ivosh.net> -Date: Thu, 3 Aug 2017 05:22:01 +0000 (+0000) -Subject: Fix handling command line option --xml-socket. -X-Git-Url: https://sourceware.org/git/?p=valgrind.git;a=commitdiff_plain;h=34dd8493de39314033509bb7ad62673f33dcf3db - -Fix handling command line option --xml-socket. -Fixes BZ#382998 -Patch by: Orgad Shaneh <orgads@gmail.com> - - - -git-svn-id: svn://svn.valgrind.org/valgrind/trunk@16467 ---- - -diff --git a/coregrind/m_libcprint.c b/coregrind/m_libcprint.c -index d66c67d..f6ba202 100644 ---- a/coregrind/m_libcprint.c -+++ b/coregrind/m_libcprint.c -@@ -526,7 +526,7 @@ void VG_(init_log_xml_sinks)(VgLogTo log_to, VgLogTo xml_to, - break; - - case VgLogTo_Socket: -- log_fd = prepare_sink_socket(VG_(clo_xml_fname_unexpanded), -+ xml_fd = prepare_sink_socket(VG_(clo_xml_fname_unexpanded), - &VG_(xml_output_sink), True); - break; - } diff --git a/dev-util/valgrind/files/valgrind-3.7.0-fno-stack-protector.patch b/dev-util/valgrind/files/valgrind-3.7.0-fno-stack-protector.patch deleted file mode 100644 index 6af455319567..000000000000 --- a/dev-util/valgrind/files/valgrind-3.7.0-fno-stack-protector.patch +++ /dev/null @@ -1,12 +0,0 @@ -diff -Naur valgrind-3.7.0.orig//Makefile.all.am valgrind-3.7.0/Makefile.all.am ---- valgrind-3.7.0.orig//Makefile.all.am 2011-10-26 17:24:45.000000000 -0400 -+++ valgrind-3.7.0/Makefile.all.am 2011-11-10 16:18:18.000000000 -0500 -@@ -82,7 +82,7 @@ - # performance and get whatever useful warnings we can out of gcc. - # -fno-builtin is important for defeating LLVM's idiom recognition - # that somehow causes VG_(memset) to get into infinite recursion. --AM_CFLAGS_BASE = \ -+AM_CFLAGS_BASE = -fno-stack-protector \ - -O2 -g \ - -Wall \ - -Wmissing-prototypes \ |