Hello,
this is definitively a problem specific to 64bits or amd64.
Also seems to depend on kernel version or special configuration or
patches for etch-backports kernels.
I tested with a very simple test program:
----------------------------------------
#include <stdlib.h>
int main(char **args, int argc) {
char *test;
test = malloc(10);
test[100] = 1;
return 0;
}
I tested under vmware with debian-etch / etch-backports:
No Problems with:
On a 32bit-System with 2.6.22-3-686 kernel and 2.6.22-4-686 kernel (
both etch-backports)...
On a 64bit-System with 2.6.18-6-amd64 kernel ( debian etch )...
Problem occures with:
On 64bit-System with 2.6.22-3-amd64 and 2.6.22-4-amd64 kernel ( both
etch-backports )
valgrind and gdb version stayed the same during the tests (just
exchanged the kernel which was bootet).
Software on simulated amd64 stayed the same during 64bit tests.
Installed software on simulated 32bit stayed the same during the 32bit
tests, but was diffrent from 64bit-system.
# valgrind --version
valgrind-3.2.1-Debian
# gdb -v
GNU gdb 6.4.90-debian
All this is reproduceable with the standard debian-etch (and
etch-backports) binary packages.
The problem also occures on my real amd64 system.
Any suggestions?
Best Regards,
Stefan Koenig
---
http://www.worldtalk.de --- Rollenspiel Chat
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
