From: "Emmanuel Thomé" <Emmanuel.Thome@gmail.com>
To: gdb-patches@sourceware.org
Subject: embedded_offset missing in c-valprint.c
Date: Mon, 05 Jul 2010 01:52:00 -0000 [thread overview]
Message-ID: <20100705015202.GA2419@truffe.loria.fr> (raw)
[-- Attachment #1: Type: text/plain, Size: 905 bytes --]
Hi,
Could you please consider the attached patch to c-valprint.c ?
Unless I am mistaken (which is possible), the function c_val_print does
not correctly track the inferior addresses of struct members. This
affects pretty-printing via python scripting, which may require this
address.
I actually tested the version from the ubuntu package 7.1-1ubuntu2, but
the defect seems also present in the git head version.
Here is an example of a session transcript illustrating the misbehaviour/
$ gdb v
GNU gdb (GDB) 7.1-ubuntu
[...]
(gdb) b 19
Breakpoint 1 at 0x4004fb: file v.c, line 19.
(gdb) r
Starting program: /home/thome/Curves/CM/complex_analytic/regis/v
Breakpoint 1, main () at v.c:19
19 return 0;
(gdb) p x
$1 = {{l = 42, a = {{{x = 0}}, {{x = 1}}}}}
(gdb) source u.py
(gdb) p x
$2 = {{l = 42, a = {42, 0}}}
v.c and u.py are attached (as well as the patch itself of course).
Best,
E.
[-- Attachment #2: v.c --]
[-- Type: text/x-csrc, Size: 221 bytes --]
struct bar {
int x;
};
typedef struct bar xbar[1];
struct foo {
int l;
xbar a[2];
};
int main()
{
struct foo x[1];
x->l = 42;
for(int i = 0 ; i < 2 ; i++)
x->a[i]->x=i;
return 0;
}
[-- Attachment #3: u.py --]
[-- Type: text/x-python, Size: 560 bytes --]
import gdb
from gmpy import mpz,mpf
class bar_printer:
def __init__(self, val):
self.val = val
def to_string(self):
X = self.val
# There's apparently a bug in array member of structs. Their
# starting address seems to be constantly equal to the starting
# address of the struct itself...
return str(int(X['x']))
def make_my_printer_objects(val):
t=str(val.type)
if t == 'struct bar [1]':
return bar_printer(val[0])
return None
gdb.pretty_printers.append(make_my_printer_objects)
[-- Attachment #4: c-valprint-patch --]
[-- Type: text/plain, Size: 415 bytes --]
--- c-valprint.c 2010-07-04 23:06:32.000000000 +0200
+++ /tmp/c-valprint.c 2010-07-05 03:29:39.000000000 +0200
@@ -216,7 +216,7 @@
{
i = 0;
}
- val_print_array_elements (type, valaddr + embedded_offset, address, stream,
+ val_print_array_elements (type, valaddr + embedded_offset, address + embedded_offset, stream,
recurse, options, i);
fprintf_filtered (stream, "}");
}
next reply other threads:[~2010-07-05 1:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-05 1:52 Emmanuel Thomé [this message]
2010-07-14 14:12 ` 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=20100705015202.GA2419@truffe.loria.fr \
--to=emmanuel.thome@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).