Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Christian Biesinger via gdb-patches" <gdb-patches@sourceware.org>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: Christian Biesinger via gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix compiler warning in linux-namespaces.c
Date: Tue, 27 Aug 2019 18:54:00 -0000	[thread overview]
Message-ID: <CAPTJ0XEE+_KFd_iA2Vn4Yj-8RYCt6iP_8_9JSmCvzA0GS19A9g@mail.gmail.com> (raw)
In-Reply-To: <87ftlmfo20.fsf@redhat.com>

On Tue, Aug 27, 2019 at 1:42 PM Sergio Durigan Junior
<sergiodj@redhat.com> wrote:
>
> On Tuesday, August 27 2019, Christian Biesinger via gdb-patches wrote:
>
> > ../../gdb/nat/linux-namespaces.c: In function ‘void mnsh_main(int)’:
> > ../../gdb/nat/linux-namespaces.c:604:8: warning: ‘fd’ may be used uninitialized in this function [-Wmaybe-uninitialized]
> >   close (fd);
> >   ~~~~~~^~~~
> >
> > And the warning is correct -- mnsh_recv_message can return -1 and leave fd
> > uninitialized, and mnsh_main will still call close (fd) if that happens.
> >
> > Initialize fd to -1 to avoid that.
>
> Thanks.  IMO this patch could be treated as obvious.

Thanks, fixed the typo below and pushed as obvious.

> > gdb/ChangeLog:
> >
> > 2019-08-27  Christian Biesinger  <cbiesinger@google.com>
> >
> >       * nat/linux-namespaces.c (mnsh_main): Initialize fd (to -1).
> > ---
> >  gdb/nat/linux-namespaces.c | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/gdb/nat/linux-namespaces.c b/gdb/nat/linux-namespaces.c
> > index 503f755903..57843cda36 100644
> > --- a/gdb/nat/linux-namespaces.c
> > +++ b/gdb/nat/linux-namespaces.c
> > @@ -562,14 +562,14 @@ mnsh_main (int sock)
> >    while (1)
> >      {
> >        enum mnsh_msg_type type;
> > -      int fd, int1, int2;
> > +      int fd = -1, int1, int2;
> >        char buf[PATH_MAX];
> >        ssize_t size, response = -1;
> >
> >        size = mnsh_recv_message (sock, &type,
> >                               &fd, &int1, &int2,
> >                               buf, sizeof (buf));
> > -
> > +`
>
> This seems like a typo.
>
> >        if (size >= 0 && size < sizeof (buf))
> >       {
> >         switch (type)
> > --
> > 2.23.0.187.g17f5b7556c-goog
>
> Cheers,
>
> --
> Sergio
> GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
> Please send encrypted e-mail if possible
> http://sergiodj.net/


      reply	other threads:[~2019-08-27 18:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-27 18:25 Christian Biesinger via gdb-patches
2019-08-27 18:42 ` Sergio Durigan Junior
2019-08-27 18:54   ` Christian Biesinger via gdb-patches [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAPTJ0XEE+_KFd_iA2Vn4Yj-8RYCt6iP_8_9JSmCvzA0GS19A9g@mail.gmail.com \
    --to=gdb-patches@sourceware.org \
    --cc=cbiesinger@google.com \
    --cc=sergiodj@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox