Summary: | kdevelop-4.1/PHP Crashs after starting up ( while scanning the files ) and Copy&Paste Content (3Lines..) | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | Tobias Hochgürtel <tobias.hochguertel> |
Component: | general | Assignee: | kdevelop-bugs-null |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | tobias.hochguertel |
Priority: | NOR | Keywords: | investigated, triaged |
Version: | 4.1.60 | ||
Target Milestone: | 4.2.0 | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Tobias Hochgürtel
2010-11-17 13:02:54 UTC
Created attachment 53488 [details]
New crash information added by DrKonqi
kdevelop (4.1.60) on KDE Platform 4.5.3 (KDE 4.5.3) using Qt 4.6.3
- What I was doing when the application crashed:
Parser was finished. And U have created an New File. (works fine) Then I copy three require_once()-lines (works fine) and then I want paste them in my New File (kdevelop4.1 crashs)
-- Backtrace (Reduced):
#7 0x00007f5c86e65e54 in Php::ExpressionVisitor::visitEncapsVar(Php::EncapsVarAst*) () from /usr/lib/libkdev4phpduchain.so
#8 0x00007f5c86c04f1d in Php::DefaultVisitor::visitEncapsList(Php::EncapsListAst*) () from /usr/lib/libkdev4phpparser.so
#9 0x00007f5c86e6274e in Php::ExpressionVisitor::visitScalar(Php::ScalarAst*) () from /usr/lib/libkdev4phpduchain.so
#10 0x00007f5c86c06167 in Php::DefaultVisitor::visitVarExpressionNormal(Php::VarExpressionNormalAst*) () from /usr/lib/libkdev4phpparser.so
#11 0x00007f5c86e63481 in Php::ExpressionVisitor::visitVarExpressionNormal(Php::VarExpressionNormalAst*) () from /usr/lib/libkdev4phpduchain.so
Kdevelop 4.1. doesn't crashed when I was Adding the Lines from Outside ( kate ) while having the same file opend in kdevelop and kate. Ater changing back to kdevelop and looking to the file which has changed, I get the Information and can push F5 for reaload and kevelop doesn't crash.I don't know if this information will help. please write down the exact steps to reproduce, esp. the sources you input. Also you might want to decrease the number of parsing threads, experience shows that more than two is simply not helping (sadly!) in KDevelop due to technical difficulties. Also, better debug symbols would be helping (with line numbers etc.), though not neccessarily required. For starters you could run KDevelop through valgrind and show me the log it produces when reproducing the issue: valgrind --track-origins=yes --num-callers=25 kdevelop Thanks waiting for information Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |