[valgrind] [Bug 502708] symbol lookup error: /usr/libexec/valgrind/vgpreload_memcheck-arm-linux.so: undefined symbol: __aeabi_uidiv

2025-04-28 Thread Fred M
https://bugs.kde.org/show_bug.cgi?id=502708 Fred M changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED

[valgrind] [Bug 502708] symbol lookup error: /usr/libexec/valgrind/vgpreload_memcheck-arm-linux.so: undefined symbol: __aeabi_uidiv

2025-04-28 Thread Fred M
https://bugs.kde.org/show_bug.cgi?id=502708 --- Comment #1 from Fred M --- finally, I forced : LDFLAGS := -lgcc -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 502708] New: symbol lookup error: /usr/libexec/valgrind/vgpreload_memcheck-arm-linux.so: undefined symbol: __aeabi_uidiv

2025-04-12 Thread Fred M
https://bugs.kde.org/show_bug.cgi?id=502708 Bug ID: 502708 Summary: symbol lookup error: /usr/libexec/valgrind/vgpreload_memcheck-arm-linux.so: undefined symbol: __aeabi_uidiv Classification: Developer tools Product: val

[valgrind] [Bug 498614] callgrind_control equivalent with vgdb ?

2025-01-13 Thread Fred M
https://bugs.kde.org/show_bug.cgi?id=498614 --- Comment #2 from Fred M --- Well, I found "vgdb instrumentation on" in the callgrind_control script -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 498614] callgrind_control equivalent with vgdb ?

2025-01-13 Thread Fred M
https://bugs.kde.org/show_bug.cgi?id=498614 --- Comment #1 from Fred M --- or maybe an argument valgrind to ask to start after X instruction ? -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 498614] New: callgrind_control equivalent with vgdb ?

2025-01-13 Thread Fred M
https://bugs.kde.org/show_bug.cgi?id=498614 Bug ID: 498614 Summary: callgrind_control equivalent with vgdb ? Classification: Developer tools Product: valgrind Version: 3.24 GIT Platform: Other OS: Linux Status:

[valgrind] [Bug 492947] New: valgrind/massif ARM => missing backtrace in case of valgrind strip.

2024-09-10 Thread Fred M
https://bugs.kde.org/show_bug.cgi?id=492947 Bug ID: 492947 Summary: valgrind/massif ARM => missing backtrace in case of valgrind strip. Classification: Developer tools Product: valgrind Version: 3.23.0 Platform: Other

[valgrind] [Bug 488715] New: support on README_MISSING_SYSCALL_OR_IOCTL for an automatic method?

2024-06-19 Thread Fred M
https://bugs.kde.org/show_bug.cgi?id=488715 Bug ID: 488715 Summary: support on README_MISSING_SYSCALL_OR_IOCTL for an automatic method? Classification: Developer tools Product: valgrind Version: unspecified Platform: Ot

[massif-visualizer] [Bug 488671] how to build with Ubuntu 24.04 ?

2024-06-18 Thread Fred M
https://bugs.kde.org/show_bug.cgi?id=488671 --- Comment #2 from Fred M --- idem : sudo apt-get install qt6-base-dev CMake Error at CMakeLists.txt:35 (find_package): Could not find a configuration file for package "Qt6" that is compatible with requested version "6.5.0&quo

[massif-visualizer] [Bug 488671] how to build with Ubuntu 24.04 ?

2024-06-18 Thread Fred M
https://bugs.kde.org/show_bug.cgi?id=488671 --- Comment #1 from Fred M --- from : https://launchpad.net/ubuntu/noble/+source/massif-visualizer , it seems to be : sudo apt install cmake debhelper-compat extra-cmake-modules libkchart-dev libkf5archive-dev libkf5config-dev libkf5coreaddons-dev

[massif-visualizer] [Bug 488671] New: how to build with Ubuntu 24.04 ?

2024-06-18 Thread Fred M
https://bugs.kde.org/show_bug.cgi?id=488671 Bug ID: 488671 Summary: how to build with Ubuntu 24.04 ? Classification: Frameworks and Libraries Product: massif-visualizer Version: master Platform: Ubuntu OS: Linux

[valgrind] [Bug 475634] valgrind is not starting

2024-04-28 Thread Fred M
https://bugs.kde.org/show_bug.cgi?id=475634 Fred M changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution

[valgrind] [Bug 479191] vgdb is blocked after several tries

2024-01-02 Thread Fred M
https://bugs.kde.org/show_bug.cgi?id=479191 --- Comment #3 from Fred M --- Created attachment 164625 --> https://bugs.kde.org/attachment.cgi?id=164625&action=edit valgrind -d -d -d logs Hello, [What is the reason for this in your case ?] For no reason, I could retry without it if

[valgrind] [Bug 479191] New: vgdb is blocked after several tries

2023-12-30 Thread Fred M
https://bugs.kde.org/show_bug.cgi?id=479191 Bug ID: 479191 Summary: vgdb is blocked after several tries Classification: Developer tools Product: valgrind Version: 3.22 GIT Platform: Other OS: Other Status: REPOR

[valgrind] [Bug 475634] valgrind is not starting

2023-12-09 Thread Fred M
https://bugs.kde.org/show_bug.cgi?id=475634 --- Comment #3 from Fred M --- Maybe, I found the root cause, After the vagrind & I do a "sleep" https://bugs.busybox.net/show_bug.cgi?id=15619 Bug 15631 - sleep command after '&' in a shell script has no effect The

[valgrind] [Bug 475634] New: valgrind is no starting

2023-10-14 Thread Fred M
https://bugs.kde.org/show_bug.cgi?id=475634 Bug ID: 475634 Summary: valgrind is no starting Classification: Developer tools Product: valgrind Version: 3.22 GIT Platform: Other OS: Other Status: REPORTED

[valgrind] [Bug 475208] error: cannot take snapshot before execution has started

2023-10-04 Thread Fred M
https://bugs.kde.org/show_bug.cgi?id=475208 --- Comment #1 from Fred M --- I workarounded like this : sleep 10 vgdb detailed_snapshot my_output.out while [[ $? != 0 ]]; do sleep 60 vgdb detailed_snapshot my_output.out done -- You are receiving this mail because: You are watching all bug

[valgrind] [Bug 475208] New: error: cannot take snapshot before execution has started

2023-10-04 Thread Fred M
https://bugs.kde.org/show_bug.cgi?id=475208 Bug ID: 475208 Summary: error: cannot take snapshot before execution has started Classification: Developer tools Product: valgrind Version: 3.22 GIT Platform: Other

[valgrind] [Bug 465176] disInstr(thumb): unhandled instruction: 0xF2AD 0x0440

2023-05-03 Thread Fred M
https://bugs.kde.org/show_bug.cgi?id=465176 --- Comment #2 from Fred M --- note to myself: linked to webkit, to workaround this issue, I can do : JavaScriptCoreUseJIT=0 JSC_useFTLJIT=0 valgrind WPE_X -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 465176] disInstr(thumb): unhandled instruction: 0xF2AD 0x0440

2023-02-02 Thread Fred M
https://bugs.kde.org/show_bug.cgi?id=465176 --- Comment #1 from Fred M --- reproduced also with the current valgrind git master -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 465176] New: disInstr(thumb): unhandled instruction: 0xF2AD 0x0440

2023-02-02 Thread Fred M
https://bugs.kde.org/show_bug.cgi?id=465176 Bug ID: 465176 Summary: disInstr(thumb): unhandled instruction: 0xF2AD 0x0440 Classification: Developer tools Product: valgrind Version: 3.20.0 Platform: Other OS: Other

[valgrind] [Bug 344802] disInstr(arm): unhandled instruction: 0xEC510F1E

2018-12-18 Thread Fred M
https://bugs.kde.org/show_bug.cgi?id=344802 Fred M changed: What|Removed |Added CC||dark_foo...@yahoo.fr --- Comment #19 from Fred M

[valgrind] [Bug 391861] Massif Assertion 'n_ips >= 1 && n_ips <= VG_(clo_backtrace_size)'

2018-03-26 Thread Fred M
https://bugs.kde.org/show_bug.cgi?id=391861 Fred M changed: What|Removed |Added CC||dark_foo...@yahoo.fr --- Comment #5 from Fred M

[valgrind] [Bug 383275] massif valgrind: m_xarray.c:162 (ensureSpaceXA): Assertion '!xa->arr' failed

2017-08-17 Thread Fred M
https://bugs.kde.org/show_bug.cgi?id=383275 --- Comment #3 from Fred M --- not reproduced on the rev 16470 . -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 383275] New: [mipsel] valgrind: m_xarray.c:162 (ensureSpaceXA): Assertion '!xa->arr' failed.

2017-08-08 Thread Fred M
https://bugs.kde.org/show_bug.cgi?id=383275 Bug ID: 383275 Summary: [mipsel] valgrind: m_xarray.c:162 (ensureSpaceXA): Assertion '!xa->arr' failed. Product: valgrind Version: 3.13.0 Platform: Compiled Sources