Re: Debugger problem in 5.10

I guess you thaw/retrieve data that was freezed/storedwith another perl or another architecture. Just remove all old data that was serialized with the other computer and use the portable nfreeze/nstore instead of freeze/store next time.

Boris

Comment on Re: Debugger problem in 5.10 Select or Download Code

Replies are listed 'Best First'.
Re^2: Debugger problem in 5.10 by duoxi (Initiate) on Jan 02, 2009 at 15:46 UTC
Boris, thanks. I did think of this and deleted all previously created archives. Also, I am not using freeze/thaw. I am using the following calls: `Storable::lock_store Storable::lock_retrieve` [download] Again, the code works fine when run in normal mode. But when I get to lock_store in the debugger, it core dumps (actually, somewhere inside the Storable routine)...	[reply] [d/l]
Re^3: Debugger problem in 5.10 by borisz (Canon) on Jan 02, 2009 at 16:07 UTC
Then use `lock_nstore` and do not rely on any data stored another way, ported to your new computer. Not in a config file not via a database ,... and so on. Boris	[reply] [d/l]
Re^4: Debugger problem in 5.10 by duoxi (Initiate) on Jan 02, 2009 at 16:34 UTC
I am sorry but I do not understand. I am not porting stored data. The data is newly created on the new computer. I just use Storable for serialization of a temporary storage area. There is no movement of data between machines. The data stored is created on the same computer it is stored, and it is again read on the same computer. D.	[reply]