Re: Static code analyzer Clang reports possible bug in getopt.c while developing gnu-pdf

2011-06-22 Thread Eric Blake
On 06/22/2011 10:30 AM, Eric Blake wrote: > Thanks for the report. I believe you (well, clang) found an actual > glibc bug! Of course, no one in their right mind ever calls > getopt(argc, argv, "W;"), do they? > > I'm in the process of seeing if I can quickly turn this into an actual > crashing

Re: Static code analyzer Clang reports possible bug in getopt.c while developing gnu-pdf

2011-06-22 Thread Eric Blake
On 06/22/2011 10:07 AM, Gustavo Martin Domato wrote: > Hi: > > I copy something I wrote on gnu-pdf development mailing list. Static > code analyzer Clang detected a possible bug at line 852. The file > they're using is a copy of the source. To see the report go to > http://www.gnupdf.org/prmgt/cla

Static code analyzer Clang reports possible bug in getopt.c while developing gnu-pdf

2011-06-22 Thread Gustavo Martin Domato
Hi: I copy something I wrote on gnu-pdf development mailing list. Static code analyzer Clang detected a possible bug at line 852. The file they're using is a copy of the source. To see the report go to http://www.gnupdf.org/prmgt/clang/report-kFVhsy.html#EndPath "> lib/getopt.c line 852 - This o