#897 Problem with multiple initializations

open
nobody
python (259)
5
2012-12-21
2008-02-22
herurg
No

This is a major showstopper.

Steps to reproduce (with C/C++ app that uses embeded python 2.5 interpreter):

1. Initialize python
2. Load wrapped C++ module
3. Finalize python
4. Initialize python again
5. Try to load the same wrapped module - get into infinite loop (SWIG_TypeClientData)

I ran into this when upgraded from 1.3.22 to 1.3.33.
I haven't tried it with simple programs, but i know several people who had similar issue. All of them eventually downgraded to SWIG 1.3.2x

Discussion

  • rather_not_disclose

    Logged In: YES
    user_id=1598900
    Originator: NO

    I sumbitted an example that can be re-swigged to demonstrate this on the last bug.

     
  • John Lenz

    John Lenz - 2008-02-22

    Logged In: YES
    user_id=153408
    Originator: NO

    Can you please retest with the latest svn code.... we fixed at least one bug related to multiple interpreters already.

     
  • rather_not_disclose

    Logged In: YES
    user_id=1598900
    Originator: NO

    in SVN (1.3.34) this is fixed (infinite loop) but now core dumps due to corrupted SWIG_This() caused by SWIG_Python_DestroyModule -- comment it out and it might work.

     
  • herurg

    herurg - 2008-02-28

    Logged In: YES
    user_id=2016846
    Originator: YES

    With 1.3.34 PyDict_SetItem(dict, SWIG_This(), swig_this) call (in SWIG_Python_NewShadowInstance) crashes for me. SWIG_This() seems to return garbage.

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks