From: Vladimir Prus <vladimir@codesourcery.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: Regression: field type preservation: 7.0 -> 7.0.1+HEAD
Date: Sat, 02 Jan 2010 10:08:00 -0000 [thread overview]
Message-ID: <201001021308.19130.vladimir@codesourcery.com> (raw)
In-Reply-To: <20100101184505.GA18391@host0.dyn.jankratochvil.net>
On Friday 01 January 2010 21:45:05 Jan Kratochvil wrote:
> Hi,
>
> there is now:
> -PASS: gdb.mi/mi-var-child.exp: get children of struct_declarations.s2.u2.u1s1
> +FAIL: gdb.mi/mi-var-child.exp: get children of struct_declarations.s2.u2.u1s1
> -PASS: gdb.mi/mi2-var-child.exp: get children of struct_declarations.s2.u2.u1s1
> +FAIL: gdb.mi/mi2-var-child.exp: get children of struct_declarations.s2.u2.u1s1
> -PASS: gdb.python/py-mi.exp: examine container children=0, no pretty-printing
> +FAIL: gdb.python/py-mi.exp: examine container children=0, no pretty-printing
>
> due to:
> Re: RFA: unbreak typedefed bitfield
> http://sourceware.org/ml/gdb-patches/2009-12/msg00295.html
> commit fc85da4ee2a7c32afc53b1b334a4f84e2e9bd84e
> http://sourceware.org/ml/gdb-cvs/2009-12/msg00100.html
> Author: Vladimir Prus <vladimir@codesourcery.com>
> Date: Mon Dec 21 09:50:26 2009 +0000
> PR gdb/10884
> * value.c (value_primitive_field): Call check_typedef
> on the type.
>
> which has landed on gdb_7_0-branch for 7.0.1:
> http://sourceware.org/ml/gdb-patches/2009-12/msg00301.html
> Author: Joel Brobecker <brobecker@gnat.com>
> commit 259702e4c806baf8ba483484ceec8feb94a39a64
> http://sourceware.org/ml/gdb-cvs/2009-12/msg00104.html
> commit f3f5ad7561d2206b09ef30df979ef58dd014543b
> http://sourceware.org/ml/gdb-cvs/2009-12/msg00103.html
>
> PASS: ^done,numchild="4",children=[child={name="struct_declarations.s2.u2.u1s1.d",exp="d",numchild="0",type="int",thread-id="1"},child={name="struct_declarations.s2.u2.u1s1.e",exp="e",numchild="10",type="char [10]",thread-id="1"},child={name="struct_declarations.s2.u2.u1s1.func",exp="func",numchild="0",type="int *(*)(void)",thread-id="1"},child={name="struct_declarations.s2.u2.u1s1.foo",exp="foo",numchild="0",type="efoo",thread-id="1"}],has_more="0"
> FAIL: ^done,numchild="4",children=[child={name="struct_declarations.s2.u2.u1s1.d",exp="d",numchild="0",type="int",thread-id="1"},child={name="struct_declarations.s2.u2.u1s1.e",exp="e",numchild="10",type="char [10]",thread-id="1"},child={name="struct_declarations.s2.u2.u1s1.func",exp="func",numchild="0",type="int *(*)(void)",thread-id="1"},child={name="struct_declarations.s2.u2.u1s1.foo",exp="foo",numchild="0",type="enum foo",thread-id="1"}],has_more="0"
> wdiff:^done,numchild="4",children=[child={name="struct_declarations.s2.u2.u1s1.d",exp="d",numchild="0",type="int",thread-id="1"},child={name="struct_declarations.s2.u2.u1s1.e",exp="e",numchild="10",type="char [10]",thread-id="1"},child={name="struct_declarations.s2.u2.u1s1.func",exp="func",numchild="0",type="int *(*)(void)",thread-id="1"},child={name="struct_declarations.s2.u2.u1s1.foo",exp="foo",numchild="0",type=[-"efoo"-]{+"enum foo"+},thread-id="1"}],has_more="0"
>
> typedef enum foo efoo;
> struct {
> int d;
> char e[10];
> int *(*func) (void);
> efoo foo;
> } u1s1;
> # Test: c_variable-4.61
> # Desc: children of struct_declarations.s2.u2.u1s1
> mi_list_varobj_children struct_declarations.s2.u2.u1s1 {
> {struct_declarations.s2.u2.u1s1.d d 0 int}
> {struct_declarations.s2.u2.u1s1.e e 10 {char \[10\]}}
> {struct_declarations.s2.u2.u1s1.func func 0 {int \*\(\*\)\((void)?\)}}
> {struct_declarations.s2.u2.u1s1.foo foo 0 efoo}
> } "get children of struct_declarations.s2.u2.u1s1"
>
> I find that the type of the field should be really reported before
> check_typedef and therefore the patch should be reverted.
I am sorry for somehow missing this problem. On the other hand, I do believe
that gdb crashing is by definition are bigger problem than wrong type reported
somewhere, so something more elaborate is required.
- Volodya
next prev parent reply other threads:[~2010-01-02 10:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-01 18:45 Jan Kratochvil
2010-01-02 10:08 ` Vladimir Prus [this message]
2010-01-02 20:30 ` [patch] " Jan Kratochvil
2010-01-03 4:58 ` Joel Brobecker
2010-01-03 5:48 ` Jan Kratochvil
2010-01-03 6:03 ` Joel Brobecker
2010-01-03 17:06 ` Daniel Jacobowitz
2010-01-03 19:26 ` Jan Kratochvil
2010-01-03 21:52 ` Daniel Jacobowitz
2010-01-03 22:14 ` Jan Kratochvil
2010-01-05 17:49 ` 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=201001021308.19130.vladimir@codesourcery.com \
--to=vladimir@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@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