On Sat, Apr 28, 2012 at 9:43 AM, Mahmood Naderan <mahmood...@gmail.com>wrote:
> why the 'length' is so much large? > That is indeed the question. My guess is that there's some bug in the way we're interpreting the syscall arguments being passed in from the application (via registers or on the stack). You could use strace on the application running natively to see what the mmap arguments should be. Then it's mostly a matter of poking around to see at what point things are getting confused about the value. Do the register contents look right on entry to the syscall? What is getSyscallArg doing, and where is it getting that ridiculous value from? At this point, there's probably no substitute for single-stepping through some of this code with gdb. I'm not familiar enoiugh with the x86 ABI to say off the top of my head where that argument is being passed. Anyone? Steve
_______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
