On Tue, 26 Jun 2001, Christoph Reichenbach wrote:
> > Result:
> > An invalid memory access occurs @ sci_resmgr.c(114). This happened with
> > the same call stack on both win32 and Linux.
>
> Does the tool you're using provide traces with function parameters, too?
>From gdb (VC++'s debugger shows similar):
#0 0x402d6e3f in memcpy (dstpp=0x3, srcpp=0x405b3008, len=256000)
at ../sysdeps/generic/memcpy.c:44
#1 0x0809b061 in gfxr_interpreter_calculate_pic (state=0x83cb488,
scaled_pic=0x8595980, unscaled_pic=0x85b4da8, flags=1,
default_palette=0,
nr=21) at sci_resmgr.c:114
#2 0x080924a6 in gfxr_get_pic (state=0x83cb488, nr=21, maps=1, flags=1,
default_palette=0, scaled=1) at resmgr.c:306
#3 0x08090f95 in gfxop_new_pic (state=0x80d7340, nr=21, flags=1,
default_palette=0) at operations.c:1738
#4 0x08070301 in kDrawPic (s=0x8406cf0, funct_nr=8, argc=2, argp=29760)
at kgraphics.c:1137
#5 0x0805238b in run_vm (s=0x8406cf0, restoring=0) at vm.c:769
--
http://www.clock.org/~matt
