>>>>> "CC" == Congcong <
zongn...@gmail.com> writes:
CC> Hi all
CC> i am using ubuntu 10.04 x64 server
CC> when i compiled temu-1.0, it displayed many warnings about
CC> ../taintcheck.h:149: warning: `fastcall' attribute ignored
CC> ../taintcheck.h:150: warning: `fastcall' attribute ignored
CC> ../taintcheck.h:153: warning: `fastcall' attribute ignored
CC> ../taintcheck.h:154: warning: `fastcall' attribute ignored
CC> ../taintcheck.h:156: warning: `fastcall' attribute ignored
CC> ../taintcheck.h:157: warning: `fastcall' attribute ignored
CC> ../taintcheck.h:158: warning: `fastcall' attribute ignored
CC> ../taintcheck.h:159: warning: `fastcall' attribute ignored
CC> ../taintcheck.h:160: warning: `fastcall' attribute ignored
CC> ../taintcheck.h:161: warning: `fastcall' attribute ignored
CC> ../taintcheck.h:162: warning: `fastcall' attribute ignored
CC> ../taintcheck.h:163: warning: `fastcall' attribute ignored
CC> ../taintcheck.h:164: warning: `fastcall' attribute ignored
CC> ../taintcheck.h:198: warning: `fastcall' attribute ignored
CC> ../taintcheck.h:215: warning: `fastcall' attribute ignored
CC> ../taintcheck.h:218: warning: `fastcall' attribute ignored
Though the volume of them is a little annoying, these warnings are not
the cause of the problem. In fact the default calling convention for
64-bit Linux corresponds to what's called "fastcall" on 32-bit. You
can remove the attributes if you don't like seeing the warnings.
CC> when i try to run temu, it always crash and displays
CC> (qemu) ./winxp.sh: line 8: 12172 Segmentation fault
CC> /home/zongnan/bitblaze/temu-1.0/tracecap/temu -snapshot -net nic,vlan=0
CC> -net tap,vlan=0,script=/etc/qemu-ifup -smb /home/zongnan/bitblaze/share
CC> -monitor stdio /home/zongnan/bitblaze/winxp.img
CC> however, when i use it on 32 bit system, i have never came across
CC> this problem, so could anyone please tell me what i should
CC> proceed?
This crash has a different cause, which I discussed in more detail in
an old message that included a patch:
https://groups.google.com/forum/?fromgroups=#!topic/bitblaze-users/3_9Zqamg7Bk
The fix is also included in the build instructions I sent to the list
a few minutes ago.
Hope this helps,
-- Stephen