Benjamin wrote:
On Mon, 30 Aug 2010 13:22:52 -0400, corvid <corvid@lavabit.com> wrote:
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?
I have the call stack, and I'm not sure how much else. I'm using gdb via Qt Creator, which is less than ideal, but it's the closest thing available to a working front-end.
What does the call stack look like?
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.
That might be it. What type of DPI stuff, specifically? I have some conceptual understanding and I'm sure I saw it in the docs, but my memory's a little hazy...
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...