Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	vinschen@redhat.com
Subject: Re: [rfa] remote-fileio.c, remote_fileio_func_fstat, uninitialized st.st_ino.
Date: Thu, 03 Mar 2011 04:37:00 -0000	[thread overview]
Message-ID: <20110303043643.GV30306@adacore.com> (raw)
In-Reply-To: <4D6EBB4A.9080207@vmware.com>

> 2011-03-02  Michael Snyder  <msnyder@vmware.com>
> 
> 	* remote-fileio.c (remote_fileio_func_fstat): Initialize st_ino
> 	to zero.

FWIW: The initialization is made for the case where the file descriptor
is not a file, so we should be ablet to deduce that the st_ino (inode ID)
is irrelevant and not used on the consumer side... This would suggest
that your change is correct. (you should still wait for Corinna to
comment)

> Index: remote-fileio.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/remote-fileio.c,v
> retrieving revision 1.40
> diff -u -p -u -p -r1.40 remote-fileio.c
> --- remote-fileio.c	25 Jan 2011 11:54:00 -0000	1.40
> +++ remote-fileio.c	2 Mar 2011 21:41:48 -0000
> @@ -1175,6 +1175,7 @@ remote_fileio_func_fstat (char *buf)
>        remote_fileio_to_fio_uint (1, fst.fst_dev);
>        st.st_mode = S_IFCHR | (fd == FIO_FD_CONSOLE_IN ? S_IRUSR : S_IWUSR);
>        st.st_nlink = 1;
> +      st.st_ino = 0;
>  #ifdef HAVE_GETUID
>        st.st_uid = getuid ();
>  #else


-- 
Joel


  reply	other threads:[~2011-03-03  4:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-02 21:49 Michael Snyder
2011-03-03  4:37 ` Joel Brobecker [this message]
2011-03-03  8:29   ` Corinna Vinschen
2011-03-03  9:25     ` Joel Brobecker
2011-03-03 10:04       ` Pedro Alves
2011-03-03 10:51         ` Corinna Vinschen
2011-03-03 17:22           ` Michael Snyder
2011-03-03 17:35             ` Corinna Vinschen
2011-03-03 18:36               ` Michael Snyder

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=20110303043643.GV30306@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.com \
    --cc=vinschen@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