On Sun, 2022-02-13 at 17:57 -0500, David Malcolm wrote:
> On Sun, 2022-02-13 at 21:16 +0530, Mir Immad wrote:
> > Hi,
> >
> > I wanted some clarification on bifurcating the exploded graph at
> > call
> > to
> > open().
> > Should the analyzer warn for code like this "when open fails" (like
> > str
On Sun, 2022-02-13 at 21:16 +0530, Mir Immad wrote:
> Hi,
>
> I wanted some clarification on bifurcating the exploded graph at call
> to
> open().
> Should the analyzer warn for code like this "when open fails" (like
> strchr
> does when 'strchr' returns NULL)
>
> int fd = open("NOFILE", O_RDONL
Snapshot gcc-12-20220213 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/12-20220213/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 12 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Hi,
I wanted some clarification on bifurcating the exploded graph at call to
open().
Should the analyzer warn for code like this "when open fails" (like strchr
does when 'strchr' returns NULL)
int fd = open("NOFILE", O_RDONLY);
write(fd, "a", 1);
because of the bad file descriptor.
unless it is
