There are 72 errors; all are at libdap::Vector.cc:1209. (1212 for the testsuite.log where I added some instrumentation in Vector.cc). There are 96 instances of
48 in stack frame 10, and 48 in stack frame 11. The instances where it occurs in frame 10 are the stacks for the 'where it was allocated' and the instances where it occurs in frame 11 are the 'where the errant access took place' frames.
So, there are 24 errors where
is not in the call sequence, and these all seem to involve
calls, also in frame 11 of the errant stack frame. These also appear in pairs - one for 'where the error happens' and one for 'where the memory was allocated.'
Here's the traceback from one of the processJoinNewOnAggVar error stacks: