[Webkit-unassigned] [Bug 34730] New: [Qt] Null QObjects properties cause Segmentation Fault
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Feb 8 15:57:21 PST 2010
https://bugs.webkit.org/show_bug.cgi?id=34730
Summary: [Qt] Null QObjects properties cause Segmentation Fault
Product: WebKit
Version: 528+ (Nightly build)
Platform: All
OS/Version: All
Status: UNCONFIRMED
Severity: Normal
Priority: P2
Component: WebKit Qt
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: bruno.schmidt at gmail.com
Created an attachment (id=48372)
--> (https://bugs.webkit.org/attachment.cgi?id=48372)
Patch fixing the bug
If an QObject is added to the javascript context and it contains properties of
the type QObject* with NULL value, calling the property causes Segmentation
Fault.
So now the code checks for objects which are null and threat them accordingly:
* QtInstance::getClass() may return NULL
* QtInstance::stringValue(ExecState* exec) may return jsNull()
* QtInstance::booleanValue() may return false.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list