Summary: | GeoDataFolder iterator methods crash | ||
---|---|---|---|
Product: | [Applications] marble | Reporter: | magliocca |
Component: | general | Assignee: | marble-bugs |
Status: | REPORTED --- | ||
Severity: | crash | CC: | morrand276 |
Priority: | NOR | ||
Version: | 22.04.3 | ||
Target Milestone: | --- | ||
Platform: | Debian stable | ||
OS: | Microsoft Windows | ||
See Also: | https://bugs.kde.org/show_bug.cgi?id=471339 | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
magliocca
2022-08-31 14:43:17 UTC
I can confirm the same problem is occurring on FreeBSD 12.3 on Marble 22.08.1 (FreeBSD port version 22.08.1_1), with Qt version 5.15.5p165, Plasma 5.24.6_1. It's actually showing up in two different ways for me. If the GeoDataFolder is created in a different function, then within begin(), *this is null, and the attempt to set the d pointer segfaults, apparently because it's trying to access memory at this+0x18 or something like that. If it's created within the same function, then *this is some absurd value like 0x7fffffffe598 and the attempt to set d fails with a bus error. These seem to just be different expressions of the same problem. I too can access at(), first(), and other methods within GeoDataFolder without any trouble, and they seem to return sensible results. This problem seems to affect just the methods that return a QVector<GeoDataFeature*>::Iterator, which are begin() and end(). |