mac test report
Николай Шафоростов
shafff at ukr.net
Fri Sep 17 06:48:09 UTC 2010
Hi. As I wrote in http://shaforostoff.blogspot.com/2010/09/kde-on-mac-test-report.html
i encountered a crash in KDevelop. Today could eliminate it by rewritting computeGccStandardMacros() in languages/cpp/setuphelpers.cpp
to use QProcess instead of KProcess. Otherwise it crashes with very strange backtrace, that includes KTarArchive class methods as well as QProcess::waitForFinished
I have compiled KDevelop 1.0.2 against kdelibs 4.5.1.
First lines of the function (all my changes):
QVector<rpp::pp_macro*> computeGccStandardMacros()
{
QVector<rpp::pp_macro*> ret;
//Get standard macros from gcc
QProcess proc;
proc.setTextModeEnabled(true);
proc.setProcessChannelMode(QProcess::MergedChannels);
// The output of the following gcc commands is several line in the format:
// "#define MACRO [definition]", where definition may or may not be present.
// Parsing each line sequentially, we can easily build the macro set.
QStringList args;
args << "-xc++" <<"-E" <<"-dM" <<"/dev/null";
proc.start("gcc", args);
if (proc.waitForFinished(500) == 0) {
Now I can import a Makefile-based project into KDevelop, but when I open .cpp files in it they don't get syntax-highlighted.
I attach the terminal output of the KDevelop process.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: output.bz2
Type: application/bzip2
Size: 4145 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20100917/17dfabca/attachment.bin>
More information about the KDevelop-devel
mailing list