[Kde-bindings] [Bug 210991] ruby Segmentation fault when Qt is uninitialized

[Gary at immanuel.kde.org]

https://bugs.kde.org/show_bug.cgi?id=210991





--- Comment #5 from Gary L. Greene, Jr. <greeneg kde org>  2009-10-19 07:38:48 ---
Due to the way Ruby's interpreter works, it honestly doesn't surprise me. I've
seen far worse segfaults from ruby gems like ActiveLDAP when I maintained code
that used it at a previous employer due to the way Ruby's garbage collector
works. Since QtRuby and Korundum both are C++ bindings with complex internals,
if any of the shared variables aren't properly marked, and the object is
improperly destroyed from the stack without the mark and sweep gc's help, a
crash of the interpreter will likely occur when it attempts to collect a stack
trace for error output as early in the initialization of the binding. Richard,
do think that maybe there are a few corner cases in the binding that would
allow a shared object to be reaped too soon in this case?

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.