https://bugs.kde.org/show_bug.cgi?id=340777
--- Comment #18 from Petar Jovanovic ---
(In reply to Luiz Angelo De Luca from comment #17)
> I switched to a new git mirror source.
>
> valgrind works like a charm with trunk@16292. Thank you very much.
>
Glad to hear so.
> Would it take too long t
https://bugs.kde.org/show_bug.cgi?id=340777
Luiz Angelo De Luca changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=340777
--- Comment #16 from Petar Jovanovic ---
(In reply to Luiz Angelo De Luca from comment #15)
> root@router.lan3:/usr/bin# valgrind --version
> valgrind-3.13.0.SVN
>
> The test was using commit svn://svn.valgrind.org/valgrind/trunk@16225
> a5019735-40e9-
https://bugs.kde.org/show_bug.cgi?id=340777
--- Comment #15 from Luiz Angelo De Luca ---
root@router.lan3:/usr/bin# valgrind --version
valgrind-3.13.0.SVN
The test was using commit svn://svn.valgrind.org/valgrind/trunk@16225
a5019735-40e9-0310-863c-91ae7b9d1cf9 That I got from
https://github.com
https://bugs.kde.org/show_bug.cgi?id=340777
--- Comment #14 from Petar Jovanovic ---
Luiz, any update?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=340777
--- Comment #13 from Petar Jovanovic ---
We are not able to reproduce this issue on our board with OpenWRT.
Can you confirm that you have tried running the latest SVN version of Valgrind
WITH the patch for MUSL (https://bugs.kde.org/show_bug.cgi?id=3592
https://bugs.kde.org/show_bug.cgi?id=340777
--- Comment #12 from Luiz Angelo De Luca ---
> Can you pass the following lines to gbd and rerun the executable?
>
> set heuristic-fence-post 99
> handle SIGSEGV noprint nostop pass
>
> Keep running (w/ "continue") GDB until it fails.
If I use bo
https://bugs.kde.org/show_bug.cgi?id=340777
--- Comment #11 from Petar Jovanovic ---
(In reply to Luiz Angelo De Luca from comment #10)
> Here is where I get the SIGSEGV. Maybe stack got corrupted. Is there any
> tips from here?
Receiving some of these signals in GDB is an expected behaviour.
C
https://bugs.kde.org/show_bug.cgi?id=340777
--- Comment #10 from Luiz Angelo De Luca ---
The patch was already in use. See:
https://github.com/lede-project/source/blob/lede-17.01/package/devel/valgrind/patches/200-musl_fix.patch
I managed to compile a SVN version
https://github.com/lede-project/
https://bugs.kde.org/show_bug.cgi?id=340777
--- Comment #9 from Petar Jovanovic ---
I believe the new (non-mips16) issues are not MIPS-related, but rather
MUSL-related.
Can you try to apply the patch in the second comment Bug 359202 and see if it
sorts out your issues with binaries that do not h
https://bugs.kde.org/show_bug.cgi?id=340777
--- Comment #8 from Luiz Angelo De Luca ---
Btw, at least the --help do works now (first failing case)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=340777
--- Comment #7 from Luiz Angelo De Luca ---
Most of binaries are mips16 on OpenWRT or LEDE.
$
./staging_dir/toolchain-mips_24kc_gcc-5.4.0_musl-1.1.16/bin/mips-openwrt-linux-readelf
-h staging_dir/target-mips_24kc_musl-1.1.16/root-ar71xx/bin/busybox
ELF
https://bugs.kde.org/show_bug.cgi?id=340777
--- Comment #6 from Petar Jovanovic ---
(In reply to Luiz Angelo De Luca from comment #5)
>==24067== Illegal opcode at address 0x4077B5
>==24067==at 0x4077B5: ??? (in /bin/busybox)
This looks suspicious. Is that busybox that has been compiled with
https://bugs.kde.org/show_bug.cgi?id=340777
--- Comment #5 from Luiz Angelo De Luca ---
Is it really necessary to test SVN? At least with 3.12.0, the problem remains:
# valgrind ping 8.8.8.8
==24067== Memcheck, a memory error detector
==24067== Copyright (C) 2002-2015, and GNU GPL'd, by Julian S
https://bugs.kde.org/show_bug.cgi?id=340777
--- Comment #4 from Petar Jovanovic ---
Is this issue still valid?
Are you seeing the issue with the latest Valgrind SVN code?
--
You are receiving this mail because:
You are watching all bug changes.
15 matches
Mail list logo
