segmentation fault when unpickling an object in another Python instance

[Raik Gruenberg]

It's not cPickle specific - I got the same segmentation fault when using 
  normal pickle.

Getting a minimum example will take some time and it can get quite long. 
I can switch off the error by deleting a line in the constructor of the 
pickled object...

Summary so far, I can not unpickle my object if:
- The constructor of this object called (before pickling) a certain 
method of an internally referenced object
- this internal object encapsulates an Numeric array
- the certain method deletes parts of this array (via Numeric.compress )

Rings a bell for someone??

Anyway, I'll see what I can do.
All comments are welcome !

Raik


Terry Reedy wrote:
> "Raik Gruenberg" <graik at web.de> wrote in message
> news:3DC96AAD.9090503 at web.de...
> 
> 
>>I have got some home-made class. From within the same Python
> 
> interpreter
> 
>>  I can create, dump and load it back without any problem. But, if I
> 
> try
> 
>>to load it after re-starting the interpreter, I end up with a
>>segmentation fault.
>>
> 
>>Obviously, it is also somewhat the fault of this
>>particular class. I narrowed down the problem somewhat. But, before
>>bothering you with all the details, perhaps anyone knows this
> 
> problem or
> 
>>has some promising idea???
> 
> 
> There have been some known problems with CPickle and some patches, but
> in the absence of keyword searching of the SourceForge database, I
> won't guess as to specifics and relation to your problem.  You may be
> asked for minimum example that exhibits problem.
> 
> TJR
> 
>