From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 4/8] remove some stale FIXMEs
Date: Wed, 27 Nov 2013 17:21:00 -0000 [thread overview]
Message-ID: <8761rd3h8h.fsf@fleche.redhat.com> (raw)
In-Reply-To: <87vbzd3nwa.fsf@fleche.redhat.com> (Tom Tromey's message of "Wed, 27 Nov 2013 07:44:21 -0700")
Tom> I'll fix it.
Here's a new version.
Tom
commit 370f78a0c0bdb770d21abc3dccb61da4ed3574eb
Author: Tom Tromey <tromey@redhat.com>
Date: Mon Nov 25 08:47:51 2013 -0700
fix a couple of FIXMEs
This fixes a couple of old "32x64" FIXME comments by using paddress
with current_gdbarch rather than hex_string and a cast to long.
2013-11-26 Tom Tromey <tromey@redhat.com>
* cli/cli-cmds.c (edit_command): Use paddress, not hex_string.
(list_command): Likewise.
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 0bda3bb..d059474 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,5 +1,10 @@
2013-11-26 Tom Tromey <tromey@redhat.com>
+ * cli/cli-cmds.c (edit_command): Use paddress, not hex_string.
+ (list_command): Likewise.
+
+2013-11-26 Tom Tromey <tromey@redhat.com>
+
* psymtab.c (allocate_psymtab): Put the filename in the filename
bcache.
diff --git a/gdb/cli/cli-cmds.c b/gdb/cli/cli-cmds.c
index 85f1713..52a6bc9 100644
--- a/gdb/cli/cli-cmds.c
+++ b/gdb/cli/cli-cmds.c
@@ -817,9 +817,8 @@ edit_command (char *arg, int from_tty)
struct gdbarch *gdbarch;
if (sal.symtab == 0)
- /* FIXME-32x64--assumes sal.pc fits in long. */
error (_("No source file for address %s."),
- hex_string ((unsigned long) sal.pc));
+ paddress (get_current_arch (), sal.pc));
gdbarch = get_objfile_arch (sal.symtab->objfile);
sym = find_pc_function (sal.pc);
@@ -982,9 +981,8 @@ list_command (char *arg, int from_tty)
struct gdbarch *gdbarch;
if (sal.symtab == 0)
- /* FIXME-32x64--assumes sal.pc fits in long. */
error (_("No source file for address %s."),
- hex_string ((unsigned long) sal.pc));
+ paddress (get_current_arch (), sal.pc));
gdbarch = get_objfile_arch (sal.symtab->objfile);
sym = find_pc_function (sal.pc);
next prev parent reply other threads:[~2013-11-27 17:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-26 21:50 [PATCH 0/8] trivia Tom Tromey
2013-11-26 21:50 ` [PATCH 2/8] make symtab::dirname const Tom Tromey
2013-11-26 21:57 ` [PATCH 1/8] make symtab::filename const Tom Tromey
2013-11-26 22:12 ` [PATCH 3/8] put the psymtab filename in the filename bcache Tom Tromey
2013-11-26 22:27 ` [PATCH 8/8] update free_objfile comment Tom Tromey
2013-11-26 22:37 ` [PATCH 7/8] remove objfile_to_front Tom Tromey
2013-11-26 22:44 ` [PATCH 5/8] pack partial_symtab for space Tom Tromey
2013-11-27 8:34 ` [PATCH 6/8] remove unnecessary declaration Tom Tromey
2013-11-27 9:49 ` [PATCH 4/8] remove some stale FIXMEs Tom Tromey
2013-11-27 12:25 ` Pedro Alves
2013-11-27 15:56 ` Tom Tromey
2013-11-27 17:21 ` Tom Tromey [this message]
2013-11-27 17:52 ` Pedro Alves
2013-12-06 19:12 ` [PATCH 0/8] trivia Tom Tromey
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=8761rd3h8h.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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