From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sourceware.org
Subject: [patch] printf "%p" gdb internal error fix
Date: Sun, 10 Sep 2006 17:20:00 -0000 [thread overview]
Message-ID: <20060910172037.GA3886@host0.dyn.jankratochvil.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 469 bytes --]
Hi,
(gdb) printf "%p\n", (void *) 7
internal error in printf_command
Before 6.5 and after patching the regression:
(gdb) printf "%p\n", (void *) 7
0x7
Bugreport by the courtesy of Akira TAGOH <tagoh(at)redhat.com>.
2006-09-10 Jan Kratochvil <jan.kratochvil@redhat.com>
* printcmd.c (printf_command): Handle forgotten "%p".
2006-09-10 Jan Kratochvil <jan.kratochvil@redhat.com>
* gdb.base/display.exp: New test of `printf' "%p" formatting.
Regards,
Jan
[-- Attachment #2: gdb-printf-p.patch --]
[-- Type: text/plain, Size: 1376 bytes --]
Index: printcmd.c
===================================================================
RCS file: /cvs/src/src/gdb/printcmd.c,v
retrieving revision 1.98
diff -u -p -r1.98 printcmd.c
--- printcmd.c 17 Jul 2006 22:15:55 -0000 1.98
+++ printcmd.c 10 Sep 2006 17:14:48 -0000
@@ -2077,6 +2077,12 @@ printf_command (char *arg, int from_tty)
printf_filtered (current_substring, val);
break;
}
+ case ptr_arg:
+ {
+ void *val = (void *) value_as_long (val_args[i]);
+ printf_filtered (current_substring, val);
+ break;
+ }
default:
internal_error (__FILE__, __LINE__,
_("failed internal consitency check"));
Index: testsuite/gdb.base/display.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/display.exp,v
retrieving revision 1.8
diff -u -p -r1.8 display.exp
--- testsuite/gdb.base/display.exp 10 Aug 2006 05:27:20 -0000 1.8
+++ testsuite/gdb.base/display.exp 10 Sep 2006 17:14:48 -0000
@@ -179,6 +179,8 @@ gdb_test "printf \"\\\\!\\a\\f\\r\\t\\v\
gdb_test "printf \"\"" ".*" "re-set term"
gdb_test "printf \"\\w\"" ".*Unrecognized escape character.*"
gdb_test "printf \"%d\" j" ".*Invalid argument syntax.*"
+# 0 or hex vs. dec printing may be platform dependent:
+gdb_test "printf \"<%p>\\n\", (void *)7" ".*7>.*"
# play with "print", too
#
next reply other threads:[~2006-09-10 17:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-10 17:20 Jan Kratochvil [this message]
2006-09-10 19:31 ` Mark Kettenis
2006-09-10 22:00 ` Daniel Jacobowitz
2007-09-04 14:19 ` Daniel Jacobowitz
2007-09-04 20:43 ` Eli Zaretskii
2007-09-04 20:53 ` Daniel Jacobowitz
2007-09-15 9:00 ` Eli Zaretskii
2007-09-15 13:52 ` Daniel Jacobowitz
2007-09-15 14:55 ` Andreas Schwab
2007-09-15 15:16 ` Eli Zaretskii
2007-09-15 15:18 ` Eli Zaretskii
2007-09-15 16:12 ` Daniel Jacobowitz
2007-09-15 18:12 ` Eli Zaretskii
2007-09-15 18:40 ` Daniel Jacobowitz
2007-09-15 21:59 ` Eli Zaretskii
2007-09-15 22:17 ` Daniel Jacobowitz
2007-09-15 16:21 ` Joseph S. Myers
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=20060910172037.GA3886@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@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