Bug#438562: jedstate doesn't work on AMD64

[Marc-Jano Knopp]

On Sat, 18 Aug 2007, at 10:58:38 (+0200), Paul Boekholt wrote:
> 2007/8/17, Marc-Jano Knopp <pub_br_debian.org at marc-jano.de>:
> > Package: jedstate
> > Version: 0.5.4.transitional.1-5
> > Severity: important
> >
> > jedstate doesn't work at all on AMD64. With the same recent_db, jedstate
> > on a i386 Lenny box works perfectly, while on an AMD64 Lenny box, it
> > does not.
> 
> GDBM files are not portable - see also
> http://lists.debian.org/debian-amd64/2006/05/msg00023.html

Oh!


> If you start with a new gdbm file, do you still have problems?

If I remove ~/.jed/recent_db ($HOME is shared on all machines) and run
jed on AMD64 first, then everything seems to work again on that machine,
but on the i386 box it does not work anymore.


> > Using strace, I noticed that (with the recent_db that worked flawlessly
> > on i386) jedstate on AMD64 at least sometimes uses absurdly high file
> > offsets:
> >
> >   lseek(3, 70368744194048, SEEK_SET)      = -1 EINVAL (Invalid argument)
>
> The jedstate package has two perl scripts. What did you strace?

I did a simple "strace jed 2>jed.trace".


> Does the gdbmrecent s-lang script work?

How do I check that?


Regards

  Marc-Jano