diff options
author | Zhenhua Luo <b19537@freescale.com> | 2012-09-12 16:20:46 +0800 |
---|---|---|
committer | Scott Garman <scott.a.garman@intel.com> | 2012-09-24 09:51:11 -0700 |
commit | a76be502fbb9517c38cd716fa1f21a238b314162 (patch) | |
tree | e5f5415cb4ae6234c0bc48f3684630647b6e2135 /meta/recipes-devtools/valgrind/valgrind-3.7.0/valgrind-3.7.0-fix-error-of-reading-debug-info.patch | |
parent | a0abfd60e8cb78b40278eec85a8d0c722f8ef1e4 (diff) | |
download | openembedded-core-a76be502fbb9517c38cd716fa1f21a238b314162.tar.gz openembedded-core-a76be502fbb9517c38cd716fa1f21a238b314162.tar.bz2 openembedded-core-a76be502fbb9517c38cd716fa1f21a238b314162.zip |
valgrind: fix debug info reading error when do memcheck on ppc targets
following is the error message:
--2263-- WARNING: Serious error when reading debug info
--2263-- When reading debug info from /lib/ld-2.13.so:
--2263-- Can't make sense of .got section mapping
--2263-- WARNING: Serious error when reading debug info
--2263-- When reading debug info from /home/root/lzh:
--2263-- Can't make sense of .data section mapping
--2263-- WARNING: Serious error when reading debug info
--2263-- When reading debug info from /usr/lib/valgrind/vgpreload_core-ppc32-linux.so:
--2263-- Can't make sense of .data section mapping
--2263-- WARNING: Serious error when reading debug info
--2263-- When reading debug info from /usr/lib/valgrind/vgpreload_memcheck-ppc32-linux.so:
--2263-- Can't make sense of .data section mapping
--2263-- WARNING: Serious error when reading debug info
--2263-- When reading debug info from /lib/libc-2.13.so:
--2263-- Can't make sense of .data section mapping
(From OE-Core rev: 14626cc76210ed6fe40316a311f24147ed8de8be)
Signed-off-by: Zhenhua Luo <b19537@freescale.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-devtools/valgrind/valgrind-3.7.0/valgrind-3.7.0-fix-error-of-reading-debug-info.patch')
-rw-r--r-- | meta/recipes-devtools/valgrind/valgrind-3.7.0/valgrind-3.7.0-fix-error-of-reading-debug-info.patch | 33 |
1 files changed, 33 insertions, 0 deletions
diff --git a/meta/recipes-devtools/valgrind/valgrind-3.7.0/valgrind-3.7.0-fix-error-of-reading-debug-info.patch b/meta/recipes-devtools/valgrind/valgrind-3.7.0/valgrind-3.7.0-fix-error-of-reading-debug-info.patch new file mode 100644 index 0000000000..b1626f0b0f --- /dev/null +++ b/meta/recipes-devtools/valgrind/valgrind-3.7.0/valgrind-3.7.0-fix-error-of-reading-debug-info.patch @@ -0,0 +1,33 @@ +Upstream-Status: Pending + +fix debug info reading error when do memcheck on ppc targets + following is the error message: + --2263-- WARNING: Serious error when reading debug info + --2263-- When reading debug info from /lib/ld-2.13.so: + --2263-- Can't make sense of .got section mapping + --2263-- WARNING: Serious error when reading debug info + --2263-- When reading debug info from /home/root/lzh: + --2263-- Can't make sense of .data section mapping + --2263-- WARNING: Serious error when reading debug info + --2263-- When reading debug info from /usr/lib/valgrind/vgpreload_core-ppc32-linux.so: + --2263-- Can't make sense of .data section mapping + --2263-- WARNING: Serious error when reading debug info + --2263-- When reading debug info from /usr/lib/valgrind/vgpreload_memcheck-ppc32-linux.so: + --2263-- Can't make sense of .data section mapping + --2263-- WARNING: Serious error when reading debug info + --2263-- When reading debug info from /lib/libc-2.13.so: + --2263-- Can't make sense of .data section mapping + +Signed-off-by: Zhenhua Luo <b19537@freescale.com> + +--- a/coregrind/m_debuginfo/readelf.c 2012-09-11 21:45:36.696462313 -0500 ++++ b/coregrind/m_debuginfo/readelf.c 2012-09-11 21:45:49.913463615 -0500 +@@ -1539,7 +1539,7 @@ + && phdr->p_offset < di->fsm.rw_map_foff + di->fsm.rw_map_size + && phdr->p_offset + phdr->p_filesz + <= di->fsm.rw_map_foff + di->fsm.rw_map_size +- && (phdr->p_flags & (PF_R | PF_W | PF_X)) == (PF_R | PF_W)) { ++ && (phdr->p_flags & (PF_R | PF_W | PF_X)) >= (PF_R | PF_W)) { + if (n_rw == N_RX_RW_AREAS) { + ML_(symerr)(di, True, + "N_RX_RW_AREAS is too low; " |