https://bugs.kde.org/show_bug.cgi?id=371916
Josef Weidendorfer changed:
What|Removed |Added
CC||josef.weidendor...@gmx.de
--- Comment #15
https://bugs.kde.org/show_bug.cgi?id=371916
--- Comment #17 from Josef Weidendorfer ---
(In reply to Philippe Waroquiers from comment #16)
> > About the changes in the malloc
> > wrappers, I think it would be better if the tool can register handlers,
> > and these hand
https://bugs.kde.org/show_bug.cgi?id=371916
--- Comment #19 from Josef Weidendorfer ---
(In reply to Julian Seward from comment #18)
> + Copyright (C) 2016-2016 Philippe Waroquiers
>
> For m_xtree.c, if there is a lot of code in there which has been moved
> from massif and/or ca
https://bugs.kde.org/show_bug.cgi?id=372643
--- Comment #1 from Josef Weidendorfer ---
> but this catalog is not loaded into kcachgrind nor into qcachegrind.
Oops. I think that translations in a developer tool such as kcachegrind
often is more confusing than useful, but it has to work.
https://bugs.kde.org/show_bug.cgi?id=372643
--- Comment #3 from Josef Weidendorfer ---
(In reply to Albert Astals Cid from comment #2)
> > qcachegrind (the pure-Qt version of kcachegrind) should just depend on Qt,
> > and no need for it to support translations.
> What ma
https://bugs.kde.org/show_bug.cgi?id=469972
Josef Weidendorfer changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=451837
Josef Weidendorfer changed:
What|Removed |Added
Assignee|josef.weidendor...@gmx.de |jsew...@acm.org
Component
https://bugs.kde.org/show_bug.cgi?id=424077
--- Comment #1 from Josef Weidendorfer ---
I do not care, as this was a user contribution and I never used it myself.
But I would assume there still are quite some Python 2 users out there?
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=420748
Josef Weidendorfer changed:
What|Removed |Added
Resolution|FIXED |NOT A BUG
--- Comment #4 from Josef
https://bugs.kde.org/show_bug.cgi?id=424078
--- Comment #2 from Josef Weidendorfer ---
Just saw this now. Interesting, and thanks for the clarifications.
As kcachgrind and converters can be executed completely independently
without needing each other in any way, it should be clear that this is
https://bugs.kde.org/show_bug.cgi?id=415293
--- Comment #10 from Josef Weidendorfer ---
Original Callgrind author here...
Sorry for not checking my old email address for open-source projects obviously
for almost 1 1/2 years... just see this now, as I was checking out callgrind on
recent Ubuntu
https://bugs.kde.org/show_bug.cgi?id=487358
Josef Weidendorfer changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=388017
--- Comment #4 from Josef Weidendorfer ---
Good to see that `--trace-children=yes` worked!
Just as remark:
Callgrind opens a file descriptor at start to allow output
to be written to the directory which was the current working
directory at prgoram
https://bugs.kde.org/show_bug.cgi?id=403802
Bug ID: 403802
Summary: leak_cpp_interior fails with some reachable blocks
different than expected
Product: valgrind
Version: 3.4.0
Platform: Compiled Sources
OS:
https://bugs.kde.org/show_bug.cgi?id=388740
--- Comment #2 from Josef Weidendorfer ---
Interesting suggestion.
For multithreaded code, this time will be the same for multiple files.
Is this about the ordering in the "parts overview"?
Does it help to add a column "Creation time&q
https://bugs.kde.org/show_bug.cgi?id=388740
--- Comment #5 from Josef Weidendorfer ---
> hmm... then maybe there could be a hierarchy for the ordering : first
> creation time, then PID ?
This should be done automatically by the Qt widget...
Adding the column should be easy, by looking
https://bugs.kde.org/show_bug.cgi?id=399322
--- Comment #1 from Josef Weidendorfer ---
Thanks, the patch looks good! Will have to wait for 3.14 to get out
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=399355
--- Comment #1 from Josef Weidendorfer ---
On a first look, this patch looks fine.
I would split the unrelated parts into separate commits (I can do that).
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=380858
Josef Weidendorfer changed:
What|Removed |Added
Status|UNCONFIRMED |CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=392449
Josef Weidendorfer changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=385127
Josef Weidendorfer changed:
What|Removed |Added
Status|UNCONFIRMED |CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=385127
Josef Weidendorfer changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=385127
--- Comment #6 from Josef Weidendorfer ---
BTW, the bug was due to going to std::sort instead of Qt's qSort in a few
places.
std::sort is more strict and requires strict ordering from the compare
function.
Otherwise, out-of-bound accesses could h
https://bugs.kde.org/show_bug.cgi?id=372643
--- Comment #7 from Josef Weidendorfer ---
Ah, I should have closed this bug after Luigi's fix,
which uses the ECM feature.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=379159
--- Comment #1 from Josef Weidendorfer ---
The backtrace is not enough for me to understand/reproduce the issue.
I only see that the machine code view was requested to be updated before
crashing.
Is this reproducable for you? Any chance to send me the
https://bugs.kde.org/show_bug.cgi?id=379438
Josef Weidendorfer changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=380942
Josef Weidendorfer changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Ever confirmed|0
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 rec
https://bugs.kde.org/show_bug.cgi?id=366142
Josef Weidendorfer changed:
What|Removed |Added
Component|callgrind |general
Assignee
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 r
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 o
https://bugs.kde.org/show_bug.cgi?id=368751
Josef Weidendorfer changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=368751
Josef Weidendorfer changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://bugs.kde.org/show_bug.cgi?id=368751
Josef Weidendorfer changed:
What|Removed |Added
Severity|normal |crash
--- Comment #1 from Josef
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
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"
https://bugs.kde.org/show_bug.cgi?id=362939
Josef Weidendorfer changed:
What|Removed |Added
Component|callgrind |general
Assignee
https://bugs.kde.org/show_bug.cgi?id=361726
Josef Weidendorfer changed:
What|Removed |Added
Component|callgrind |general
Assignee
38 matches
Mail list logo
