After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 732155 - Cannot initialize python loader from python application
Cannot initialize python loader from python application
Status: RESOLVED FIXED
Product: libpeas
Classification: Platform
Component: python
unspecified
Other Linux
: Normal normal
: ---
Assigned To: libpeas-maint
libpeas-maint
Depends on:
Blocks: 733434
 
 
Reported: 2014-06-24 12:34 UTC by Garrett Regier
Modified: 2014-07-23 14:36 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Bug 732155 - Fix initializing Python loader from Python application (3.67 KB, patch)
2014-06-24 12:39 UTC, Garrett Regier 		committed Details | Review

Description Garrett Regier 2014-06-24 12:34:46 UTC 
However, we already support an already initialized python.


Program received signal SIGSEGV, Segmentation fault.
0x000000355530361d in PySys_GetObject () from /lib64/libpython2.7.so.1.0
Missing separate debuginfos, use: debuginfo-install python-2.7.5-9.fc20.x86_64
(gdb) bt

+ Trace 233724

  • #0 PySys_GetObject
    from /lib64/libpython2.7.so.1.0
  • #1 PySys_SetArgvEx
    from /lib64/libpython2.7.so.1.0
  • #2 peas_plugin_loader_python_initialize
    at /home1/agunturu/lepton/rift/modules/ext/gnome/libpeas/libpeas-1.9.0/loaders/python/peas-plugin-loader-python.c line 428
  • #3 peas_plugin_loader_initialize
    at /home1/agunturu/lepton/rift/modules/ext/gnome/libpeas/libpeas-1.9.0/libpeas/peas-plugin-loader.c line 50
  • #4 get_plugin_loader
    at /home1/agunturu/lepton/rift/modules/ext/gnome/libpeas/libpeas-1.9.0/libpeas/peas-engine.c line 690
  • #5 load_plugin
    at /home1/agunturu/lepton/rift/modules/ext/gnome/libpeas/libpeas-1.9.0/libpeas/peas-engine.c line 834
  • #6 peas_engine_load_plugin_real
    at /home1/agunturu/lepton/rift/modules/ext/gnome/libpeas/libpeas-1.9.0/libpeas/peas-engine.c line 875
  • #7 g_cclosure_marshal_VOID__BOXEDv
    at /home1/agunturu/lepton/rift/modules/ext/gnome/glib/glib-2.38.2/gobject/gmarshal.c line 1160
  • #8 g_type_class_meta_marshalv
    at /home1/agunturu/lepton/rift/modules/ext/gnome/glib/glib-2.38.2/gobject/gclosure.c line 997
  • #9 _g_closure_invoke_va
    at /home1/agunturu/lepton/rift/modules/ext/gnome/glib/glib-2.38.2/gobject/gclosure.c line 840
  • #10 g_signal_emit_valist 






Comment 1


Garrett Regier





          2014-06-24 12:39:39 UTC
        



Created attachment 279113 [details] [review]
Bug 732155 - Fix initializing Python loader from Python application






Comment 2


Ignacio Casal Quinteiro (nacho)





          2014-06-24 12:45:31 UTC
        



Review of attachment 279113 [details] [review]:

Seems fair enough.






Comment 3


Garrett Regier





          2014-07-23 14:36:17 UTC
        



This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.