Summary: | segfault in kpixmapcache (triggered from kwin): KPixmapCache::Private::invalidateMmapFiles | ||
---|---|---|---|
Product: | [Frameworks and Libraries] kdelibs | Reporter: | Melchior Franz <mfranz> |
Component: | kdeui | Assignee: | kdelibs bugs <kdelibs-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | aseigo, mpyne, poletti.marco, rivolaks |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Melchior Franz
2009-05-14 15:22:48 UTC
Here's some more info (related to the above bt): (gdb) f 0 #0 0xb7b6591e in KPixmapCache::Private::invalidateMmapFiles (this=0x8b90508) at /home/m/kde4/kdelibs/kdeui/util/kpixmapcache.cpp:441 441 mIndexMmapInfo.indexHeader->cacheId = 0; (gdb) p mIndexMmapInfo $5 = { file = 0x8d330f8, { memory = 0xb3665000 <Address 0xb3665000 out of bounds>, indexHeader = 0xb3665000, dataHeader = 0xb3665000 }, size = 516, available = 4296704 } *** Bug 187724 has been marked as a duplicate of this bug. *** is this addressed by the recent fixes for bug #160284? This code was addressed recently, but not as part of 160284 but for bug 182026 (which fixes pointer aliasing issues with shared memory). Did the fix for that fix this too? I don't know, but it's possible that pointer aliasing was causing this bug too. I'll optimistically mark as FIXED for now, please re-open if it gets reproduced again. |