Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Hui Zhu <teawater@gmail.com>,
	gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [obv] Fix unused-but-set-variable error   [Re: [OB] Fix linux-low.c build error]
Date: Mon, 19 Dec 2011 06:50:00 -0000	[thread overview]
Message-ID: <4EEED8FB.4040103@codesourcery.com> (raw)
In-Reply-To: <20111218205826.GA15385@host2.jankratochvil.net>

On 12/19/2011 04:58 AM, Jan Kratochvil wrote:
> Checked in this alternative fix to not break the next nightly builds.
> 
> I believe it now should pass also on Ubuntu, tested it with artificial
> warn_unused_result attribute for `write'.
> 
> 
> Regards,
> Jan
> 
> 
> http://sourceware.org/ml/gdb-cvs/2011-12/msg00185.html
> 
> --- src/gdb/gdbserver/ChangeLog	2011/12/18 15:49:04	1.529
> +++ src/gdb/gdbserver/ChangeLog	2011/12/18 20:55:08	1.530
> @@ -1,3 +1,11 @@
> +2011-12-18  Jan Kratochvil  <jan.kratochvil@redhat.com>
> +
> +	* linux-low.c (linux_create_inferior): Put empty if clause for write.
> +
> +	Revert:
> +	2011-12-18  Hui Zhu  <teawater@gmail.com>
> +	* linux-low.c (linux_create_inferior): Save return value to ret.
> +

This reminds me that I committed a similar patch some days ago.  Here is a
patch to revert.

-- 
Yao (齐尧) 

	* tracepoint.c (gdb_ust_thread): Put an empty if clause for write.

	Revert:
	2011-12-14  Yao Qi  <yao@codesourcery.com>
	* tracepoint.c (gdb_ust_thread): Don't ignore return value
	of write.

Index: gdb/gdbserver/tracepoint.c
===================================================================
RCS file: /cvs/src/src/gdb/gdbserver/tracepoint.c,v
retrieving revision 1.38
diff -u -r1.38 tracepoint.c
--- gdb/gdbserver/tracepoint.c	15 Dec 2011 12:40:03 -0000	1.38
+++ gdb/gdbserver/tracepoint.c	19 Dec 2011 06:17:49 -0000
@@ -8122,8 +8122,8 @@
 		strcpy (cmd_buf, "");
 	    }
 
-	  /* Fix compiler's warning: ignoring return value of 'write'.  */
-	  ret = write (fd, buf, 1);
+	  if (write (fd, buf, 1) < 0)
+	    /* Errors ignored.  */;
 	  close (fd);
 	}
     }


  parent reply	other threads:[~2011-12-19  6:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-18 16:05 [OB] Fix linux-low.c build error Hui Zhu
2011-12-18 20:58 ` Jan Kratochvil
2011-12-18 22:55   ` [obv] Fix unused-but-set-variable error [Re: [OB] Fix linux-low.c build error] Jan Kratochvil
2011-12-19  3:22     ` Hui Zhu
2011-12-19  3:34     ` Joel Brobecker
2011-12-19  6:50     ` Yao Qi [this message]
2011-12-19  6:53       ` Joel Brobecker
2011-12-19  8:13         ` Yao Qi
2011-12-19  9:32           ` Joel Brobecker
2011-12-19 10:23       ` Jan Kratochvil

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=4EEED8FB.4040103@codesourcery.com \
    --to=yao@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=teawater@gmail.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