[frameworks-ktexteditor] [Bug 385413] introduce a build option to use QtScript instead of QtQML because of #384404

https://bugs.kde.org/show_bug.cgi?id=385413 RJVB changed: What|Removed |Added Attachment #108193|0 |1 is obsolete|

[frameworks-ktexteditor] [Bug 385413] introduce a build option to use QtScript instead of QtQML because of #384404

https://bugs.kde.org/show_bug.cgi?id=385413 RJVB changed: What|Removed |Added See Also||https://bugs.kde.org/show_b

[frameworks-ktexteditor] [Bug 385413] introduce a build option to use QtScript instead of QtQML because of #384404

https://bugs.kde.org/show_bug.cgi?id=385413 --- Comment #22 from RJVB --- 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 && lineDelimiter >=

[frameworks-ktexteditor] [Bug 385413] introduce a build option to use QtScript instead of QtQML because of #384404

https://bugs.kde.org/show_bug.cgi?id=385413 --- Comment #21 from RJVB --- > 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. Probably the

[frameworks-ktexteditor] [Bug 385413] introduce a build option to use QtScript instead of QtQML because of #384404

https://bugs.kde.org/show_bug.cgi?id=385413 Rex Dieter changed: What|Removed |Added CC||rdie...@gmail.com -- You are

[frameworks-ktexteditor] [Bug 385413] introduce a build option to use QtScript instead of QtQML because of #384404

https://bugs.kde.org/show_bug.cgi?id=385413 RJVB changed: What|Removed |Added Attachment #108501|0 |1 is obsolete|

[frameworks-ktexteditor] [Bug 385413] introduce a build option to use QtScript instead of QtQML because of #384404

https://bugs.kde.org/show_bug.cgi?id=385413 --- Comment #19 from Dominik Haumann --- And now you have to add more debug("xyz...") statements in the js file to identify exactly the line of the crash. Which line in the js code crashes Qt? -- You are receiving this mail because:

[frameworks-ktexteditor] [Bug 385413] introduce a build option to use QtScript instead of QtQML because of #384404

https://bugs.kde.org/show_bug.cgi?id=385413 RJVB changed: What|Removed |Added Attachment #108500|0 |1 is obsolete|

[frameworks-ktexteditor] [Bug 385413] introduce a build option to use QtScript instead of QtQML because of #384404

https://bugs.kde.org/show_bug.cgi?id=385413 --- Comment #17 from RJVB --- 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 with debug

[frameworks-ktexteditor] [Bug 385413] introduce a build option to use QtScript instead of QtQML because of #384404

https://bugs.kde.org/show_bug.cgi?id=385413 --- Comment #16 from RJVB --- Sorry, I just haven't had time. Hopefully next week. -- You are receiving this mail because: You are watching all bug changes.

[frameworks-ktexteditor] [Bug 385413] introduce a build option to use QtScript instead of QtQML because of #384404

https://bugs.kde.org/show_bug.cgi?id=385413 --- Comment #15 from Dominik Haumann --- @Rene: Any news? As said, we don't use any Qt Quick Compiler. To drive this forward, simply copy the cstyle.js file into the respective file and add debugging output. This essentially is

[frameworks-ktexteditor] [Bug 385413] introduce a build option to use QtScript instead of QtQML because of #384404

https://bugs.kde.org/show_bug.cgi?id=385413 --- Comment #14 from Christoph Cullmann --- No, we don't use a QtQuickCompiler. -- You are receiving this mail because: You are watching all bug changes.

[frameworks-ktexteditor] [Bug 385413] introduce a build option to use QtScript instead of QtQML because of #384404

https://bugs.kde.org/show_bug.cgi?id=385413 --- Comment #13 from RJVB --- 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 afraid to

[frameworks-ktexteditor] [Bug 385413] introduce a build option to use QtScript instead of QtQML because of #384404

https://bugs.kde.org/show_bug.cgi?id=385413 --- Comment #12 from Christoph Cullmann --- > Come to think of it, maybe that in this case it's not the JIT compiler that > causes the crash, but the generator that translates the script into C++ . In > that case I'd just have to

[frameworks-ktexteditor] [Bug 385413] introduce a build option to use QtScript instead of QtQML because of #384404

https://bugs.kde.org/show_bug.cgi?id=385413 --- Comment #11 from Dominik Haumann --- The json header in the cstyle.js file itself. -- You are receiving this mail because: You are watching all bug changes.

[frameworks-ktexteditor] [Bug 385413] introduce a build option to use QtScript instead of QtQML because of #384404

https://bugs.kde.org/show_bug.cgi?id=385413 --- Comment #10 from RJVB --- (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?

[frameworks-ktexteditor] [Bug 385413] introduce a build option to use QtScript instead of QtQML because of #384404

https://bugs.kde.org/show_bug.cgi?id=385413 --- Comment #9 from RJVB --- 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.

[frameworks-ktexteditor] [Bug 385413] introduce a build option to use QtScript instead of QtQML because of #384404

https://bugs.kde.org/show_bug.cgi?id=385413 --- Comment #8 from Dominik Haumann --- See: https://docs.kde.org/trunk5/en/applications/katepart/dev-scripting.html Scripts on disk have higher priority that scripts compiled into the katepart library. That means: If you copy the

[frameworks-ktexteditor] [Bug 385413] introduce a build option to use QtScript instead of QtQML because of #384404

https://bugs.kde.org/show_bug.cgi?id=385413 --- Comment #7 from RJVB --- 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). But I

[frameworks-ktexteditor] [Bug 385413] introduce a build option to use QtScript instead of QtQML because of #384404

https://bugs.kde.org/show_bug.cgi?id=385413 --- Comment #6 from Dominik Haumann --- Rene, if you want to invest your time effectively, fix the remaining bugs in the current implementation: Look into the indentation scripts and see what line exactly crashes, and then find a

[frameworks-ktexteditor] [Bug 385413] introduce a build option to use QtScript instead of QtQML because of #384404

https://bugs.kde.org/show_bug.cgi?id=385413 --- Comment #5 from Christoph Feck --- > I don't get what's dead about QtScript that would oblige you to switch. QtScript is deprecated since Qt 5.5. It is only still included because it has some features that are not available in

[frameworks-ktexteditor] [Bug 385413] introduce a build option to use QtScript instead of QtQML because of #384404

https://bugs.kde.org/show_bug.cgi?id=385413 --- Comment #4 from RJVB --- 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 have been

[frameworks-ktexteditor] [Bug 385413] introduce a build option to use QtScript instead of QtQML because of #384404

https://bugs.kde.org/show_bug.cgi?id=385413 Christoph Cullmann changed: What|Removed |Added CC||cullm...@kde.org ---

[frameworks-ktexteditor] [Bug 385413] introduce a build option to use QtScript instead of QtQML because of #384404

https://bugs.kde.org/show_bug.cgi?id=385413 --- Comment #2 from RJVB --- 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 (in my

[frameworks-ktexteditor] [Bug 385413] introduce a build option to use QtScript instead of QtQML because of #384404

https://bugs.kde.org/show_bug.cgi?id=385413 Dominik Haumann changed: What|Removed |Added Resolution|--- |INVALID