Bug 37073 - Segmentation fault `WebCore::TimerHeapElement::operator=`
Summary: Segmentation fault `WebCore::TimerHeapElement::operator=`
Status: UNCONFIRMED
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC Linux
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-04 17:37 PDT by Jonas H
Modified: 2010-04-04 17:37 PDT (History)
0 users

See Also:

Attachments
gdb traceback of the segfault (8.57 KB, text/plain)
2010-04-04 17:37 PDT, Jonas H 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jonas H 2010-04-04 17:37:05 PDT 
Created attachment 52515 [details]
gdb traceback of the segfault

I can reproduce a Segmentation Fault that occurs in `WebCore::TimerHeapElement::operator=` probably because `t` is a null pointer. The full traceback is attached.

I'm using a rather complex setup: Python + PyWebkitGTK (the Python binding) + PyJavaScriptCore (a Python JSC binding, [1]) + GObject threads.

I'm sure this has something to do with threads as we're getting *lots* of threading problems with this setup.

Could please anyone give me a tip what the problem might be so I can do further research fixing this issue? Thanks! :-)


[1] http://github.com/cream/PyJavascriptCore (fork of http://launchpad.net/pyjavascriptcore)