On Tue, Feb 16, 2010 at 5:33 PM, Martin Jansa <[email protected]> wrote:
[...]
> But from my opinion, if there is some simple code, which can trigger this
> problem in
> reproducible way, then it whould be fixed in qt/app code (enabled
> optimizations are maybe hiding some nasty concurrency problem, but
> probably cannot fix the real problem).
Hi Martin, this is a very simple snippet to reproduce the problem:
main.cpp:
#include <QDomDocument>
#include <QDebug>
int main(int, char **)
{
QDomDocument dd;
QString errorMsg;
int errorLine, errorColumn;
if (dd.setContent(QString("<?xml
version=\"1.0\"?><test/>"),false,&errorMsg,&errorLine,&errorColumn))
qWarning("parse ok");
else
qWarning() << QString("Parse error: %1 line %2 column
%3").arg(errorMsg).arg(errorLine).arg(errorColumn);
}
xmltest.pro:
QT += xml
TARGET = xmltest
TEMPLATE = app
SOURCES += main.cpp
on the freerunner:
r...@om-gta02 /var/volatile/tmp $ ./xmltest
"Parse error: error occurred while parsing element line 1 column 1"
r...@om-gta02 /var/volatile/tmp $
that is the exact error in NWA.
Thanks for taking care of that.
Regards
Niko
_______________________________________________
Shr-devel mailing list
[email protected]
http://lists.shr-project.org/mailman/listinfo/shr-devel
