----- "Nick Kew" <n...@apache.org> wrote: > 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).
Given the fact that we've lost all of INK_* and INK* in favour for TS_* and TS*, I'd say upgrading to 2.1.4 or trunk > 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? I think we've had that discussion in ``[DISCUSS] Change SDK return values?'' http://www.mail-archive.com/dev@trafficserver.apache.org/msg02353.html > -- > Nick Kew i -- Igor Galić Tel: +43 (0) 664 886 22 883 Mail: i.ga...@brainsware.org URL: http://brainsware.org/
