Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@redhat.com>
To: gdb-patches@sourceware.org
Subject: [obv][commit] Eliminate single-use variable LEN in infrun.c
Date: Mon, 17 Sep 2012 07:30:00 -0000	[thread overview]
Message-ID: <20120917125859.6c960d1c@spoyarek> (raw)

Hi,

I have committed the following obvious patch into trunk.

Regards,
Siddhesh

http://sourceware.org/ml/gdb-cvs/2012-09/msg00082.html

===================================================================
RCS file: /cvs/src/src/gdb/ChangeLog,v
retrieving revision 1.14664
retrieving revision 1.14665
diff -u -r1.14664 -r1.14665
--- src/gdb/ChangeLog	2012/09/17 07:15:47	1.14664
+++ src/gdb/ChangeLog	2012/09/17 07:26:54	1.14665
@@ -1,3 +1,8 @@
+2012-09-17  Siddhesh Poyarekar  <siddhesh@redhat.com>
+
+	* infrun.c (restore_infcall_suspend_state): Eliminate single-use
+	variable LEN.
+
 2012-09-17  Jan Kratochvil  <jan.kratochvil@redhat.com>
 
 	PR 14119
===================================================================
RCS file: /cvs/src/src/gdb/infrun.c,v
retrieving revision 1.558
retrieving revision 1.559
diff -u -r1.558 -r1.559
--- src/gdb/infrun.c	2012/09/17 07:09:34	1.558
+++ src/gdb/infrun.c	2012/09/17 07:26:55	1.559
@@ -6777,11 +6777,10 @@
   if (inf_state->siginfo_gdbarch == gdbarch)
     {
       struct type *type = gdbarch_get_siginfo_type (gdbarch);
-      size_t len = TYPE_LENGTH (type);
 
       /* Errors ignored.  */
       target_write (&current_target, TARGET_OBJECT_SIGNAL_INFO, NULL,
-		    inf_state->siginfo_data, 0, len);
+		    inf_state->siginfo_data, 0, TYPE_LENGTH (type));
     }
 
   /* The inferior can be gone if the user types "print exit(0)"


                 reply	other threads:[~2012-09-17  7:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20120917125859.6c960d1c@spoyarek \
    --to=siddhesh@redhat.com \
    --cc=gdb-patches@sourceware.org \
    /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