I just went through the long process of building webkit 1.4.1 on my
yeeloong. It works fairly well until I go to any websites with
javascript on them. Webkit segfaults at this point. Below is the output
of running backtrace on the coredump. Anyways, I'm sure this is more of
a webkit problem then a ports problem, but I thought I'd check here
first. In the mean time running surf with javascript disabled works
great.

#0  0x0000000055204f50 in JSC::Interpreter::privateExecute () from
/usr/local/lib/libwebkitgtk-1.0.so.0.1
(gdb) backtrace
#0  0x0000000055204f50 in JSC::Interpreter::privateExecute () from
/usr/local/lib/libwebkitgtk-1.0.so.0.1
#1  0x000000005520c898 in JSC::Interpreter::execute () from
/usr/local/lib/libwebkitgtk-1.0.so.0.1
#2  0x000000005525d658 in JSC::evaluate () from
/usr/local/lib/libwebkitgtk-1.0.so.0.1
#3  0x00000000542bcbe8 in WebCore::ScriptController::evaluateInWorld ()
from /usr/local/lib/libwebkitgtk-1.0.so.0.1
#4  0x00000000542bd610 in WebCore::ScriptController::evaluate () from
/usr/local/lib/libwebkitgtk-1.0.so.0.1
#5  0x0000000054473c98 in WebCore::ScriptElement::executeScript () from
/usr/local/lib/libwebkitgtk-1.0.so.0.1
#6  0x0000000054473f14 in WebCore::ScriptElement::execute () from
/usr/local/lib/libwebkitgtk-1.0.so.0.1
#7  0x000000005447cf70 in WebCore::ScriptRunner::timerFired () from
/usr/local/lib/libwebkitgtk-1.0.so.0.1
#8  0x000000005447d520 in WebCore::Timer<WebCore::ScriptRunner>::fired
() from /usr/local/lib/libwebkitgtk-1.0.so.0.1
#9  0x000000005490f080 in
WebCore::ThreadTimers::sharedTimerFiredInternal () from
/usr/local/lib/libwebkitgtk-1.0.so.0.1
#10 0x000000005490f14c in WebCore::ThreadTimers::sharedTimerFired ()
from /usr/local/lib/libwebkitgtk-1.0.so.0.1
#11 0x00000000540d5ef8 in WebCore::timeout_cb () from
/usr/local/lib/libwebkitgtk-1.0.so.0.1
#12 0x000000005f8f2db0 in g_source_get_time () from
/usr/local/lib/libglib-2.0.so.2800.0
#13 0x0000000000000000 in ?? ()

Reply via email to