Date: Wed, 25 Apr 2012 23:13:06 +0400 From: Boris Samorodov <bsam@passap.ru> To: Dimitry Andric <dim@FreeBSD.org> Cc: freebsd-current@freebsd.org, =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= <dumbbell@FreeBSD.org> Subject: Re: segfault in vfscanf(3): clang and __restrict usage Message-ID: <4F984CC2.5080404@passap.ru> In-Reply-To: <4F98492D.8070006@FreeBSD.org> References: <4F9703C9.8080503@FreeBSD.org> <4F98492D.8070006@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
25.04.2012 22:57, Dimitry Andric пишет: > On 2012-04-24 21:49, Jean-Sébastien Pédron wrote: >> Hi everyone, >> >> vfscanf(3) in HEAD (r234606) segfaults when compiled with clang. For >> instance, here is a call made in cmake which crashes: >> fscanf(f, "%*[^\n]\n"); > > Using r234549 here, everything compiled with clang, but I cannot make > that statement crash, whatever I do. Do you have a specific input file > which crashes it? ----- % uname -a FreeBSD bsam.wart.ru 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r234635: Tue Apr 24 11:41:32 SAMT 2012 bsam@bsam.wart.ru:/usr/obj/usr/src/sys/BBX i386 % sudo gdb smartd smartd.core GNU gdb 6.1.1 [FreeBSD] [...] #0 0x33ebdc2e in vfscanf () from /lib/libc.so.7 (gdb) ----- I think that cupsd also suffer from the bug. BTW, I have the system and almost all ports compiled (tomorrow and today) with clang. -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F984CC2.5080404>