On 23/04/2014, at 7:32 AM, Burkhard Lück wrote:
Am Mittwoch, 23. April 2014, 06:55:23 schrieb Ian Wadham:
On 20/04/2014, at 6:12 PM, Burkhard Lück wrote:
Am Sonntag, 20. April 2014, 16:41:35 schrieb Ian Wadham:
Well, that is news to me. I never knew before that all the KDE Handbooks
are on
On 20/04/2014, at 6:12 PM, Burkhard Lück wrote:
Am Sonntag, 20. April 2014, 16:41:35 schrieb Ian Wadham:
Well, that is news to me. I never knew before that all the KDE Handbooks are
on the web now. What about translations?
Am Mittwoch, 23. April 2014, 06:55:23 schrieb Ian Wadham:
On 20/04/2014, at 6:12 PM, Burkhard Lück wrote:
Am Sonntag, 20. April 2014, 16:41:35 schrieb Ian Wadham:
Well, that is news to me. I never knew before that all the KDE Handbooks
are on the web now. What about translations?
Am Sonntag, 20. April 2014, 16:41:35 schrieb Ian Wadham:
Well, that is news to me. I never knew before that all the KDE Handbooks are
on the web now. What about translations?
http://docs.kde.org/development/de/kdegames/palapeli/large-puzzle-holders.html
--
Burkhard Lück
Visit
On 18/04/2014, at 4:32 AM, Luigi Toscano wrote:
Ian Wadham ha scritto:
Hello Thomas and Luigi,
Sorry it has been such a while since you wrote. A lot of water has
flowed under the bridge since then, but this issue is still of the utmost
importance to MacPorts. See:
On 18/04/2014, at 4:58 AM, Thomas Lübking wrote:
On Donnerstag, 17. April 2014 20:32:17 CEST, Luigi Toscano wrote:
Ian Wadham ha scritto:
Sorry it has been such a while since you wrote. A lot of water has
flowed under the bridge since then, but this issue is still of the utmost
importance
Hello Thomas and Luigi,
Sorry it has been such a while since you wrote. A lot of water has
flowed under the bridge since then, but this issue is still of the utmost
importance to MacPorts. See:
https://trac.macports.org/wiki/KDEProblems/KDETickets
On 21/03/2014, at 11:52 PM, Thomas Lübking
Ian Wadham ha scritto:
Hello Thomas and Luigi,
Sorry it has been such a while since you wrote. A lot of water has
flowed under the bridge since then, but this issue is still of the utmost
importance to MacPorts. See:
https://trac.macports.org/wiki/KDEProblems/KDETickets
On
On Donnerstag, 17. April 2014 20:32:17 CEST, Luigi Toscano wrote:
Ian Wadham ha scritto:
Sorry it has been such a while since you wrote. A lot of water has
flowed under the bridge since then, but this issue is still of the utmost
importance to MacPorts. See:
On 20/03/2014, at 7:28 AM, mk-li...@email.de wrote:
On 19 Mar 2014, at 06:29 , Thomas Lübking thomas.luebk...@gmail.com wrote:
There seems a known issue reg. multithreaded libxml2 [1], but since Marko
was the reporter, i simply ruled it out being the remaining one.
I doubt it was a libxml2
On Freitag, 21. März 2014 08:24:06 CEST, Ian Wadham wrote:
That call to KGlobal::locale(); seems an odd one, KDE guys.
That function is supposed to
return a locale (KLocale *), but here it is executed as a
procedure, ignoring the return
result. I can only conclude that the code is being
On 19/03/2014, at 4:29 PM, Thomas Lübking wrote:
YY
H H YYY
H H PP PP YYY YYY
HHH HHH PPPPP YYY
On 19 Mar 2014, at 06:29 , Thomas Lübking thomas.luebk...@gmail.com wrote:
There seems a known issue reg. multithreaded libxml2 [1], but since Marko was
the reporter, i simply ruled it out being the remaining one.
I doubt it was a libxml2 issue, since the corresponding poster wrote
—
pHi on
mk-li...@email.de ha scritto:
On 19 Mar 2014, at 06:29 , Thomas Lübking thomas.luebk...@gmail.com wrote:
There seems a known issue reg. multithreaded libxml2 [1], but since Marko
was the reporter, i simply ruled it out being the remaining one.
I doubt it was a libxml2 issue, since the
On 19 Mar 2014, at 21:50 , Luigi Toscano luigi.tosc...@tiscali.it wrote:
The crash described in that stack trace happens in a part of code which is
executed *before* initializing livxml.
OK, and what do we learn from that?
Greets,
Marko
Visit
On 19 Mar 2014, at 22:30 , Thomas Lübking thomas.luebk...@gmail.com wrote:
That the libxml2 bug is not related to the bug #261509 backtrace (doesn't
change anything since i anticipated that for social reasons ;-)
Ah, ok, so that supports the notion that it was just an accidental coincidence.
On Mittwoch, 19. März 2014 22:24:13 CEST, mk-li...@email.de wrote:
On 19 Mar 2014, at 21:50 , Luigi Toscano luigi.tosc...@tiscali.it wrote:
The crash described in that stack trace happens in a part of code which is
executed *before* initializing livxml.
OK, and what do we learn from that?
On 20/03/2014, at 8:34 AM, mk-li...@email.de wrote:
On 19 Mar 2014, at 22:30 , Thomas Lübking thomas.luebk...@gmail.com wrote:
That the libxml2 bug is not related to the bug #261509 backtrace (doesn't
change anything since i anticipated that for social reasons ;-)
Ah, ok, so that supports
On Tuesday 18 of March 2014 15:09:08 Ian Wadham wrote:
Hi Luigi,
On 18/03/2014, at 10:17 AM, Luigi Toscano wrote:
I'm pretty sure meinproc4 does not depend on anything tex-related. It
depends on libxml, libxslt, docbook-xml and docbook-xslt. Could you
please try to investigate a bit more
Hi Luigi,
On 18 Mar 2014, at 14:33 , Luigi Toscano luigi.tosc...@tiscali.it wrote:
I wonder why it happens only here and not in other applications; the crash is
in a innocent call to KGlobal. Do you know about similar crashes/stacktraces
in other applications?
I don’t know whether this
Ages ago I was hunting a but in KDE’s about dialog and had set up a Mercurial
repo for it on BitBucket [1].
One could use that location for the minor app which you’re suggesting.
[1] https://bitbucket.org/mkae/kde-tests
Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe
As shown in [1] I’ve got a working native KDE tutorial application started.
So, now one could add whatever code you think is needed to test the issue
observed with meinproc4.
[1] http://mail.kde.org/pipermail/kdevelop/2014-March/018258.html
Visit
mk-li...@email.de wrote:
Hi Luigi,
On 18 Mar 2014, at 14:33 , Luigi Toscano luigi.tosc...@tiscali.it wrote:
I wonder why it happens only here and not in other applications; the crash
is
in a innocent call to KGlobal. Do you know about similar crashes/stacktraces
in other applications?
On 18 Mar 2014, at 23:15 , Luigi Toscano luigi.tosc...@tiscali.it wrote:
Ok: I've seen the other message, but then I would start from this and make
sure that the stacktrace is the correct one.
Hmm…
Could you (or any other Mac user/developer) please try to
- recompile kdelibs with debug
Luigi, before I am off for tonight I verified that I can start meinproc4 with
lldb. Works.
All I’d need now would be big and complex files to work on.
Without doing any building of any port I’d want to just steal some XML/XSL
source files perhaps from KDELIBS and let meinproc4 work on them in
Thomas Lübking wrote:
On Dienstag, 18. März 2014 23:26:34 CEST, mk-li...@email.de wrote:
On 18 Mar 2014, at 23:15 , Luigi Toscano luigi.tosc...@tiscali.it wrote:
Ok: I've seen the other message, but then I would start from this and make
sure that the stacktrace is the correct one.
Hmm…
So, I got all *.docbook files coming with kdelibs4 and copied them into a test
directory and wrote a bash script which calls meinproc4 for every of those
files.
Of course there are now tons of warning because I obviously don’t have some
needed files in certain directories which meinproc4 needs…
Hi Thomas,
thanks for that clarification with code! :-)
OK, now I see what you mean.
I still wonder how and where you found this str == NULL” issue…
I must have seen some other stack trace then. Which one are you referring to,
actually?
Greets,
Marko (who is now eventually truly off for
28 matches
Mail list logo
