Bug 376955 - Segmentation fault when opening project configuration
Summary: Segmentation fault when opening project configuration
Status: RESOLVED DUPLICATE of bug 374525
Alias: None
Product: kdevelop
Classification: Applications
Component: general (show other bugs)
Version: 5.0.80
Platform: Appimage Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-26 14:41 UTC by Richard Gladman
Modified: 2017-03-30 09:12 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.1.0
Sentry Crash Report:

Attachments
Output from running kdevelop from terminal (11.62 KB, text/plain)
2017-02-26 14:41 UTC, Richard Gladman 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Richard Gladman 2017-02-26 14:41:38 UTC 
Created attachment 104234 [details]
Output from running kdevelop from terminal

OS: openSUSE Tumbleweed
Plasma: 5.9.2
KDE Frameworks: 5.30.0
Qt: 5.7.1

To reproduce:

Start KDevelop
Project -> New from template
Python -> Simple python application

Fill in the name and path, select git version management and create the project

Highlight the project
Go to Project -> Open Configuration

Segmentation Fault

This also happens when right clicking the project and selecting Open Configuration
Comment 1 Sven Brauch 2017-02-26 15:42:49 UTC 
Backtrace please.
Comment 2 Richard Gladman 2017-02-26 15:54:08 UTC 
(In reply to Sven Brauch from comment #1)
> Backtrace please.

I'm not sure how. 

Often when an application crashes, an error handler pops up that helps generate a back trace etc. In this case that is not happening.
Comment 3 Sven Brauch 2017-02-26 22:33:21 UTC 
Ah ok, just run kdevelop in gdb by hand:
 # gdb kdevelop
 > run
Then when it crashes, generate the backtrace by typing
 > thread apply all bt

Greetings, Sven
Comment 4 Richard Gladman 2017-02-27 00:11:56 UTC 
$ > gdb ./KDevelop-5.0.80-x86_64.AppImage                                                                                                                                    
GNU gdb (GDB; openSUSE Tumbleweed) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-suse-linux".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://bugs.opensuse.org/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./KDevelop-5.0.80-x86_64.AppImage...(no debugging symbols found)...done.
(gdb)

I can't find anything that look likes debugging symbols for the appimage. I'll look at building from source on the morning.
Comment 5 Sven Brauch 2017-02-27 07:53:47 UTC 
Ah, sorry, somehow I overlooked that you used 5.0.80 -- with the AppImage, I can reproduce the problem. I can generate the trace myself then, no need for you to do that. Thanks!
Comment 6 Francis Herne 2017-03-30 09:12:59 UTC 
The Python project template uses the generic manager; the cppcheck plugin would crash when this was used.

*** This bug has been marked as a duplicate of bug 374525 ***