| Summary: | Stack smashing crash when opening project properties | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | git.ceeac |
| Component: | Astyle | Assignee: | kdevelop-bugs-null |
| Status: | RESOLVED DOWNSTREAM | ||
| Severity: | crash | CC: | fischer, igorkuo, jarmo.tiitto, nolo18 |
| Priority: | NOR | ||
| Version First Reported In: | 6.3.250800 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
git.ceeac
2025-08-17 07:32:17 UTC
Cannot reproduce in KDevelop master. I can think of two possible reasons for the crash on your system: 1. Arch Linux enabled some new compiler flags for the compilation of the latest KDevelop package version, which discovered a bug in KDevelop or the astyle library. 2. Either the kdevelop or the astyle package was miscompiled or corrupted when installed on your system. The easiest thing to try first is to reinstall both packages. Also try rebooting your system. Note that the relevant KDevelop code has not been modified in the last 3 years, so this is not likely to be a recent regression. Looks like https://archlinux.org/packages/extra/x86_64/astyle was updated hours later than https://archlinux.org/packages/extra/x86_64/kdevelop. Maybe the same issue as https://gitlab.archlinux.org/archlinux/packaging/packages/kdevelop/-/issues/1? Try downgrading to the previous astyle version and if it works ask Arch maintainers to rebuild KDevelop against the latest astyle version. *** Bug 508637 has been marked as a duplicate of this bug. *** OK, downgrading astyle from 3.6.12-1 to 3.6.6-1 seems to fix the crash. (In reply to git.ceeac from comment #5) > OK, downgrading astyle from 3.6.12-1 to 3.6.6-1 seems to fix the crash. Please report the issue to Arch maintainers. Rebuilding KDevelop against the latest astyle version should fix the issue as it did the last time: https://gitlab.archlinux.org/archlinux/packaging/packages/kdevelop/-/commit/e912c180690fffa823a2c0cb64f730ea1a620f91 *** Bug 509170 has been marked as a duplicate of this bug. *** |