30 Aug
2010
30 Aug
'10
9:25 p.m.
On Mon, Aug 30, 2010 at 2:53 PM, corvid <corvid@lavabit.com> wrote:
What does the call stack look like?
Here's the backtrace: http://obeythepenguin.users.sourceforge.net/dillo/misc/dStr_insert_l-backtra...
Actually, if you saw inflate and you were coming through the decode.c and cache.c code, I can't immediately think of a way that it would necessarily be a dpi issue...
All right, that makes sense since DPI should report a pipe error instead of segfaulting.