On Thu, 17 Jun 2010 11:14:43 -0400, Jorge Arellano Cid wrote:
On Thu, Jun 17, 2010 at 09:44:03AM -0400, Dennis Nezic wrote:
I seem to be experiencing a very nasty bug that breaks my Dillo. A few seconds after starting dillo, it "freezes" -- standard-output stops, the graphics freeze and never get redrawn (resulting in those psychodelic effects of moving windows over a non-redrawing window). My dillo window then doesn't respond to my window manager's "close" events, and I have to manually kill it.
I can't give you the exact steps to reproduce it -- sometimes it's like this immediately after starting ... sometimes it magically starts to happen a few seconds afterwards -- possibly after I click on a link.
dillo-2.2 fltk-2_pre7513 (I also tried with earlier versions (6970))
Ideas?
gdb dillo <dillo freezes somewhere here> ctrl-c bt
And send us the gdb backtrace.
(gdb) bt #0 0x00007f3cca17089d in connect () from /lib/libpthread.so.0 #1 0x000000000044227e in Dpi_connect_socket () #2 0x0000000000442f6f in a_Dpi_send_blocking_cmd () #3 0x0000000000411115 in a_Cookies_get_query () #4 0x000000000044098d in a_Http_make_query_str () #5 0x0000000000441481 in Http_connect_queued_sockets () #6 0x00000000004375da in Dns_timeout_client () #7 0x00007f3ccac8c4cf in fltk::wait () from /usr/lib64/fltk/libfltk2.so #8 0x00007f3ccac8c595 in fltk::run () from /usr/lib64/fltk/libfltk2.so #9 0x000000000040af23 in main () I don't know if this helps -- but that's the bt for dillo after I ctrl-c, after the graphics/ui becomes unresponsive.