qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Benjamin <davidben@MIT.EDU>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH] eepro100: Allocate a larger buffer for regname()
Date: Wed, 25 Nov 2009 21:20:10 -0500	[thread overview]
Message-ID: <1259202010-20599-1-git-send-email-davidben@mit.edu> (raw)

This should avoid truncating the register name when debugging.

Signed-off-by: David Benjamin <davidben@mit.edu>
---
 hw/eepro100.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/hw/eepro100.c b/hw/eepro100.c
index 8734907..3676dc0 100644
--- a/hw/eepro100.c
+++ b/hw/eepro100.c
@@ -648,7 +648,7 @@ static const char * const reg[PCI_IO_SIZE / 4] = {
 
 static char *regname(uint32_t addr)
 {
-    static char buf[16];
+    static char buf[32];
     if (addr < PCI_IO_SIZE) {
         const char *r = reg[addr / 4];
         if (r != 0) {
-- 
1.6.3.3

             reply	other threads:[~2009-11-26  2:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-26  2:20 David Benjamin [this message]
2009-11-27  9:31 ` [Qemu-devel] [PATCH] eepro100: Allocate a larger buffer for regname() Stefan Weil

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=1259202010-20599-1-git-send-email-davidben@mit.edu \
    --to=davidben@mit.edu \
    --cc=qemu-devel@nongnu.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 NNTP newsgroup(s).