bug#14062: 24.3.50; emacs_backtrace.txt

[martin rudalics]

> But for nil, BUFFERP will return zero, and the code that uses XBUFFER
> should not be called, IMO.
[...]
> But the uninitialized contents field should be zero, no?  Again, it
> should not pass the BUFFERP test.
>
> So the mystery still stands.

You mean that the w->contents argument of XBUFFER _always_ passes the
BUFFERP test first and then fails at the assertion in XBUFFER?  How can
that make sense?

martin