Bug 405097 - Unhandled exception in KDevPlatformLanguage.dll during background parsing crashes program
Summary: Unhandled exception in KDevPlatformLanguage.dll during background parsing cra...
Status: RESOLVED WORKSFORME
Alias: None
Product: kdevelop
Classification: Applications
Component: Language Support: CPP (Clang-based) (other bugs)
Version First Reported In: 5.3.1
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-04 23:56 UTC by Jeremy W. Murphy
Modified: 2019-04-05 04:33 UTC (History)
1 user (show)

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


Attachments
Unhandled exception dialogue from Visual Studio debugger (9.74 KB, image/png)
2019-03-04 23:56 UTC, Jeremy W. Murphy
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jeremy W. Murphy 2019-03-04 23:56:04 UTC
Created attachment 118549 [details]
Unhandled exception dialogue from Visual Studio debugger

SUMMARY

Unhandled exception in KDevPlatformLanguage.dll: Access violation reading location 0x20.

STEPS TO REPRODUCE
1. Open my work project
2. Wait for a few minutes

OBSERVED RESULT

See attached image.

EXPECTED RESULT

No crashes. :)

SOFTWARE/OS VERSIONS
Windows: 10 version 1607
KDE Frameworks Version: 5.52.0
Qt Version: 5.11.2

ADDITIONAL INFORMATION

Using the Windows installer downloaded from kdevelop.org.
Comment 1 Sven Brauch 2019-03-04 23:57:58 UTC
Hi, sorry for the trouble and thanks for the report. Unfortunately this is not enough information to do anything about it. We either need a backtrace or a sample file which reproduces the issue.
Comment 2 Jeremy W. Murphy 2019-03-05 00:10:38 UTC
(In reply to Sven Brauch from comment #1)
> Hi, sorry for the trouble and thanks for the report. Unfortunately this is
> not enough information to do anything about it. We either need a backtrace
> or a sample file which reproduces the issue.

Hi Sven, how do I generate the backtrace in Windows? It's not my usual programming environment. I have Visual Studio, do I just run it from within?
Comment 3 Kevin Funk 2019-03-06 07:54:00 UTC
@Jeremy: Yep, that's one option.

Unfortunately we don't provide the debugging symbols (PDB files) though. So the stack trace is likely going to be not that useful. But you can check whether it reveals some details.
Comment 4 Jeremy W. Murphy 2019-03-06 08:00:50 UTC
(In reply to Kevin Funk from comment #3)
> @Jeremy: Yep, that's one option.
> 
> Unfortunately we don't provide the debugging symbols (PDB files) though. So
> the stack trace is likely going to be not that useful. But you can check
> whether it reveals some details.

Ok, thanks. Is it practical to include that PDB file in the Windows installer? Our as an optional download?
I guess my other option is to build with symbols myself?
Comment 5 Kevin Funk 2019-03-06 08:07:37 UTC
It's an option, but we currently dont do it. As the installer is generated on KDE's Binary Factory, there's no easy way to get access to the PDB files either.

You're best option is to compile KDevelop yourself, using the https://community.kde.org/Craft package manager.
Comment 6 Bug Janitor Service 2019-03-21 04:33:11 UTC
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
mark the bug 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!
Comment 7 Bug Janitor Service 2019-04-05 04:33:10 UTC
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!