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

https://bugs.kde.org/show_bug.cgi?id=383275 --- Comment #3 from Fred M <dark_foo...@yahoo.fr> --- 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.

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

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

https://bugs.kde.org/show_bug.cgi?id=391861 Fred M <dark_foo...@yahoo.fr> changed: What|Removed |Added CC||dark_foo...@ya

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

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 475208] error: cannot take snapshot before execution has started

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

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 475634] New: valgrind is no starting

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 465176] New: disInstr(thumb): unhandled instruction: 0xF2AD 0x0440

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 465176] disInstr(thumb): unhandled instruction: 0xF2AD 0x0440

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] disInstr(thumb): unhandled instruction: 0xF2AD 0x0440

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 475634] valgrind is not starting

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 sleep is

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

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:

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

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=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 needed. [chip

[valgrind] [Bug 475634] valgrind is not starting

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