From: Luis Gustavo <luis_gustavo@mentor.com>
To: gdb-patches@sourceware.org
Subject: [PATCH] Fix mi "-var-create" regression
Date: Wed, 10 Oct 2012 20:05:00 -0000 [thread overview]
Message-ID: <5075D4FD.9050900@mentor.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1407 bytes --]
Hi,
After the commit that fixed #13393
(http://sourceware.org/bugzilla/show_bug.cgi?id=13393), certain calls to
-var-create with "set print object on" started failing with a
dereferencing error, like so:
(gdb)
-var-create - * $sp
^error,msg="Attempt to dereference a generic pointer."
(gdb)
This happens because in value.c:value_actual_type we have this check:
if (TYPE_CODE (result) == TYPE_CODE_PTR
|| TYPE_CODE (result) == TYPE_CODE_REF)
{
struct type *real_type;
real_type = value_rtti_indirect_type (value, NULL, NULL, NULL);
if (real_type)
{
if (real_type_found)
*real_type_found = 1;
result = real_type;
}
}
If we reach this point with result being a pointer of reference, we
execute the if block. This will eventually lead to a call to
valops.c:get_value_at, where we throw an error in case the target type
is void (pointers usually have such a target type)
Anton does mention a particular problem with indirect pointers in #13393
comment #8, but it is not clear if a bug ticket has been filed for that.
The following patch adds a check for target type void, and skips the
problematic if block accordingly. This fixes the problem and does not
seem to cause any regressions.
With "set print object off", everything works as it should.
Ok?
[-- Attachment #2: rtti-print-object.diff --]
[-- Type: text/x-patch, Size: 951 bytes --]
2012-10-10 Luis Machado <lgustavo@codesourcery.com>
* value.c (value_actual_type): Check for TYPE_CODE_VOID
target types.
Index: gdb/gdb/value.c
===================================================================
--- gdb.orig/gdb/value.c 2012-10-10 16:38:21.872234906 -0300
+++ gdb/gdb/value.c 2012-10-10 16:42:49.560222099 -0300
@@ -850,8 +850,13 @@ value_actual_type (struct value *value,
result = value_type (value);
if (opts.objectprint)
{
- if (TYPE_CODE (result) == TYPE_CODE_PTR
+ /* If result's target type is TYPE_CODE_VOID, do not try fetching its rtti
+ type. GDB will try to dereference the void pointer and will throw an
+ error when trying to do so. */
+ if ((TYPE_CODE (result) == TYPE_CODE_PTR
|| TYPE_CODE (result) == TYPE_CODE_REF)
+ && ((TYPE_TARGET_TYPE (result) != NULL)
+ && TYPE_CODE (TYPE_TARGET_TYPE (result)) != TYPE_CODE_VOID))
{
struct type *real_type;
next reply other threads:[~2012-10-10 20:05 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-10 20:05 Luis Gustavo [this message]
2012-10-11 21:53 ` Sergio Durigan Junior
2012-10-11 22:10 ` Luis Machado
2012-10-17 17:29 ` Tom Tromey
2012-10-12 19:57 ` Marc Khouzam
2012-10-14 17:18 ` Joel Brobecker
2012-10-15 12:21 ` Luis Machado
2012-10-18 1:13 ` Tom Tromey
2012-10-19 13:14 ` Luis Machado
2012-10-28 22:44 ` Luis Machado
2012-10-30 20:36 ` Tom Tromey
2012-11-14 19:21 ` Luis Machado
2012-11-15 16:44 ` Marc Khouzam
2012-11-15 17:48 ` Joel Brobecker
2012-11-15 18:47 ` Tom Tromey
2012-11-15 20:54 ` Marc Khouzam
2012-11-15 21:13 ` Tom Tromey
2012-11-15 23:28 ` Luis Machado
2012-11-16 0:50 ` Marc Khouzam
2012-11-16 2:10 ` Luis Machado
2012-11-29 20:11 ` Andreas Schwab
2012-11-29 21:07 ` Joel Brobecker
2012-11-30 2:13 ` Luis Machado
2012-12-07 2:48 ` Joel Brobecker
2012-12-07 2:51 ` Luis Machado
2012-12-26 12:31 ` Luis Machado
2013-01-03 3:46 ` Joel Brobecker
2013-01-03 12:30 ` Luis Machado
2013-01-03 12:38 ` Joel Brobecker
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=5075D4FD.9050900@mentor.com \
--to=luis_gustavo@mentor.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