[kcachegrind] [Bug 368751] KCachegrind crashes after a profile gets loaded

2016-10-21 Thread Josef Weidendorfer via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=368751 Josef Weidendorfer changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[kcachegrind] [Bug 368751] KCachegrind crashes after a profile gets loaded

2016-09-29 Thread Josef Weidendorfer via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=368751 Josef Weidendorfer changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED

[kcachegrind] [Bug 368751] KCachegrind crashes after a profile gets loaded

2016-09-29 Thread Josef Weidendorfer via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=368751 --- Comment #5 from Josef Weidendorfer --- Created attachment 101346 --> https://bugs.kde.org/attachment.cgi?id=101346&action=edit Proposed patch After private conversation, the bug should be fixed with the proposed patch. The code accesses one byte

[valgrind] [Bug 369456] callgrind_control failed to find an active callgrind run.

2016-09-28 Thread Josef Weidendorfer via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=369456 --- Comment #1 from Josef Weidendorfer --- callgrind_control uses "vgdb" starting from Valgrind 3.11 to get a list of running valgrind instances. Perhaps this is not working on OSX. What is the output of "vgdb -l" with callgrind running? -- You are re

[kcachegrind] [Bug 368751] KCachegrind crashes after a profile gets loaded

2016-09-13 Thread Josef Weidendorfer via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=368751 --- Comment #4 from Josef Weidendorfer --- Hmm... probably not out-of-memory then. Any chance for me to reproduce the bug, ie. can you make the file available to me (e.g. via sending me a link in private email)? -- You are receiving this mail because

[kcachegrind] [Bug 368751] KCachegrind crashes after a profile gets loaded

2016-09-13 Thread Josef Weidendorfer via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=368751 Josef Weidendorfer changed: What|Removed |Added Severity|normal |crash --- Comment #1 from Josef Weidendorf

[valgrind] [Bug 366142] Illegal opcode _mm_maskload_ps

2016-07-28 Thread Josef Weidendorfer via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366142 Josef Weidendorfer changed: What|Removed |Added Component|callgrind |general Assignee|josef.weidendor

[valgrind] [Bug 362939] test apk in android 5.0 or most,at 0x6A23AB4: art::Thread::InstallImplicitProtection() (in /system/lib/libart.so)

2016-05-12 Thread Josef Weidendorfer via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362939 Josef Weidendorfer changed: What|Removed |Added Component|callgrind |general Assignee|josef.weidendor

[valgrind] [Bug 356675] callgrind test apk in android 5.0.2

2016-05-12 Thread Josef Weidendorfer via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356675 --- Comment #2 from Josef Weidendorfer --- Can you provide the complete output of the crash? As the patch is about VG core stuff, I assume the crash also happens with other VG tools? If so, It seems better to re-assign this to "general" component. --

[valgrind] [Bug 361726] WARNING:unhandled syscall on ppc64

2016-04-18 Thread Josef Weidendorfer via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361726 Josef Weidendorfer changed: What|Removed |Added Component|callgrind |general Assignee|josef.weidendor

[valgrind] [Bug 356044] Dwarf line info reader misinterprets is_stmt register

2015-11-30 Thread Josef Weidendorfer via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356044 --- Comment #3 from Josef Weidendorfer --- Am 28.11.2015 um 22:03 schrieb Ivo Raisr via KDE Bugzilla: > DWARF v4 says about "is_stmt": > A boolean indicating that the current instruction is a recommended breakpoint > location. A recommended breakpoint l