[ wxwindows-Bugs-1435752 ] Segmentation fault during pychecker run

[SourceForge.net]

Bugs item #1435752, was opened at 2006-02-21 10:22
Message generated for change (Comment added) made by cgrohmann
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=109863&aid=1435752&group_id=9863

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: wxGTK specific
Group: Fatal
>Status: Closed
>Resolution: Out of Date
Priority: 5
Private: No
Submitted By: Carsten Grohmann (cgrohmann)
Assigned to: Nobody/Anonymous (nobody)
Summary: Segmentation fault during pychecker run

Initial Comment:
During a pychcker run on the a wxPython project file,
pychecker dies with a segmentation fault.

The scripts itself runs with out errors.

Output:
=======
(process:20125): GLib-GObject-CRITICAL **:
gtype.c:2254: initialization assertion failed, use
IA__g_type_init() prior to this function

(process:20125): GLib-GObject-CRITICAL **:
gtype.c:2254: initialization assertion failed, use
IA__g_type_init() prior to this function

(process:20125): GLib-GObject-CRITICAL **:
gtype.c:2254: initialization assertion failed, use
IA__g_type_init() prior to this function

(process:20125): GLib-GObject-CRITICAL **:
g_type_add_interface_static: assertion
`G_TYPE_IS_INSTANTIATABLE (instance_type)' failed

(process:20125): GLib-GObject-CRITICAL **:
gtype.c:2254: initialization assertion failed, use
IA__g_type_init() prior to this function

(process:20125): GLib-GObject-CRITICAL **:
gtype.c:2254: initialization assertion failed, use
IA__g_type_init() prior to this function

(process:20125): GLib-GObject-CRITICAL **:
gtype.c:2254: initialization assertion failed, use
IA__g_type_init() prior to this function

(process:20125): GLib-GObject-CRITICAL **:
g_object_new: assertion `G_TYPE_IS_OBJECT
(object_type)' failed
Segmentation fault

Backtrace:
==========
0xb7249457 in gtk_window_new () from
/usr/lib/libgtk-x11-2.0.so.0
(gdb) bt
#0  0xb7249457 in gtk_window_new () from
/usr/lib/libgtk-x11-2.0.so.0
#1  0xb763d58f in wxClipboard::wxClipboard () from
/usr/lib/libwx_gtk2u_core-2.6.so.0
#2  0xb76e5404 in wxClipboardBase::Get () from
/usr/lib/libwx_gtk2u_core-2.6.so.0
#3  0xb66b1f79 in wxPyFileDropTarget::OnDrop ()
   from
/usr/lib/python2.3/site-packages/wx-2.6-gtk2-unicode/wx/_misc_.so
#4  0x08058b8e in PyObject_Call ()
#5  0x080b606c in PyEval_GetFuncName ()
#6  0x080b8357 in PyEval_EvalCodeEx ()
#7  0x080fa712 in PyFunction_SetClosure ()
#8  0x08058b8e in PyObject_Call ()
#9  0x080b606c in PyEval_GetFuncName ()
#10 0x080b6cbc in PyEval_GetFuncName ()
#11 0x080b8357 in PyEval_EvalCodeEx ()
#12 0x080fa712 in PyFunction_SetClosure ()
#13 0x0805c4cf in PyObject_CallFunction ()
#14 0x0809827b in PyType_Ready ()
#15 0x080ab158 in _PyUnicodeUCS4_IsNumeric ()
#16 0x080b6be4 in PyEval_GetFuncName ()
#17 0x080b6cbc in PyEval_GetFuncName ()
#18 0x080b6cbc in PyEval_GetFuncName ()
#19 0x080b6cbc in PyEval_GetFuncName ()
#20 0x080b6cbc in PyEval_GetFuncName ()
#21 0x080b6cbc in PyEval_GetFuncName ()
#22 0x080b8357 in PyEval_EvalCodeEx ()
#23 0x080b6aa4 in PyEval_GetFuncName ()
#24 0x080b6cbc in PyEval_GetFuncName ()
#25 0x080b8357 in PyEval_EvalCodeEx ()
#26 0x080b85d5 in PyEval_EvalCode ()
#27 0x080d929c in PyRun_FileExFlags ()
#28 0x080d9563 in PyRun_SimpleFileExFlags ()
#29 0x08054f07 in Py_Main ()
#30 0xb7d78ed0 in __libc_start_main () from
/lib/tls/libc.so.6
#31 0x080548e1 in _start ()

Versions:
=========
Python:    2.3.5
Pychecker: 0.8.16
wxPython:  2.6.1.2
libgtk:    2.8.10

----------------------------------------------------------------------

>Comment By: Carsten Grohmann (cgrohmann)
Date: 2007-08-22 18:48

Message:
Logged In: YES 
user_id=574043
Originator: YES

I think, this bug has been fixed, cause it doesn't occur using the current
versions.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=109863&aid=1435752&group_id=9863