I have the bundled null-transform segfaulting on me. This happens with the bundled (unaltered) source, and built on Linux/x86 with -O0 flag to gcc.
(version is 2.1.3 - tell me to upgrade if I'm talking about a fixed issue). Diagnosis: In the first call to handle_transform, INKVConnwrite is called with nbytes == -1, so it returns INK_ERROR_PTR (0xbad). This is then passed to INKVIOBufferGet in the second call to handle_transform at line 159, causing segfault. Failure to check data->output_vio looks like a simple bug in null-transform.c, but I'm concerned about this liberal use of a bogus pointer in the library. Doesn't this cause a lot of brittleness in production? -- Nick Kew
