From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: jan.kratochvil@redhat.com (Jan Kratochvil)
Cc: xgsa@yandex.ru (xgsa), tromey@redhat.com (Tom Tromey),
gdb-patches@sourceware.org
Subject: Re: set print object on should affect MI varobjs (PR mi/13393)
Date: Mon, 23 Jul 2012 17:21:00 -0000 [thread overview]
Message-ID: <201207231721.q6NHLIkh001963@d06av02.portsmouth.uk.ibm.com> (raw)
In-Reply-To: <20120416163226.GA9706@host2.jankratochvil.net> from "Jan Kratochvil" at Apr 16, 2012 06:32:26 PM
Jan Kratochvil wrote:
> On Sat, 14 Apr 2012 14:28:26 +0200, xgsa wrote:
> > >Yeah. I'm sorry about the delay. The patch is ok, please check it in.
> >
> > Checked in.
>
> Fedora 17 x86_64:
> +FAIL: gdb.mi/mi-var-rtti.exp: list children of s.public in type_update_when_use_rtti
> +FAIL: gdb.mi/mi-var-rtti.exp: list children of s.ptr (without RTTI) in type_update_when_use_rtti
> +FAIL: gdb.mi/mi-var-rtti.exp: list children of s.ptr.public (without RTTI) in type_update_when_use_rtti
Yes, I'm seeing similar failures on a number of platforms (arm, spu, s390x).
The reason seems to be that the test case is attempting to display local
variables that are not yet initialized, and thus their contents are random.
For C++ objects, this includes a random vtable pointer ...
Now, this particular sub-test appears to do this deliberately; all the other
sub-tests only create the varobj *after* their corresponding objects were
initialized. I'm not quite sure what exactly the test is supposed to be
testing, but I guess it ought to be done differently ...
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2012-07-23 17:21 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-02 19:50 set print object on should affect MI varobjs (PR 13393) xgsa
2011-12-08 8:15 ` xgsa
2011-12-19 20:34 ` xgsa
2011-12-20 17:47 ` Tom Tromey
2011-12-21 19:01 ` set print object on should affect MI varobjs (PR gdb/13393) xgsa
2011-12-21 19:37 ` Jan Kratochvil
2011-12-22 10:17 ` set print object on should affect MI varobjs (PR mi/13393) xgsa
2011-12-24 1:55 ` Jan Kratochvil
2011-12-24 13:56 ` xgsa
2012-01-02 2:22 ` Jan Kratochvil
2012-01-06 15:47 ` RTTI type improvement for (was: "Re: set print object on should affect MI varobjs (PR mi/13393)") xgsa
2012-01-09 14:41 ` Jan Kratochvil
2012-01-11 21:58 ` RTTI type improvement for Tom Tromey
2012-01-12 11:25 ` xgsa
2012-02-06 21:45 ` Tom Tromey
2012-02-08 18:34 ` xgsa
2012-02-10 20:13 ` Tom Tromey
2012-02-19 18:46 ` set print object on should affect MI varobjs (PR mi/13393) xgsa
2012-02-23 4:58 ` xgsa
2012-03-18 16:28 ` xgsa
2012-03-18 20:41 ` Eli Zaretskii
2012-03-19 7:10 ` xgsa
2012-03-19 17:41 ` Eli Zaretskii
2012-03-23 17:09 ` xgsa
2012-03-26 19:08 ` xgsa
2012-03-30 17:51 ` Tom Tromey
2012-03-30 18:01 ` Eli Zaretskii
2012-03-30 20:11 ` xgsa
2012-03-30 18:01 ` Eli Zaretskii
2012-03-30 20:25 ` xgsa
2012-03-30 20:52 ` Eli Zaretskii
2012-03-30 21:26 ` xgsa
2012-03-31 5:54 ` Eli Zaretskii
2012-03-31 6:57 ` xgsa
2012-03-31 9:33 ` xgsa
2012-04-03 0:54 ` Doug Evans
2012-04-03 13:27 ` xgsa
2012-04-06 17:11 ` xgsa
2012-04-13 8:07 ` xgsa
2012-04-13 12:22 ` Eli Zaretskii
2012-04-13 12:34 ` xgsa
2012-04-13 17:23 ` Tom Tromey
2012-04-14 23:35 ` xgsa
2012-04-16 18:35 ` Jan Kratochvil
2012-07-23 17:21 ` Ulrich Weigand [this message]
2012-08-06 7:26 ` xgsa
2012-02-21 14:15 ` RTTI type improvement for xgsa
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=201207231721.q6NHLIkh001963@d06av02.portsmouth.uk.ibm.com \
--to=uweigand@de.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=tromey@redhat.com \
--cc=xgsa@yandex.ru \
/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