Now it looks like wider problem - #571532, #571542, #571397.
Does ant actually try to mmap stdin? That's a bug in ant.
POSIX says you may only mmap a file, shared memory object,
or typed memory object. The stdin file descriptor is neither
of those things therefore you can't mmap stdin.
No, no, no. Not in my example:
gcc tst.c -o tst
tst < tst.c
My point is a different one, see in #570889.
14997 gij-4.4 CALL open(0x8e59e58,O_RDONLY|O_LARGEFILE,<unused>0)
14997 gij-4.4 NAMI ".../defaults.properties"
14997 gij-4.4 RET open 10/0xa
14997 gij-4.4 CALL fstat(0xa,0xbfbf29ec)
14997 gij-4.4 STRU size=1701
14997 gij-4.4 RET fstat 0
14997 gij-4.4 CALL mmap(0,0x2000,PROT_READ,MAP_PRIVATE,0xa,0,0)
14997 gij-4.4 RET mmap 712716288/0x2a7b3000
14997 gij-4.4 PSIG SIGBUS SIG_DFL
The ant/gij-4.4 mmaps 8192 bytes from file of size 1701
on architecture with pagesize 4096.
It is at least weird, possible consequences are demonstrated
by my tst.c example.
Petr
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/pine.lnx.4.62.1002260903500.9...@sci.felk.cvut.cz
