Sample code:
	PyObject *b=PyBytes_FromString("eh ?????");
	PyObject *mv=PyMemoryView_FromObject(b);
	PyObject_CheckReadBuffer(mv);

From following the chain of calls in PyObject_CheckReadBuffer,
a few things are unclear.

It calls bf_getbuffer with a NULL Py_Buffer pointer, although the PEP
explicitely states that is should never be NULL.

PyBuffer_FillInfo immediately returns success if the view pointer is
NULL.  I'm guessing this is to just determine if the operation could be
completed, but it returns before any checks are done.

It then attempts to release a hardcoded NULL Py_buffer pointer
which of course crashes.

And the following statement crashes the interpreter:

>>> compile(memoryview(b"text"), "name", "exec")

Attaching patch and test.

The test would be better in test_memoryview rather than in test_builtin.

On Thu, Sep 25, 2008 at 6:39 AM, Antoine Pitrou <report@bugs.python.org> wrote:
>
> Antoine Pitrou <pitrou@free.fr> added the comment:
>
> The test would be better in test_memoryview rather than in test_builtin.

I disagree. The test I added is really about compile, and its failure
was really just a side effect of the buffer bug.

> I disagree. The test I added is really about compile, and its failure
> was really just a side effect of the buffer bug.

Well, I won't fight over it, but it's really meant to check an aspect of
memoryview behaviour - otherwise why would it be part of your patch ? -,
and as such it should be in test_memoryview (and if it's meant to check
compile() then it should be in some hypothetical test_compile :-)).

In general I find it annoying that many tests are dumped into "generic"
test files like test_builtin, rather than in the test file appropriate
for the functionality being tested.

That said, I haven't looked at the rest of the patch yet, sorry! (back
from holidays)

The rest of the patch is fine with me (I assume you've run all the unit
tests :-)).

I'm actually having a hard time trying to get memoryview to use
PyObject_CheckReadBuffer. Eventually, test should be written in C, but
for now are you ok with the compile test?

Fixed in r66630.