Bug 298995 - Crash when analysing a standard Symfony2 project
Summary: Crash when analysing a standard Symfony2 project
Status: RESOLVED FIXED
Alias: None
Product: kdevelop
Classification: Applications
Component: Language Support: PHP (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: HI crash
Target Milestone: 4.3.0
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-28 19:48 UTC by DanaKil
Modified: 2013-03-31 01:23 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
valgrind log - kdevelop opening a symfony2 project (384.74 KB, text/plain)
2012-05-07 20:05 UTC, DanaKil
Details

Note You need to log in before you can comment on or make changes to this bug.
Description DanaKil 2012-04-28 19:48:54 UTC
Symfony2 is a rather new php framework (http://symfony.com/download). When I want to import a new Symfony2 project, the analyser start its job then it systematically crashes before it can finish.

Reproducible: Always

Steps to Reproduce:
1. Download a fresh Symfony2 project (http://symfony.com/download) with vendors and unzip it
2. Open/import a project and choose the previously unzipped directory

Actual Results:  
The project should be fully analysed/parsed but it always crashes (Segmentation fault) at about 65%.

Expected Results:  
The project should be fully analysed.

I can't provide more informations because my distro can't find the debugging package for KDevelop (Kubuntu 12.06).

An other user already reported a bug about Symfony2 (https://bugs.kde.org/show_bug.cgi?id=290458 : php plugin does not provide decent support for autocompletion) but he didn't say he experienced any crashes.
Comment 1 Milian Wolff 2012-05-07 12:22:54 UTC
I just did what you said and it works like expected for me.

So I need a backtrace for the crash you experience - maybe you experience bug 275491 ?

anyhow, a reproducible test case is important for me. If you can reproduce it at will, try also to run kdevelop through valgrind and attach the log it produces:

valgrind --track-origins=yes --num-callers=25 kdevelop &> valgrind.log
Comment 2 DanaKil 2012-05-07 20:05:50 UTC
Created attachment 70935 [details]
valgrind log  - kdevelop opening a symfony2 project

valgrind --track-origins=yes --num-callers=25 kdevelop &> valgrind.log
Comment 3 DanaKil 2012-05-07 20:21:08 UTC
The bug https://bugs.kde.org/show_bug.cgi?id=275491 looks very similar to mine indeed, sorry for not finding it before posting this one. I tried to delete the .kdev4 folder but no success.

I added a valgrind log as attachement. Kdevelop ran for a few minutes then it silently closed without the usual crash reporter. In the command line from where I started valgrind/kdevelop, there was simply a "processus stopped" (not sure about the english translation).

I can't manage to install the needed debug package to produce a usable backtracke, I think I have some dependancies problems since my recent upgrade to Kubuntu 12.04. Note that it is not related because I had the same crash problem with my precious Kubuntu 11.10.
Comment 4 Milian Wolff 2012-05-30 12:18:00 UTC
the valgrind log doesn't show any apparent issue :( so I really need to get a proper backtrace with debug symbols
Comment 5 DanaKil 2013-03-31 01:23:58 UTC
Hello,
I just tried to import a Symfony2 project (an existing one with a lot of files) and the crash I reported some month ago has vanished [kubuntu 12.10]

Thank you :-)