Hi,

> My origonal post has a fix that got around this core dump, ie doing checks
> for null pointers.

I know... but my point is that a 'null pointer' should never happen  
there (since d is assigned on KFileWidget constructor, and thus, is  
never null).

It would be great some context information on the backtrace (like,  
what KOffice code did the call), also it is crucial to know where  
exactly on the showEvent() the dump happened.

I prefer to understand the problem deeply than adding a null pointer  
check blindly that we don't actually understand why is it happening.


Regards,
Rafael Fernández López.
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<