Richard Maine wrote:
...
> Oh, and I find it suspicious that you didn't mention another
> matter, because it is high on the list of pointer-related errors.
> Might one of the pointers in question have an undefined pointer
> association status? If the association status is undefined, then
> you aren't allowed to even call associated. Or for that matter, is
> one of them disassociated? If you are just looking at pointer innards
> such as the target address, that might be irrelevant if there is a
> bit somewhere else saying that the pointer is disassociated.
In addition, though I could be wrong, I seem to remember that
two pointers are actually not associated if they point to different
slices. If they merely overlap in memory, but have differing
sizes, ranks, or strides, are they (officially) associated?
--
J. Giles
"I conclude that there are two ways of constructing a software
design: One way is to make it so simple that there are obviously
no deficiencies and the other way is to make it so complicated
that there are no obvious deficiencies." -- C. A. R. Hoare
|