From: Simon Marchi <simon.marchi@ericsson.com>
To: Pedro Alves <palves@redhat.com>, <gdb-patches@sourceware.org>
Cc: Simon Marchi <simon.marchi@polymtl.ca>
Subject: Re: [PATCH 01/14] Factor out print_unpacked_pointer from generic_val_print
Date: Mon, 27 Jul 2015 18:16:00 -0000 [thread overview]
Message-ID: <55B67557.8060506@ericsson.com> (raw)
In-Reply-To: <55B16081.5010400@redhat.com>
On 15-07-23 05:45 PM, Pedro Alves wrote:
> Line too long. Comment seems stale -- there's no UNRESOLVED_ELTTYPE
> parameter.
>
> Otherwise looks good.
>
> Thanks,
> Pedro Alves
Fixed, here is what I pushed:
From 9f436164d55690a0b3d2e4308bfd8834996b97d1 Mon Sep 17 00:00:00 2001
From: Simon Marchi <simon.marchi@ericsson.com>
Date: Mon, 27 Jul 2015 14:11:18 -0400
Subject: [PATCH] Factor out print_unpacked_pointer from generic_val_print
gdb/ChangeLog:
* valprint.c (generic_val_print): Factor out
print_unpacked_pointer code to ...
(print_unpacked_pointer): ... this new function.
---
gdb/ChangeLog | 6 ++++++
gdb/valprint.c | 48 +++++++++++++++++++++++++++++++-----------------
2 files changed, 37 insertions(+), 17 deletions(-)
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index a03ca35..c36f548 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,9 @@
+2015-07-27 Simon Marchi <simon.marchi@ericsson.com>
+
+ * valprint.c (generic_val_print): Factor out
+ print_unpacked_pointer code to ...
+ (print_unpacked_pointer): ... this new function.
+
2015-07-27 Patrick Palka <patrick@parcs.ath.cx>
* event-top.c (handle_sigterm): Don't inspect
diff --git a/gdb/valprint.c b/gdb/valprint.c
index 52a386a..c643956 100644
--- a/gdb/valprint.c
+++ b/gdb/valprint.c
@@ -359,6 +359,33 @@ val_print_invalid_address (struct ui_file *stream)
fprintf_filtered (stream, _("<invalid address>"));
}
+/* Print a pointer based on the type of its target.
+
+ Arguments to this functions are roughly the same as those in
+ generic_val_print. A difference is that ADDRESS is the address to print,
+ with embedded_offset already added. ELTTYPE represents
+ the pointed type after check_typedef. */
+
+static void
+print_unpacked_pointer (struct type *type, struct type *elttype,
+ CORE_ADDR address, struct ui_file *stream,
+ const struct value_print_options *options)
+{
+ struct gdbarch *gdbarch = get_type_arch (type);
+
+ if (TYPE_CODE (elttype) == TYPE_CODE_FUNC)
+ {
+ /* Try to print what function it points to. */
+ print_function_pointer_address (options, gdbarch, address, stream);
+ return;
+ }
+
+ if (options->symbol_print)
+ print_address_demangle (options, gdbarch, address, stream, demangle);
+ else if (options->addressprint)
+ fputs_filtered (paddress (gdbarch, address), stream);
+}
+
/* A generic val_print that is suitable for use by language
implementations of the la_val_print method. This function can
handle most type codes, though not all, notably exception
@@ -414,7 +441,8 @@ generic_val_print (struct type *type, const gdb_byte *valaddr,
/* Array of unspecified length: treat like pointer to first
elt. */
addr = address + embedded_offset;
- goto print_unpacked_pointer;
+ print_unpacked_pointer (type, elttype, addr, stream, options);
+ break;
case TYPE_CODE_MEMBERPTR:
val_print_scalar_formatted (type, valaddr, embedded_offset,
@@ -430,22 +458,8 @@ generic_val_print (struct type *type, const gdb_byte *valaddr,
}
unresolved_elttype = TYPE_TARGET_TYPE (type);
elttype = check_typedef (unresolved_elttype);
- {
- addr = unpack_pointer (type, valaddr + embedded_offset);
- print_unpacked_pointer:
-
- if (TYPE_CODE (elttype) == TYPE_CODE_FUNC)
- {
- /* Try to print what function it points to. */
- print_function_pointer_address (options, gdbarch, addr, stream);
- return;
- }
-
- if (options->symbol_print)
- print_address_demangle (options, gdbarch, addr, stream, demangle);
- else if (options->addressprint)
- fputs_filtered (paddress (gdbarch, addr), stream);
- }
+ addr = unpack_pointer (type, valaddr + embedded_offset);
+ print_unpacked_pointer (type, elttype, addr, stream, options);
break;
case TYPE_CODE_REF:
--
2.1.4
next prev parent reply other threads:[~2015-07-27 18:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 16:47 [PATCH 00/14] Split generic_val_print in smaller parts Simon Marchi
2015-07-15 16:47 ` [PATCH 06/14] Factor out enum printing code from generic_val_print Simon Marchi
2015-07-15 16:47 ` [PATCH 04/14] Factor out memberptr " Simon Marchi
2015-07-15 16:47 ` [PATCH 01/14] Factor out print_unpacked_pointer " Simon Marchi
2015-07-23 21:45 ` Pedro Alves
2015-07-24 2:29 ` Simon Marchi
2015-07-27 18:16 ` Simon Marchi [this message]
2015-07-15 16:48 ` [PATCH 07/14] Factor out flags printing code " Simon Marchi
2015-07-15 16:48 ` [PATCH 14/14] Factor out complex " Simon Marchi
2015-07-15 16:48 ` [PATCH 08/14] Factor out function/method " Simon Marchi
2015-07-23 21:45 ` Pedro Alves
2015-07-27 18:17 ` Simon Marchi
2015-07-15 16:48 ` [PATCH 11/14] Factor out char " Simon Marchi
2015-07-23 21:46 ` Pedro Alves
2015-07-27 18:17 ` Simon Marchi
2015-07-15 16:48 ` [PATCH 09/14] Factor out bool " Simon Marchi
2015-07-15 16:48 ` [PATCH 02/14] Factor out array " Simon Marchi
2015-07-15 16:48 ` [PATCH 03/14] Factor out pointer " Simon Marchi
2015-07-15 16:48 ` [PATCH 13/14] Factor out decfloat " Simon Marchi
2015-07-15 16:48 ` [PATCH 05/14] Factor out reference " Simon Marchi
2015-07-15 16:48 ` [PATCH 12/14] Factor out float " Simon Marchi
2015-07-23 21:46 ` Pedro Alves
2015-07-27 18:18 ` Simon Marchi
2015-07-15 16:48 ` [PATCH 10/14] Factor out int " Simon Marchi
2015-07-23 21:54 ` [PATCH 00/14] Split generic_val_print in smaller parts Pedro Alves
2015-07-27 18:14 ` Simon Marchi
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=55B67557.8060506@ericsson.com \
--to=simon.marchi@ericsson.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=simon.marchi@polymtl.ca \
/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