public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@vmware.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: [RFA] gdbserver support for qCRC: (compare-sections)
Date: Fri, 19 Mar 2010 23:27:00 -0000	[thread overview]
Message-ID: <4BA40867.4090703@vmware.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 292 bytes --]

This patch adds support to gdbserver for the "qCRC:" request.

This in turn supports the gdb "compare-sections" command, which
basically lets you verify that the binary image on the target
matches the executable that you're debugging.

I borrowed code from gdb/remote.c, I assume that's OK.


[-- Attachment #2: qcrc.txt --]
[-- Type: text/plain, Size: 1954 bytes --]

2010-03-19  Michael Snyder  <msnyder@vmware.com>

	* server.c (crc32): New function.
	(handle_query): Add handling for 'qCRC:' request.

Index: server.c
===================================================================
RCS file: /cvs/src/src/gdb/gdbserver/server.c,v
retrieving revision 1.108
diff -u -p -r1.108 server.c
--- server.c	20 Jan 2010 22:55:38 -0000	1.108
+++ server.c	19 Mar 2010 23:23:15 -0000
@@ -788,6 +788,40 @@ handle_threads_qxfer (const char *annex,
 
 }
 
+/* Table used by the crc32 function to calcuate the checksum.  */
+
+static unsigned long crc32_table[256] =
+{0, 0};
+
+static unsigned long
+crc32 (CORE_ADDR base, int len, unsigned int crc)
+{
+  if (!crc32_table[1])
+    {
+      /* Initialize the CRC table and the decoding table.  */
+      int i, j;
+      unsigned int c;
+
+      for (i = 0; i < 256; i++)
+	{
+	  for (c = i << 24, j = 8; j > 0; --j)
+	    c = c & 0x80000000 ? (c << 1) ^ 0x04c11db7 : (c << 1);
+	  crc32_table[i] = c;
+	}
+    }
+
+  while (len--)
+    {
+      unsigned char byte = 0;
+
+      /* Fixme -- no error checking.  */
+      read_inferior_memory (base, &byte, 1);
+      crc = (crc << 8) ^ crc32_table[((crc >> 24) ^ byte) & 255];
+      base++;
+    }
+  return crc;
+}
+
 /* Handle all of the extended 'q' packets.  */
 void
 handle_query (char *own_buf, int packet_len, int *new_packet_len_p)
@@ -1421,6 +1455,23 @@ handle_query (char *own_buf, int packet_
       return;
     }
 
+  if (strncmp ("qCRC:", own_buf, 5) == 0)
+    {
+      /* CRC check (compare-segment).  */
+      char *comma;
+      CORE_ADDR base = strtoul (own_buf + 5, &comma, 16);
+      int len;
+
+      if (*comma++ != ',')
+	{
+	  write_enn (own_buf);
+	  return;
+	}
+      len = strtoul (comma, NULL, 16);
+      sprintf (own_buf, "C%lx", crc32 (base, len, 0xffffffff));
+      return;
+    }
+
   /* Otherwise we didn't know what packet it was.  Say we didn't
      understand it.  */
   own_buf[0] = 0;

             reply	other threads:[~2010-03-19 23:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-19 23:27 Michael Snyder [this message]
2010-03-22 17:59 ` Michael Snyder
2010-03-23 16:26   ` Pedro Alves
2010-03-23 18:16     ` Michael Snyder
2010-03-23 18:32       ` Pedro Alves
2010-03-23 22:44         ` Michael Snyder
2010-03-23 23:15           ` Pedro Alves
2010-03-24  0:16             ` Pedro Alves
2010-03-24  0:34               ` Michael Snyder
2010-03-24  1:15         ` Pedro Alves

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=4BA40867.4090703@vmware.com \
    --to=msnyder@vmware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).