https://bugs.kde.org/show_bug.cgi?id=415872
Milian Wolff changed:
What|Removed |Added
CC||josep.m.pe...@gmail.com
--- Comment #20 from
https://bugs.kde.org/show_bug.cgi?id=264470
Milian Wolff changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=424732
Milian Wolff changed:
What|Removed |Added
Resolution|--- |UPSTREAM
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=424530
--- Comment #3 from Milian Wolff ---
Can you check and see if it works with a trivial CMake-based project?
thanks
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=424530
--- Comment #1 from Milian Wolff ---
The >''< seems to be the issue - it doesn't use the binary of your executable
properly - can you check why? this is actually a value that comes from the
project builder, so potentially it is a
https://bugs.kde.org/show_bug.cgi?id=421719
Milian Wolff changed:
What|Removed |Added
Ever confirmed|0 |1
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=421719
Milian Wolff changed:
What|Removed |Added
Resolution|--- |BACKTRACE
Component|general
https://bugs.kde.org/show_bug.cgi?id=421509
Milian Wolff changed:
What|Removed |Added
Resolution|--- |FIXED
Latest Commit
https://bugs.kde.org/show_bug.cgi?id=421343
Milian Wolff changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=420771
Milian Wolff changed:
What|Removed |Added
Assignee|kdevelop-bugs-n...@kde.org |kompare-de...@kde.org
Product
https://bugs.kde.org/show_bug.cgi?id=420998
--- Comment #1 from Milian Wolff ---
it's a crash in libclang, so there's not much chance for us to fix it. can you
try to use a newer libclang or kdevelop to see if that is fixed? alternatively,
can you try to set the following env var
https://bugs.kde.org/show_bug.cgi?id=397205
Milian Wolff changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=243232
--- Comment #8 from Milian Wolff ---
Git commit d3e59db950789c4302f8f2ee2865bf1304853392 by Milian Wolff.
Committed on 04/04/2020 at 08:42.
Pushed by mwolff into branch 'master'.
ignore races in QOrderedMutexLocker
M +28 -0kde.s
https://bugs.kde.org/show_bug.cgi?id=419423
Milian Wolff changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|INTENTIONAL
https://bugs.kde.org/show_bug.cgi?id=419423
Milian Wolff changed:
What|Removed |Added
Summary|Incorrect |improve highlighting for
https://bugs.kde.org/show_bug.cgi?id=389837
--- Comment #2 from Milian Wolff ---
Created attachment 127089
--> https://bugs.kde.org/attachment.cgi?id=127089&action=edit
black rect over mail text
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=389837
--- Comment #1 from Milian Wolff ---
for me it's worse, I often see this rect as black on top of my message text,
obscuring the mail message
KMail 5.13.3
KDE Plasma Version: 5.18.3
KDE Frameworks Version: latest git
Qt Version: 5.14.1
--
Yo
https://bugs.kde.org/show_bug.cgi?id=274430
--- Comment #12 from Milian Wolff ---
The problem is that our editor (ktexteditor) operates in utf-16 and
clang/parsing operates in utf-8. we will need to find a way to quickly
translate from one to another to create the highlight ranges
--
You are
https://bugs.kde.org/show_bug.cgi?id=418955
--- Comment #1 from Milian Wolff ---
crash within LLVM/clang, maybe it's depending on g++ for the libstdc++? though
quite odd that it's crashing... anyhow, not really something we can easily fix
in kdevleop I guess?
I'll see if I f
https://bugs.kde.org/show_bug.cgi?id=418544
Milian Wolff changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=418544
--- Comment #2 from Milian Wolff ---
hmm that's bad - can you try the latest code from git? does that run into this
issue too?
if yes, could you by any chance have a look into this? alternatively, can you
get me an example project that I ca
https://bugs.kde.org/show_bug.cgi?id=417679
Milian Wolff changed:
What|Removed |Added
Resolution|--- |FIXED
Latest Commit
https://bugs.kde.org/show_bug.cgi?id=417679
--- Comment #4 from Milian Wolff ---
I've pushed a fix to the 2.2 branch and master, can you try that please? if it
fixes the issue, then we can create a 2.2.2 release
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=417961
Milian Wolff changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution
https://bugs.kde.org/show_bug.cgi?id=418220
Milian Wolff changed:
What|Removed |Added
Resolution|--- |UPSTREAM
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=409235
--- Comment #3 from Milian Wolff ---
can you try the latest kdevelop version from git master which uses the cmake
file api instead of the cmake server mode? maybe that fixes this?
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=417903
Milian Wolff changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Latest Commit
https://bugs.kde.org/show_bug.cgi?id=417202
--- Comment #4 from Milian Wolff ---
Git commit d38ae65bc3b5304e13fd641b4971939e67f70d09 by Milian Wolff.
Committed on 14/02/2020 at 09:23.
Pushed by mwolff into branch 'master'.
Start implementation of cmake-file-api support
Before long
https://bugs.kde.org/show_bug.cgi?id=417202
--- Comment #4 from Milian Wolff ---
Git commit d38ae65bc3b5304e13fd641b4971939e67f70d09 by Milian Wolff.
Committed on 14/02/2020 at 09:23.
Pushed by mwolff into branch 'master'.
Start implementation of cmake-file-api support
Before long
https://bugs.kde.org/show_bug.cgi?id=417202
Milian Wolff changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Latest Commit
https://bugs.kde.org/show_bug.cgi?id=417903
--- Comment #1 from Milian Wolff ---
the issue is that we transmit the wrong defines to the clang parse job, i.e.
one with `#define __cplusplus 201103L` despite the fact that we do also pass
`-std=c++17`.
thanks for the report, I'm looking into
https://bugs.kde.org/show_bug.cgi?id=417903
Milian Wolff changed:
What|Removed |Added
Ever confirmed|0 |1
Component|Analyzer: Cppcheck
https://bugs.kde.org/show_bug.cgi?id=415644
Milian Wolff changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=415644
--- Comment #3 from Milian Wolff ---
funny how noone noticed this until now
I'll apply a patch based on yours now, thanks!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=355348
Milian Wolff changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=267248
Milian Wolff changed:
What|Removed |Added
CC||piotr.mierzwin...@gmail.com
--- Comment #3 from
https://bugs.kde.org/show_bug.cgi?id=417149
--- Comment #2 from Milian Wolff ---
Jan, if you can also reproduce this issue, please - would you be willing to
look at the (old and crude) code in try to figure out how we can fix it on a
hidpi system (assuming you are also running into this issue
https://bugs.kde.org/show_bug.cgi?id=417149
Milian Wolff changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=417151
Milian Wolff changed:
What|Removed |Added
CC||jgrul...@redhat.com
--- Comment #17 from Milian
https://bugs.kde.org/show_bug.cgi?id=402066
Milian Wolff changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde
https://bugs.kde.org/show_bug.cgi?id=417151
--- Comment #16 from Milian Wolff ---
Git commit aa7bc707be21ac268a380a6b4ad972f62b3a72df by Milian Wolff.
Committed on 14/02/2020 at 10:03.
Pushed by mwolff into branch '5.5'.
Don't crash when we fail to find a screen for the active t
https://bugs.kde.org/show_bug.cgi?id=409235
Milian Wolff changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=417151
--- Comment #15 from Milian Wolff ---
quite odd, that output looks super harmless - I think we can't do much more
about this bug until a developer can reproduce it and debug it... at least it
shouldn't crash anymore (I hope)
--
You are rece
https://bugs.kde.org/show_bug.cgi?id=417202
--- Comment #3 from Milian Wolff ---
OK, the branch is now ready for testing. There are some things left to be done,
most notably support for runtimes (docker etc). I'll also have to test it on a
real world project outside the unit tests now.
--
https://bugs.kde.org/show_bug.cgi?id=417202
--- Comment #2 from Milian Wolff ---
I've started working on this now over at
https://invent.kde.org/mwolff/kdevelop/commits/cmake-file-api
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=417151
--- Comment #13 from Milian Wolff ---
Git commit e37549a4b04cd88174b968b37c7061376e0c6744 by Milian Wolff.
Committed on 07/02/2020 at 11:40.
Pushed by mwolff into branch 'master'.
Don't crash when we fail to find a screen for the
https://bugs.kde.org/show_bug.cgi?id=417151
--- Comment #12 from Milian Wolff ---
Thank you, that makes it very clear where it crashes. What's unfortunate is
that I cannot reproduce this. I talked to Aleix yesterday and was even running
KDevelop on a 4k + 2x configuration and didn't se
https://bugs.kde.org/show_bug.cgi?id=402066
Milian Wolff changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=402066
Milian Wolff changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=417151
--- Comment #9 from Milian Wolff ---
quite probably this is a 4K issue then, can you try to see if it reproduces
when you set the scale factor to 1? Obviously it will look like crap, but I
want to see if that fixes the issue for you or not.
And again
https://bugs.kde.org/show_bug.cgi?id=417202
Milian Wolff changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=417151
--- Comment #3 from Milian Wolff ---
That's an odd one. Could you install debug symbols please? I wonder if it's
ActiveTooltip that fails for you, i.e. line 109 in activetooltip.cpp:
QRect screenGeometry =
QGuiApplication
https://bugs.kde.org/show_bug.cgi?id=416010
--- Comment #3 from Milian Wolff ---
thank you!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=416010
Milian Wolff changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Latest Commit
https://bugs.kde.org/show_bug.cgi?id=369546
--- Comment #15 from Milian Wolff ---
Git commit e3883a89853ffe6456e2fb595b69bd50668f6e85 by Milian Wolff.
Committed on 20/01/2020 at 14:55.
Pushed by mwolff into branch 'master'.
Don't get confused when encountering parse errors in def
https://bugs.kde.org/show_bug.cgi?id=369546
Milian Wolff changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=412954
--- Comment #17 from Milian Wolff ---
Can you try again please?
It's quite odd, it seems as if your system compiles the test with -O2 despite
the fact that it should be compiled in Debug mode (i.e. with -O0). Anyhow, the
patch I pushed just now s
https://bugs.kde.org/show_bug.cgi?id=412954
Milian Wolff changed:
What|Removed |Added
Resolution|--- |FIXED
Latest Commit|https
https://bugs.kde.org/show_bug.cgi?id=412954
--- Comment #14 from Milian Wolff ---
I don't know mock, nor if the compiler flags are to be blamed. can you try
without mock, and without the compiler flags?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=412954
--- Comment #12 from Milian Wolff ---
FTR:
```
[root@60d1986599c5 build]# ./tests/auto/tst_inject
===
All tests passed (23 assertions in 2 test cases)
[root@60d1986599c5
https://bugs.kde.org/show_bug.cgi?id=412954
--- Comment #11 from Milian Wolff ---
Just tried it with a centos 7.7 docker image with devtools 7 - the test works
there as expected. I would say you either need to provide me with a docker
image or virtual machine to reproduce this properly, or
https://bugs.kde.org/show_bug.cgi?id=412954
--- Comment #10 from Milian Wolff ---
it helps in showing that we do setup everything correctly, but then fail to
intercept the calls to malloc etc.
that centos machine of yours - is it using 64bit or 32bit? do you have any
special devtools or other
https://bugs.kde.org/show_bug.cgi?id=412954
--- Comment #8 from Milian Wolff ---
That's very odd - could you please change the code for the test and dump the
`contents` variable to stdout?
Maybe it's some security feature in CentOS 7.7 that prevents our injector code
from working? I&
https://bugs.kde.org/show_bug.cgi?id=412954
Milian Wolff changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=414354
--- Comment #1 from Milian Wolff ---
could you please provide a patch? then I wouldn't be opposed to increase
compatibility.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=410254
Milian Wolff changed:
What|Removed |Added
CC||m...@milianw.de
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=412954
--- Comment #4 from Milian Wolff ---
try again, that should be fixed by now, cf. bug 413108
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=413108
Milian Wolff changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=412954
--- Comment #1 from Milian Wolff ---
can you try a newer version than 1.1 - i.e. latest git master - and see if it
fails there too?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=412742
Milian Wolff changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Latest Commit
https://bugs.kde.org/show_bug.cgi?id=412929
--- Comment #1 from Milian Wolff ---
I'm all for finding a way to inject frames from scripting languages in some
way, but so far I haven't gotten there. It will require some kind of API that
would then be called by ruby. Or do you have some
https://bugs.kde.org/show_bug.cgi?id=412742
--- Comment #3 from Milian Wolff ---
The pipe should be cleaned up via the trap, no?
trap cleanup EXIT
will call
rm -f "$pipe"
is that not working for you?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=409606
--- Comment #6 from Milian Wolff ---
nvm that, I forgot to init the mmap hook, it all seems to work fine actually!
thanks a lot for bringing this to my attention, I'm seriously wondering why I
never tried this out so far.
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=409606
--- Comment #5 from Milian Wolff ---
Hm yes indeed, I just tested it and I can really intercept it - awesome! I'll
definitely want to add that in the future then. I'm not yet sure how to do this
properly though, as intercepting mmap may still
https://bugs.kde.org/show_bug.cgi?id=409606
Milian Wolff changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=410107
--- Comment #2 from Milian Wolff ---
if it's a deadlock, can you get the backtrace for all threads please? to do so,
run
(gdb) thread apply all bt
thanks
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=409606
--- Comment #3 from Milian Wolff ---
but the mmap symbol in libc is just a shim that gets replaced by a symbol from
the vdso, no? and afaik you cannot intercept these via LD_PRELOAD - or am I
mistaken?
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=412630
Milian Wolff changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=412742
Milian Wolff changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=409041
--- Comment #8 from Milian Wolff ---
Hey Bernd, I hope to have finally fixed it. Can you please try it out and see
how it goes?
thanks
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=409041
Milian Wolff changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Latest Commit|https
https://bugs.kde.org/show_bug.cgi?id=409041
Milian Wolff changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=409041
Milian Wolff changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde
https://bugs.kde.org/show_bug.cgi?id=406931
Milian Wolff changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/kde
https://bugs.kde.org/show_bug.cgi?id=405221
Milian Wolff changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/kde
https://bugs.kde.org/show_bug.cgi?id=403730
--- Comment #2 from Milian Wolff ---
no :(
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=409606
--- Comment #1 from Milian Wolff ---
syscalls like mmap cannot be easily intercepted with LD_PRELOAD or similar,
which makes it quasi impossible to do with the current architecture of
heaptrack.
thankfully, you can easily use perf to achieve the same
https://bugs.kde.org/show_bug.cgi?id=408388
Milian Wolff changed:
What|Removed |Added
Resolution|--- |INTENTIONAL
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=408547
--- Comment #1 from Milian Wolff ---
odd, that's EAGAIN which isn't documented as a possible return value in
https://linux.die.net/man/2/flock
but as the error indicates, we should probably just try again? I'll try to
write a patch
https://bugs.kde.org/show_bug.cgi?id=408380
Bug ID: 408380
Summary: detect useless overrides
Product: clazy
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priori
https://bugs.kde.org/show_bug.cgi?id=407323
Bug ID: 407323
Summary: suggest fixit for clazy-range-loop
Product: clazy
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=407323
--- Comment #1 from Milian Wolff ---
Qt 5.7 is old enough by now
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=407322
Bug ID: 407322
Summary: suggest to use QRegularExpressionMatch::capturedRef
Product: clazy
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severi
https://bugs.kde.org/show_bug.cgi?id=407321
Bug ID: 407321
Summary: clazy-qvariant-template-instantiation: don't warn
about type aliases
Product: clazy
Version: unspecified
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=406865
--- Comment #2 from Milian Wolff ---
please attach a debugger in such cases, then interrupt on freeze and get us a
backtrace
alternatively, use a profiler like hotspot, then enable off-CPU profiling and
look for long freezes in the main thread
https://bugs.kde.org/show_bug.cgi?id=406847
Milian Wolff changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=406842
Milian Wolff changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=403642
--- Comment #4 from Milian Wolff ---
@Dan: works for me, thanks a lot! Please commit :)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=403642
--- Comment #2 from Milian Wolff ---
0.036 debug:
Akonadi::ResourceBase::taskDone[/home/milian/projects/kf5/src/kde/pim/akonadi/src/agentbase/resourcebase.cpp:1560]:
Akonadi::ResourceBasePrivate(0x5571174e8250) e "2 Custom startCo
https://bugs.kde.org/show_bug.cgi?id=403642
--- Comment #1 from Milian Wolff ---
0.036 debug:
Akonadi::ResourceBase::taskDone[/home/milian/projects/kf5/src/kde/pim/akonadi/src/agentbase/resourcebase.cpp:1524]:
Akonadi::ResourceBasePrivate(0x557139529a30) e "2 Custom startCo
201 - 300 of 874 matches
Mail list logo
