Bug 407385 - Crash after Segmentation Fault when opening clang CMake project
Summary: Crash after Segmentation Fault when opening clang CMake project
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: kdevelop
Classification: Applications
Component: Language Support: CPP (Clang-based) (show other bugs)
Version: 5.3.1
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-10 08:38 UTC by Stefan Laufmann
Modified: 2019-05-10 11:50 UTC (History)
0 users

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


Attachments
trace of gdb (run and bt) (59.64 KB, text/x-log)
2019-05-10 08:40 UTC, Stefan Laufmann
Details
zipped log of running kdevelop in console (543.09 KB, application/gzip)
2019-05-10 08:43 UTC, Stefan Laufmann
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Laufmann 2019-05-10 08:38:47 UTC
Kdevelop crashes with a Segmentation Fault on opening the clang CMake codebase.

STEPS TO REPRODUCE
1. Open Kdevelop
2. Open Project, choose clang source directory, finish
3. Wait for background parser to run and produce the SegFault

OBSERVED RESULT
- crashes with segmentation fault

EXPECTED RESULT
- finish parsing source code files, continue to run normally

SOFTWARE/OS VERSIONS
Linux: 5.0.2
KDE Plasma Version: 5:102
KDE Frameworks Version: 5:102
Qt Version: 5.11.3

ADDITIONAL INFORMATION
- output to stderr in attached file (kdevelop.log)
- gdb trace (run and bt) in attached file
Comment 1 Stefan Laufmann 2019-05-10 08:40:31 UTC
Created attachment 119947 [details]
trace of gdb (run and bt)

I obtained this trace by running
> gdb kdevelop
> run
> bt
> quit
Comment 2 Stefan Laufmann 2019-05-10 08:43:12 UTC
Created attachment 119948 [details]
zipped log of running kdevelop in console

I obtained this log by running
> KDEV_CLANG_DISPLAY_DIAGS=1 kdevelop &> kdevelop.log
in a console.

Compressed the resulting file to fit into quota.
Comment 3 Kevin Funk 2019-05-10 09:18:11 UTC
Opening the Clang source in KDevelop is unfortunately not /that/ good. As this contains the regression test suite which contains source files which make earlier versions of Clang crash... :)

You might want to put a .kdev_ignore file into the test suite folder, see comments from https://bugs.kde.org/show_bug.cgi?id=382771#c12 and following to get some ideas how to do that.
Comment 4 Kevin Funk 2019-05-10 09:19:14 UTC
To further debug that issue you'd probably need to install the debug symbols for clang so the backtrace gets more useful.
Comment 5 Stefan Laufmann 2019-05-10 11:50:04 UTC
(In reply to Kevin Funk from comment #3)
> Opening the Clang source in KDevelop is unfortunately not /that/ good. As
> this contains the regression test suite which contains source files which
> make earlier versions of Clang crash... :)
> 
> You might want to put a .kdev_ignore file into the test suite folder, see
> comments from https://bugs.kde.org/show_bug.cgi?id=382771#c12 and following
> to get some ideas how to do that.

Ok. I was most curious about the reason of all this.
It worked with placing .kdev_ignore files in the "test" and "unittests" directory. I will see whether it will be possible to build my code since I am trying to implement a scan-build checker.

Thanks for the help.