#15211: KDL in MultiLocker::ReadLock()
-----------------------------+----------------------------
Reporter: 3dEyes | Owner: waddlesplash
Type: bug | Status: assigned
Priority: normal | Milestone: Unscheduled
Component: System/Kernel | Version: R1/Development
Resolution: | Keywords:
Blocked By: | Blocking:
Has a Patch: 0 | Platform: All
-----------------------------+----------------------------
Comment (by mmlr):
The address contains `0xcccccccc` which would match the "uninitialized
memory" pattern written by the normal allocator. Since the lock cannot
really be uninitialized (as one would expect the corresponding lock to
fail in that case), this might be a use-after-free case where the
allocation has been handed out again already. Is it possible that the
thread went away due to a missing reference or some such?
The `isr_array (nearest)` is a red herring as `(nearest)` always just
means that the symbol lookup did not find an actual match. This can happen
in some generated and/or optimized code and usually means that it's not
actually where it suggest it might be.
--
Ticket URL: <https://dev.haiku-os.org/ticket/15211#comment:8>
Haiku <https://dev.haiku-os.org>
The Haiku operating system.