https://bugs.kde.org/show_bug.cgi?id=385413
RJVB <rjvber...@gmail.com> changed:
What|Removed |Added
See Also||https://bugs.kde.org/
https://bugs.kde.org/show_bug.cgi?id=385413
--- Comment #22 from RJVB <rjvber...@gmail.com> ---
Using a for instead of a while also crashes:
// var lineDelimiter = 10; // 10 limit search, hope this is a sane
value
for ( var lineDelimiter = 9 ; currentLine > 0 &&a
https://bugs.kde.org/show_bug.cgi?id=385413
--- Comment #21 from RJVB <rjvber...@gmail.com> ---
> The crashing line would be either the `if (firstPosVirtual <
> currentIndentation)` expression, or else something happens unwinding the
> stack when coming out of the while loop.
P
https://bugs.kde.org/show_bug.cgi?id=385413
RJVB <rjvber...@gmail.com> changed:
What|Removed |Added
Attachment #108501|0 |1
is ob
https://bugs.kde.org/show_bug.cgi?id=385413
RJVB <rjvber...@gmail.com> changed:
What|Removed |Added
Attachment #108500|0 |1
is ob
https://bugs.kde.org/show_bug.cgi?id=385413
--- Comment #17 from RJVB <rjvber...@gmail.com> ---
Created attachment 108500
--> https://bugs.kde.org/attachment.cgi?id=108500=edit
test cstyle.js
I had some time over my morning coffee. When using QtScript and just the stock
cstyle.js w
https://bugs.kde.org/show_bug.cgi?id=385413
--- Comment #16 from RJVB <rjvber...@gmail.com> ---
Sorry, I just haven't had time. Hopefully next week.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=385413
--- Comment #13 from RJVB <rjvber...@gmail.com> ---
Ok, so you're not doing exactly as described at
http://doc.qt.io/QtQuickCompiler/? (I only took a casual look, to me this falls
under "everything you never wanted to know but were not too af
https://bugs.kde.org/show_bug.cgi?id=385413
--- Comment #10 from RJVB <rjvber...@gmail.com> ---
(In reply to Dominik Haumann from comment #8)
> To be sure, increase the revision of the cstyle.js file in the json
> header.
Sorry, which json header would that be?
https://bugreports.
https://bugs.kde.org/show_bug.cgi?id=385953
Bug ID: 385953
Summary: reduce installed footprint?
Product: digikam
Version: 5.7.0
Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
Severity: wishlist
https://bugs.kde.org/show_bug.cgi?id=385413
--- Comment #9 from RJVB <rjvber...@gmail.com> ---
Yes, thanks. That should at least help in identifying where things go wrong.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=385413
--- Comment #7 from RJVB <rjvber...@gmail.com> ---
I agree that would be the proper approach. It's what I tried to do initially,
when I noticed that I know exactly how to trigger the crash (pretty certain I
described that in the bug I filed, too).
https://bugs.kde.org/show_bug.cgi?id=385946
Bug ID: 385946
Summary: invalid service: applications/org.kde.drkonqi.desktop
Product: drkonqi
Version: 5.11.1
Platform: Compiled Sources
OS: All
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=385413
--- Comment #4 from RJVB <rjvber...@gmail.com> ---
I agree that the code doesn't appear to be designed to swap backends easily
(like the rendering backend in KDevelop's documentation feature, for instance).
It looks like the transition could hav
https://bugs.kde.org/show_bug.cgi?id=385413
--- Comment #2 from RJVB <rjvber...@gmail.com> ---
Exactly what's being fixed (and where)? If there's a fix for the upstream bug
that doesn't involve doing the impossible I'd love to know it.
Keeping the old code afloat isn't an option
https://bugs.kde.org/show_bug.cgi?id=385883
RJVB <rjvber...@gmail.com> changed:
What|Removed |Added
Resolution|INVALID |UPSTREAM
--- Comment #4 fro
https://bugs.kde.org/show_bug.cgi?id=385883
--- Comment #2 from RJVB <rjvber...@gmail.com> ---
How is that a library bug? You may not agree with the design principle, but
it's nothing new that not all headers are always self-sufficient. There's no
bug in the sense that testGbmSurface com
https://bugs.kde.org/show_bug.cgi?id=385883
Bug ID: 385883
Summary: KWin5 trivial build failure against gbm 10.1.3
Product: kwin
Version: 5.11.1
Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=385869
Bug ID: 385869
Summary: DrKonqi connects to obsolete signal user1Clicked
Product: drkonqi
Version: unspecified
Platform: Compiled Sources
OS: All
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=385640
--- Comment #9 from RJVB <rjvber...@gmail.com> ---
>
> https://woboq.com/blog/nice-debug-output-with-qt.html -- grep for
> "backtrace" -- you can enable them for e.g. warnings exclusively.
It turns out that seting QT_MESSAGE_
https://bugs.kde.org/show_bug.cgi?id=385848
--- Comment #2 from RJVB <rjvber...@gmail.com> ---
This output from the calling terminal may hint at what happened:
virtual KDevelop::IAssistant::Ptr
UnknownDeclarationProblem::solutionAssistant() const scanThread seems to have
outlived its usef
https://bugs.kde.org/show_bug.cgi?id=385848
RJVB <rjvber...@gmail.com> changed:
What|Removed |Added
Version|unspecified |5.1.80
--
You are rec
https://bugs.kde.org/show_bug.cgi?id=385848
--- Comment #1 from RJVB <rjvber...@gmail.com> ---
(Oops, DrKonqi manipulation error)
It looks like the actual crash happened in ContextBrowserView::isLocked() but
that the reason is the delivery of a pending event to a view after it was
d
-40-g35f3f710c0)
(Compiled from sources)
Qt Version: 5.8.0
Frameworks Version: 5.38.0
Operating System: Linux 4.9.30-ck1-mainline-core2-rjvb x86_64
Distribution: Ubuntu 14.04.5 LTS
-- Information about the crash:
- What I was doing when the application crashed:
I closed a session containing
https://bugs.kde.org/show_bug.cgi?id=385803
Bug ID: 385803
Summary: parser often leaves echos of previous syntax errors
Product: kdevelop
Version: 5.1.80
Platform: Compiled Sources
OS: All
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=385703
Bug ID: 385703
Summary: QtWebengine documentatio viewer causes KDevelop crash
on exit
Product: kdevelop
Version: 5.1.80
Platform: Compiled Sources
OS: OS X
https://bugs.kde.org/show_bug.cgi?id=385640
--- Comment #8 from RJVB <rjvber...@gmail.com> ---
> What's the problem with running it under GDB?
Nothing, except that it takes minutes just to get the app to start (lldb is a
bit faster on my Mac) and it takes up gobs of additional RAM.
https://bugs.kde.org/show_bug.cgi?id=385640
--- Comment #7 from RJVB <rjvber...@gmail.com> ---
(In reply to Kevin Funk from comment #6)
> Yes. It told me you haven't fully understood the problem
I've understood (accepted) that the complexity of the plugin/toolview
architecture is in l
https://bugs.kde.org/show_bug.cgi?id=385640
--- Comment #5 from RJVB <rjvber...@gmail.com> ---
Created attachment 108328
--> https://bugs.kde.org/attachment.cgi?id=108328=edit
debugging patch
I'll be running with this myself (in hope it's safe to call KMessageBox when
this iss
https://bugs.kde.org/show_bug.cgi?id=385640
--- Comment #4 from RJVB <rjvber...@gmail.com> ---
(In reply to Kevin Funk from comment #2)
> Note: I can't reproduce your problem.
Could you please add something like this, at least? (Or use an ASSERT if you
run with those
https://bugs.kde.org/show_bug.cgi?id=385640
--- Comment #3 from RJVB <rjvber...@gmail.com> ---
Have you read the ticket and commit message? I cannot reproduce the issue at
will either. It happens and *will* (always?) provoke a crash, but it does so
seemingly randomly.
If you want to ru
https://bugs.kde.org/show_bug.cgi?id=385640
RJVB <rjvber...@gmail.com> changed:
What|Removed |Added
Latest Commit||https://commits.kde.o
https://bugs.kde.org/show_bug.cgi?id=385640
RJVB <rjvber...@gmail.com> changed:
What|Removed |Added
Version|unspecified |5.1.80
--
You are rec
https://bugs.kde.org/show_bug.cgi?id=385640
RJVB <rjvber...@gmail.com> changed:
What|Removed |Added
See Also||https://bugs.kde.org/
https://bugs.kde.org/show_bug.cgi?id=385556
RJVB <rjvber...@gmail.com> changed:
What|Removed |Added
See Also||https://bugs.kde.org/
: 5.8.0
Frameworks Version: 5.38.0
Operating System: Linux 4.9.30-ck1-mainline-core2-rjvb x86_64
Distribution: Ubuntu 14.04.5 LTS
-- Information about the crash:
- What I was doing when the application crashed:
I had been dragging the documentation toolview window to and from the dock to
study how
https://bugs.kde.org/show_bug.cgi?id=385556
--- Comment #4 from RJVB <rjvber...@gmail.com> ---
One more observation, and this one is reproducible on Mac AND Linux:
1. Add the "Documentation" toolview to a toolbar (no need to open and use it).
Close the documentation toolview i
https://bugs.kde.org/show_bug.cgi?id=385556
RJVB <rjvber...@gmail.com> changed:
What|Removed |Added
Status|NEEDSINFO |UNCONFIRMED
Reso
https://bugs.kde.org/show_bug.cgi?id=385556
--- Comment #2 from RJVB <rjvber...@gmail.com> ---
Sadly I have no idea how to reproduce the issue. What I think happens is this:
- I undocked the documentation window in one of my sessions sometime in the
past
and there are two related iss
https://bugs.kde.org/show_bug.cgi?id=385556
RJVB <rjvber...@gmail.com> changed:
What|Removed |Added
Summary|documentation viewer|documentation viewer
https://bugs.kde.org/show_bug.cgi?id=385556
Bug ID: 385556
Summary: documentation viewer docking behaviour
Product: kdevelop
Version: 5.1.80
Platform: Compiled Sources
OS: OS X
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=385460
Bug ID: 385460
Summary: outline dropdown widget shows duplicate entries
Product: kdevelop
Version: git master
Platform: Compiled Sources
OS: All
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=385434
--- Comment #1 from RJVB <rjvber...@gmail.com> ---
Probe output (extract):
kdevplatform.documentation: QWidget::setTabOrder() called in
DocumentationView(0x7fdb3adaf6c0) with widgets from different windows
QLineEdit(0x7fdb36585af0) QTr
https://bugs.kde.org/show_bug.cgi?id=385450
Bug ID: 385450
Summary: requested ticket with simulated release version
Product: kdevelop
Version: 5.1.2
Platform: Compiled Sources
OS: All
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=385450
RJVB <rjvber...@gmail.com> changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Reso
https://bugs.kde.org/show_bug.cgi?id=384404
--- Comment #16 from RJVB <rjvber...@gmail.com> ---
OK, so 184564 alone is not a fix. And applying all patches from the 5.8 branch
head breaks the build at least in the aggregate source tree. Something about a
change related to qml
https://bugs.kde.org/show_bug.cgi?id=384404
--- Comment #15 from RJVB <rjvber...@gmail.com> ---
It certainly looks promising, but what makes you think it's related?
Anyway, I'll try 5.8/head (i.e. all patches from v5.8.0..HEAD) and see what
comes out of that. I already tried to cherry-pic
https://bugs.kde.org/show_bug.cgi?id=385398
--- Comment #7 from RJVB <rjvber...@gmail.com> ---
No, I haven't, it's a conclusion drawn on the linked bug report (384404)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=385439
Bug ID: 385439
Summary: "Failed to parse translation unit: " errors for
inexistant files
Product: kdevelop
Version: git master
Platform: Compiled Sources
OS: All
https://bugs.kde.org/show_bug.cgi?id=385434
Bug ID: 385434
Summary: QWidget::setTabOrder called incorrectly(?)
Product: kdevelop
Version: git master
Platform: Compiled Sources
OS: All
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=385392
--- Comment #7 from RJVB <rjvber...@gmail.com> ---
Touching wood, but you seem to have resolved this. I had a hunch it had to be
something very simple.
I haven't tried to restore the toolview to my toolbars yet to see if the view
no longer r
https://bugs.kde.org/show_bug.cgi?id=384404
--- Comment #13 from RJVB <rjvber...@gmail.com> ---
For anyone else affected by this: I've attached a patch that reverts
KTextEditor to use QtScript here: https://bugs.kde.org/show_bug.cgi?id=385413 .
Tweaking the function that triggers the bug
https://bugs.kde.org/show_bug.cgi?id=385413
Bug ID: 385413
Summary: introduce a build option to use QtScript instead of
QtQML because of #384404
Product: frameworks-ktexteditor
Version: unspecified
Platform: Compiled
https://bugs.kde.org/show_bug.cgi?id=385398
--- Comment #5 from RJVB <rjvber...@gmail.com> ---
Yeah, that was my null hypothesis too, but I was kind of hoping it'd be wrong.
This irks me, I cannot help but feel that it ought to be possible to tweak the
"incriminated"
https://bugs.kde.org/show_bug.cgi?id=385398
RJVB <rjvber...@gmail.com> changed:
What|Removed |Added
OS|OS X|All
Product|kd
https://bugs.kde.org/show_bug.cgi?id=385398
--- Comment #3 from RJVB <rjvber...@gmail.com> ---
OK, now I'm curious. The stack backtrace in 384404 doesn't look like the one I
get at all, at least not the part in QtQML. How can you know it's the same bug?
It'd be extremely nice if ther
https://bugs.kde.org/show_bug.cgi?id=385392
--- Comment #5 from RJVB <rjvber...@gmail.com> ---
Yes, most other plugins don't behave that way. Two that do are the debugger
plugins; they also have the habit of restoring their toolbar. In their case
it's more hit-and-run, indicating that
https://bugs.kde.org/show_bug.cgi?id=384404
--- Comment #12 from RJVB <rjvber...@gmail.com> ---
Ouch, I'm stuck on Qt 5.8 for the time being. Do we know anything that would
allow backporting the fix from 5.9?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=385398
--- Comment #1 from RJVB <rjvber...@gmail.com> ---
Turns out this is reproducible:
- Use the proposed "recover data" feature after reopening the session and
parsing stopped.
- hit enter after the new line
The
https://bugs.kde.org/show_bug.cgi?id=385398
Bug ID: 385398
Summary: kdevelop : crash after hitting enter in code editor
Product: kdevelop
Version: unspecified
Platform: Compiled Sources
OS: OS X
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=385392
--- Comment #3 from RJVB <rjvber...@gmail.com> ---
The venom is in this hunk, the other appears to be without negative
side-effects:
diff --git kdevplatform/shell/documentationcontroller.cpp
kdevplatform/shell/documentationcontroller.cpp
https://bugs.kde.org/show_bug.cgi?id=385392
--- Comment #2 from RJVB <rjvber...@gmail.com> ---
Created attachment 108181
--> https://bugs.kde.org/attachment.cgi?id=108181=edit
sessionrc config file
FWIW, I get this in all my sessions.
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=385392
--- Comment #1 from RJVB <rjvber...@gmail.com> ---
Created attachment 108180
--> https://bugs.kde.org/attachment.cgi?id=108180=edit
session's 2nd project config
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=385392
Bug ID: 385392
Summary: documentationview regression: now imposes itself all
the time
Product: kdevelop
Version: unspecified
Platform: Compiled Sources
OS: All
https://bugs.kde.org/show_bug.cgi?id=383875
RJVB <rjvber...@gmail.com> changed:
What|Removed |Added
CC||rjvber...@gmail.com
--- Comm
https://bugs.kde.org/show_bug.cgi?id=384724
--- Comment #4 from RJVB <rjvber...@gmail.com> ---
I beg to differ. It makes no sense to warn about unhandled cmake server
messages for the majority of users (basically everyone not working on cmake
server support). They're only useful when deb
https://bugs.kde.org/show_bug.cgi?id=385288
--- Comment #7 from RJVB <rjvber...@gmail.com> ---
OK. I would have hoped that it's a question of 1 or 2 magic calls at the right
spot, but you're right. This is exactly the sort of thing that might take
junior a sizeable amount of time to get
https://bugs.kde.org/show_bug.cgi?id=385333
Bug ID: 385333
Summary: kdevelop: crash in recursive(?) cmake invocation
Product: kdevelop
Version: unspecified
Platform: Compiled Sources
OS: OS X
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=384724
--- Comment #1 from RJVB <rjvber...@gmail.com> ---
A new spammy bit which doesn't print anything understandable or of interest,
introduced by #11bc71c1 :
diff --git a/plugins/cmake/cmakeutils.cpp b/plugins/cmake/cmakeutils.cpp
https://bugs.kde.org/show_bug.cgi?id=385228
--- Comment #5 from RJVB <rjvber...@gmail.com> ---
I thought you were referring to the open document tabswitcher (Ctrl+Tab) but
that one also doesn't reflect the tab order reliably.
And as far as the open documents drop-down menu is concerned: s
https://bugs.kde.org/show_bug.cgi?id=385288
--- Comment #5 from RJVB <rjvber...@gmail.com> ---
I'm not trying to imply anything. Labelling a fix as a junior job suggests that
it'll be more work to come up with one than I'd have thought (and hoped).
--
You are receiving this mail becaus
https://bugs.kde.org/show_bug.cgi?id=385288
--- Comment #3 from RJVB <rjvber...@gmail.com> ---
Junior job? Will it be that much work to fix this?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=385288
--- Comment #2 from RJVB <rjvber...@gmail.com> ---
Created attachment 108126
--> https://bugs.kde.org/attachment.cgi?id=108126=edit
screenshot of the dialog taken with the "window under cursor" option
That image is 13933 pi
https://bugs.kde.org/show_bug.cgi?id=385288
--- Comment #1 from RJVB <rjvber...@gmail.com> ---
Comment on attachment 108125
--> https://bugs.kde.org/attachment.cgi?id=108125
cmake import wizard width issue
That image is a screenshot spanning the entire width of my screen.
https://bugs.kde.org/show_bug.cgi?id=385288
Bug ID: 385288
Summary: oversized cmakebuilddir dialog (width)
Product: kdevelop
Version: git master
Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=385228
RJVB <rjvber...@gmail.com> changed:
What|Removed |Added
Severity|wishlist|normal
--- Comment #4 fro
https://bugs.kde.org/show_bug.cgi?id=385228
RJVB <rjvber...@gmail.com> changed:
What|Removed |Added
Severity|normal |wishlist
--- Comment #2 fro
https://bugs.kde.org/show_bug.cgi?id=385228
Bug ID: 385228
Summary: alphanumerical vs. unsorted ordering in outline
navigator and open file dropdown menu
Product: kdevelop
Version: git master
Platform: Compiled Sources
https://bugs.kde.org/show_bug.cgi?id=385217
--- Comment #1 from RJVB <rjvber...@gmail.com> ---
Or worse:
void AbstractFileManagerPlugin::addDirToWatcher( void
KDevelop::AbstractFileManagerPlugin::addDirToWatcher(KDevelop::ProjectWatcher*
watcher, const QString& path)
I had t
https://bugs.kde.org/show_bug.cgi?id=385217
Bug ID: 385217
Summary: code completion gives foo:foo::foo() instead of
foo:foo()
Product: kdevelop
Version: git master
Platform: Compiled Sources
OS: All
https://bugs.kde.org/show_bug.cgi?id=385110
--- Comment #3 from RJVB <rjvber...@gmail.com> ---
Any chance this is related to the situation where you start to add
"classname::" in front of a function name, you use completion and find the
function name has been eaten? I don't know
https://bugs.kde.org/show_bug.cgi?id=385110
--- Comment #1 from RJVB <rjvber...@gmail.com> ---
Created attachment 108049
--> https://bugs.kde.org/attachment.cgi?id=108049=edit
after accepting the 1st proposition
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=385110
Bug ID: 385110
Summary: code completion adds semicolon after opening brace
(function argument list)
Product: kdevelop
Version: unspecified
Platform: Compiled Sources
https://bugs.kde.org/show_bug.cgi?id=384880
--- Comment #15 from RJVB <rjvber...@gmail.com> ---
FWIW, none of my former employers (national scientific research institutions)
would buy software from vendors with that kind of attitude.
I'll propose the approach upstream and probably the lo
https://bugs.kde.org/show_bug.cgi?id=384880
--- Comment #12 from RJVB <rjvber...@gmail.com> ---
> Why not push that into KDirWatch to get the efficient lookup everywhere, not
> just in KDevelop?
And then what, let everyone who doesn't have the latest frameworks version
stick
https://bugs.kde.org/show_bug.cgi?id=385064
Bug ID: 385064
Summary: KDevelop crash when clicking "Show documentation for"
in the code context browser
Product: kdevelop
Version: unspecified
Platform: Compiled Sources
https://bugs.kde.org/show_bug.cgi?id=384880
RJVB <rjvber...@gmail.com> changed:
What|Removed |Added
Attachment #108017|0 |1
is ob
https://bugs.kde.org/show_bug.cgi?id=384880
--- Comment #9 from RJVB <rjvber...@gmail.com> ---
Created attachment 108017
--> https://bugs.kde.org/attachment.cgi?id=108017=edit
on-demand set-up of dir-only dirwatching
This is a PoC implementation of my idea of deferring the dirwatche
https://bugs.kde.org/show_bug.cgi?id=384885
RJVB <rjvber...@gmail.com> changed:
What|Removed |Added
CC||ap...@gmx.de
--
You are rec
https://bugs.kde.org/show_bug.cgi?id=384885
--- Comment #5 from RJVB <rjvber...@gmail.com> ---
The only explanation I can find is that the compiler (clang 4.0.1) miscompiles
the svncpp code in KDevelop (but not the comparable code in kdesvn, from which
I copied certain things for t
https://bugs.kde.org/show_bug.cgi?id=385012
Bug ID: 385012
Summary: counterproductivity: semantic analysis issues preempt
code context popups
Product: kdevelop
Version: git master
Platform: Compiled Sources
https://bugs.kde.org/show_bug.cgi?id=384990
Bug ID: 384990
Summary: CMake: action to build mac files and auto-generated
headers
Product: kdevelop
Version: git master
Platform: Compiled Sources
OS: All
https://bugs.kde.org/show_bug.cgi?id=384885
--- Comment #4 from RJVB <rjvber...@gmail.com> ---
It really *is* a freak crash.
The code behaves as if the call to `apr_pool_initialize()` is never actually
made in `svn::pool_create()`. I can assign the function's return to a variable
and
https://bugs.kde.org/show_bug.cgi?id=384899
--- Comment #5 from RJVB <rjvber...@gmail.com> ---
Created attachment 107957
--> https://bugs.kde.org/attachment.cgi?id=107957=edit
untrolling patch
I have been meaning to rewind some of your changes one by one to see what could
be a good c
https://bugs.kde.org/show_bug.cgi?id=384955
Bug ID: 384955
Summary: project naming
Product: kdevelop
Version: git master
Platform: Compiled Sources
OS: All
Status: UNCONFIRMED
Severity: wishlist
https://bugs.kde.org/show_bug.cgi?id=384885
--- Comment #3 from RJVB <rjvber...@gmail.com> ---
Here's what happens: apr_pool_create_ex is called with NULL parent and
allocator, leading to a nullptr dereference:
* thread #1: tid = 0x1c6e93b, 0x00012bde307f
libapr-1.0.dylib`apr_pool_cre
https://bugs.kde.org/show_bug.cgi?id=384775
--- Comment #7 from RJVB <rjvber...@gmail.com> ---
This was committed to the 5.2 branch too, from the looks of it?
If so I have to disappoint: the reported issues with e.g. cmakeutils.cpp and
cmakepreferences.cpp persist. These notable (from a M
https://bugs.kde.org/show_bug.cgi?id=384880
--- Comment #8 from RJVB <rjvber...@gmail.com> ---
Either way, KDirWatch *is* that old. Most code in it was last touched during a
Jenkins commit in 2013 (transition to KF5?). Some work has been done on it
recently but still it too checks each and
https://bugs.kde.org/show_bug.cgi?id=384899
Bug ID: 384899
Summary: find/replace key persistence causes find/replace
toolview "trolling"
Product: kdevplatform
Version: git master
Platform: Compiled Sources
https://bugs.kde.org/show_bug.cgi?id=384885
--- Comment #2 from RJVB <rjvber...@gmail.com> ---
Apparently it's related to the QMake project manager. Loading a qmake-based
project into an already running session triggers the crash.
--
You are receiving this mail because:
You are watching a
601 - 700 of 1337 matches
Mail list logo
