R
Richard Banville
Guest
No. This is an OpenEdge shared ptr that is encoded to consist of the internal segment table entry number and the offset within the shm segment pointed to by that table which when decoded results in the shared data. It is done this way since absolute addresses do not work for data in shared memory. The latch id in this case is indeed the shared pointer to the bktlb_t but not the latch itself. The latch itself is 32 bytes further within that structure. Each latch has to have a unique identifier. For the BUF latches, the shared pointer to the associated bktbl is the unique identifier. Prior to true object latching, the value would have been one of 4 integer values < 32. I think they were 24, 25, 26, 27 but can't remember for sure.
Continue reading...
Continue reading...