Konqueror problem -- this one is worse :-(

[CP Hennessy]

On Saturday 16 November 2002 16:30, Moritz Moeller-Herrmann wrote:
> >> http://www.intel.com/design/intelxscale/
[snip]
> #5  <signal handler called>
> #6  0x445f01b0 in KJS::Value::toObject(KJS::ExecState*) const (this=0x0,
>     exec=0xbfffe170) at value.cpp:305
I think that it's not a good idea that the "this" value is NULL! :)

> #7  0x445c8c52 in KJS::AccessorNode2::evaluate(KJS::ExecState*) const (
>     this=0x8315e10, exec=0xbfffd7fc) at nodes.cpp:583
> #8  0x445c667f in KJS::Node::value(KJS::ExecState*) const (this=0xfffffe00,
>     exec=0xbfffe170) at nodes.cpp:116
The "this" value here also looks highly suspicious ( it is essentiall NULL - 
200 )!

> #9  0x445cd291 in KJS::AssignNode::value(KJS::ExecState*) const (
>     this=0x8309e58, exec=0xbfffe170) at nodes.cpp:1535
Actually here the code looks like:
v = expr->value(exec);
but is it possible for "expr" to be a NULL pointer?

CPH

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<