From: Pedro Alves <palves@redhat.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: Udma Catalin-Dan-B32721 <B32721@freescale.com>
Subject: Re: gdb 7.6: Fix info mem command for 32 bits host/64 bits target
Date: Wed, 26 Jun 2013 16:11:00 -0000 [thread overview]
Message-ID: <51CB11D6.1020306@redhat.com> (raw)
In-Reply-To: <51CB116D.7060009@redhat.com>
BTW,
$ grep hex_string_custom * | grep long
finds:
breakpoint.c: /* The longest string possibly returned by hex_string_custom
breakpoint.c: strcpy (astr1, hex_string_custom ((unsigned long) from_addr, 8));
breakpoint.c: strcpy (astr2, hex_string_custom ((unsigned long) to_addr, 8));
Those casts are likewise bogus:
static void
breakpoint_adjustment_warning (CORE_ADDR from_addr, CORE_ADDR to_addr,
int bnum, int have_bnum)
{
/* The longest string possibly returned by hex_string_custom
is 50 chars. These must be at least that big for safety. */
char astr1[64];
char astr2[64];
strcpy (astr1, hex_string_custom ((unsigned long) from_addr, 8));
strcpy (astr2, hex_string_custom ((unsigned long) to_addr, 8));
if (have_bnum)
warning (_("Breakpoint %d address previously adjusted from %s to %s."),
bnum, astr1, astr2);
else
warning (_("Breakpoint address adjusted from %s to %s."), astr1, astr2);
}
--
Pedro Alves
next prev parent reply other threads:[~2013-06-26 16:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-26 15:10 Udma Catalin-Dan-B32721
2013-06-26 16:07 ` Pedro Alves
2013-06-26 16:11 ` Pedro Alves [this message]
2013-06-26 16:17 ` Pedro Alves
2013-06-26 17:11 ` Tom Tromey
2013-06-26 16:20 ` Udma Catalin-Dan-B32721
2013-06-27 8:42 ` Udma Catalin-Dan-B32721
2013-06-27 8:44 ` 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=51CB11D6.1020306@redhat.com \
--to=palves@redhat.com \
--cc=B32721@freescale.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