30 Aug
2010
30 Aug
'10
7:22 p.m.
Benjamin wrote:
On 8/30/10, corvid <corvid@lavabit.com> wrote:
Do you have an idea of what's wrong with the dStr_insert_l() crash? I didn't get that far until late last night, since it took me a while to figure out iowatch, but it looks like it happens during rendering. I saw there's a zlib inflate (I think) somewhere up the call stack, and that it segfaults at memcpy(), and that's about all I have so far.
Does Windows let you get a meaningful backtrace?
Does Dillo use any temporary files when rendering a page? I haven't adjusted paths.cc beyond mkdir() -> dMkdir(), so I wonder if that has something to do with it.
Nope. Although it can start trying to do dpi stuff while a page is coming.