[valgrind] [Bug 479600] Segmentation fault launching the valgrind (mipsel-openwrt-linux-musl-gcc)

2024-04-09 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=479600 Mark Wielaard changed: What|Removed |Added Summary|Segmentation fault |Segmentation fault

[valgrind] [Bug 479600] Segmentation fault launching the valgrind

2024-01-11 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=479600 --- Comment #4 from erikas.masai...@teltonika.lt --- Updated musl. Now i am getting: ==12556== Memcheck, a memory error detector ==12556== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al. ==12556== Using

[valgrind] [Bug 479600] Segmentation fault launching the valgrind

2024-01-10 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=479600 --- Comment #3 from Paul Floyd --- The redirect is likely to be from either the link loader ld.so or from libc. If it is from ld.so it might be a phony implmentation in which malloc returns some global or stack memory and free does nothing. Possibly

[valgrind] [Bug 479600] Segmentation fault launching the valgrind

2024-01-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=479600 --- Comment #2 from erikas.masai...@teltonika.lt --- (In reply to Paul Floyd from comment #1) > You need to understand where the invalid free is happening. > > Seeing a redirect for free but not malloc is unusual. you mean in my code, or in libc? --

[valgrind] [Bug 479600] Segmentation fault launching the valgrind

2024-01-10 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=479600 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr --- Comment #1 from Paul Floyd