Enrico Scholz wrote:
this looks already strange... a hash value with so much '0' is highly
improbable...
Mmmm, so it could be a beecrypt2 problem... right?
I'll try installing from non-debian sources util-vserver and beecrypt to
see what happens. The hash belongs to a real executable though
(according to "file <hash_file>"), not sure which executable but
something to do with mount (my guess from the strings it contains).
I will add some testcases to localise the problem. But because I can not
reproduce this behavior on my system, I can not tell a solution now.
I would appreciate :)
valgrind could give some more information perhaps; I guess a gdb
stacktrace will not be very meaningful.
Darn! no amd64 package for valgrind. I guess the i386 version won't help
much debugging 64bit executables so I'll try to build a 64bit version
(though I feel it might not be possible at all yet as valgrind is very
arch dependant...)
Thanks,
Alberto
_______________________________________________
Vserver mailing list
[email protected]
http://list.linux-vserver.org/mailman/listinfo/vserver
