Bug 12809

Summary: CRASH: Reproducible crasher in Linux/Qt port
Product: WebKit Reporter: Justin Haygood <jhaygood>
Component: PlatformAssignee: Oliver Hunt <oliver>
Status: CLOSED FIXED    
Severity: Major CC: mitz
Priority: P1    
Version: 420+   
Hardware: PC   
OS: Linux   
Attachments:
Description Flags
Stubbed out implementation of clipboard for qt aroben: review+

Justin Haygood
Reported 2007-02-18 22:10:13 PST
gdb reveals: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 47928969825216 (LWP 28484)] 0x00002b974fbd7ebe in WebCore::Clipboard::setAccessPolicy () from /home/jhaygood/OSS/Webkit/WebKitBuild/Debug/lib/libWebKitQt.so.1 How to reproduce: Basically, attempting to copy anything, even accidently :) Platform: OpenSUSE 10.2 (x86_64) Qt: 4.2.2 (x86_64) GCC: 4.1.2 (SUSE Linux)
Attachments
Stubbed out implementation of clipboard for qt (8.39 KB, patch)
2007-02-18 23:12 PST, Oliver Hunt 		aroben: review+
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Oliver Hunt
Comment 1 2007-02-18 22:13:29 PST
This is caused by the absence of a qt impl of Clipboard :(
Oliver Hunt
Comment 2 2007-02-18 23:12:09 PST
Created attachment 13233 [details] Stubbed out implementation of clipboard for qt
Adam Roben (:aroben)
Comment 3 2007-02-18 23:14:03 PST
Comment on attachment 13233 [details] Stubbed out implementation of clipboard for qt r=me
mitz
Comment 4 2007-02-19 07:27:22 PST
Committed in r19700. Is there a reason why the bug is still open?
mitz
Comment 5 2007-02-19 12:03:12 PST
Presumed fixed until proven otherwise.
Justin Haygood
Comment 6 2007-02-19 18:42:59 PST
Still crashes for me in r19717. Same place. Same cause: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 47459251575744 (LWP 5989)] 0x00002b29f259ea5e in WebCore::Clipboard::setAccessPolicy () from /home/jhaygood/OSS/Webkit/WebKitBuild/Release/lib/libWebKitQt.so.1 (gdb) back #0 0x00002b29f259ea5e in WebCore::Clipboard::setAccessPolicy () from /home/jhaygood/OSS/Webkit/WebKitBuild/Release/lib/libWebKitQt.so.1 #1 0x00002b29f27b6892 in WebCore::EventHandler::handleDrag () from /home/jhaygood/OSS/Webkit/WebKitBuild/Release/lib/libWebKitQt.so.1 #2 0x00002b29f27b9d30 in WebCore::EventHandler::handleMouseMoveEvent () from /home/jhaygood/OSS/Webkit/WebKitBuild/Release/lib/libWebKitQt.so.1 #3 0x00002b29f27ba762 in WebCore::EventHandler::handleMouseMoveEvent () from /home/jhaygood/OSS/Webkit/WebKitBuild/Release/lib/libWebKitQt.so.1 #4 0x00002b29f27cbfc8 in WebCore::FrameView::handleMouseMoveEvent () from /home/jhaygood/OSS/Webkit/WebKitBuild/Release/lib/libWebKitQt.so.1
Oliver Hunt
Comment 7 2007-02-19 19:05:24 PST
What value does this have at that point?
Justin Haygood
Comment 8 2007-02-19 21:03:31 PST
Oops, really is fixed. Would help if I ran the right binary :)
Oliver Hunt
Comment 9 2007-02-19 21:28:28 PST
Hurrah! I was slightly confused as the patch should have fixed it -- and lo' it had :D
Note You need to log in before you can comment on or make changes to this bug.