On Thu, Nov 02, 2006 at 12:09:52AM -0300, [EMAIL PROTECTED] wrote:
> I have just asked a friend who uses Debian on amd64 too to install and
> test the software, and the exact same error happens. Then, it is not
> unreproducible. It should be a bug only present on 64bits architectures,
> however. In which one did you try the games?
Sure enough, I can reproduce the segfault on amd64; I was testing on i386
before.
Here is a backtrace from a version of ire built with debugging symbols:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 47388434000368 (LWP 18300)]
0x0000000000430852 in GET_INT () at pe/pe_vm.cpp:407
407 return (*curvm->ip++).u8;
(gdb) bt
#0 0x0000000000430852 in GET_INT () at pe/pe_vm.cpp:407
#1 0x0000000000430837 in GET_INT () at pe/pe_vm.cpp:797
#2 0x0000000000434dc8 in PV_PicScroll () at pe/pe_vm.cpp:5338
#3 0x0000000000431972 in microkernel () at pe/pe_vm.cpp:1498
#4 0x0000000000422e15 in ForceDropObject (x=129, y=14, object=0x10b0530)
at object.cpp:472
#5 0x00000000004233ad in MoveToMap (x=129, y=14, object=0x10b0530)
at object.cpp:360
#6 0x000000000041549c in load_z1 (fname=<value optimized out>)
at loadsave.cpp:591
#7 0x0000000000416fba in LoadMap (mapnum=1) at loadsave.cpp:117
#8 0x0000000000409b90 in _mangled_main (argc=3, argv=0x7fff31d06438)
at ire.cpp:363
#9 0x00002b197a72e4ca in __libc_start_main () from /lib/libc.so.6
#10 0x0000000000000000 in ?? ()
(gdb) print curvm
$1 = (PEVM *) 0x6119a0
(gdb) print curvm->ip
$3 = (VMTYPE *) 0x8
Probably a straightforward int/pointer type error. I'll look at the build
logs.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
[EMAIL PROTECTED] http://www.debian.org/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
