Any idea what might be causing this and what I can do?...

update: Also, UPGRADE YOUR STORABLE (latest version is Storable-2.13) and see if that fixes it (no point in debugging outdated code).

I was under the impression that you cannot (err, should not) upgrade Storable without upgrading Perl at the same time.. Is that not the case?..

Also, I am not sure if it is failing during a read or a write, but according to the stack trace I'd say probably more likely a write...

Here is the code for writing:

      my @vals=(\@someArray,\%someHash);
      my $res=store(\@vals,"$path/$name");
[download]

Here is some code for reading:

  my @someArray = ();
  my %someHash = ();
  my $res=retrieve("$path/$name");
  if($res) {
    my ($tmp1, $tmp2) = @$res;
    if($tmp1) {
      @someArray = @$tmp1;
    }
    if($tmp2) {
      %someHash = %$tmp2;
    }
  }
[download]

I started doing diff on storable.xs and am pretty sure that it must be failing inside magic_write, somewhere around this line:

WRITE(header, length);
[download]

Interestingly this was changed in 2.07 to:

WRITE( (unsigned char*) header, length);
[download]

The WRITE #define has been unchanged, even up to version 2.13:

#define WRITE(x,y)                             \
  STMT_START {                                \
    if (!cxt->fio)                            \
        MBUF_WRITE(x,y);                    \
    else if (PerlIO_write(cxt->fio, x, y) != y)    \
        return -1;                            \
  } STMT_END
[download]

I'm not a C programmer so I'm not sure what relevance any of this has, could this be the source of the problem?... I can't find in the ChangeLog why that particular change was made and don't really know what it does...

Any ideas?...

I was under the impression that you cannot (err, should not) upgrade Storable without upgrading Perl at the same time.. Is that not the case?..

That is not the case. I upgrade core (albeit generally only ones which are distributed separately on CPAN) modules every day and so should you (for example, File::Spec is continually being improved).

...my $res=retrieve("$path/$name");...

It could very well be that $path/$name is corrupt somehow, but how would anyone except you reproduce that?

I started doing diff on storable.xs and am pretty sure that it must be ...

Um, yeah, whatever. Did you try your code with the newest storable? Did it work? Did you try regenerating $path/$name? Does it still break (with the newest storable)? If you still can't get it to work try contacting the perl Storable people (perl5-porters at at at at at at at at at at at at at at at at at at at perl.org), and be sure to send them a self-contained snippet which reproduces the bug (including a copy of your storable file).

Good luck

MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"

I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).

** The third rule of perl club is a statement of fact: pod is sexy.