On Tue, May 6, 2008 at 5:28 AM, Adam Sjøgren <asjo(a)koldfront.dk> wrote:
I have tried to do this now, this is what happened:
Does that help?
Yes, it certainly does. The watchpoint was never triggered. Since
that is the only place where XEmacs had the pointer in question, that
means that XEmacs did not touch the pointer, which makes the
possibility of the bug being in XEmacs code even more remote. It
doesn't prove that the bug is not in XEmacs, but it makes it much less
likely. We could still have some kind of random heap corruption bug
that touches the memory in question without going through the pointer.
But that would tend to trigger segfaults, which you aren't seeing.
XEmacs-Beta mailing list