From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: archer@sourceware.org
Subject: Re: [python] [approval request] Re: FYI a testcase FAIL: test Frame.read_var_value - error
Date: Fri, 06 Mar 2009 14:22:00 -0000 [thread overview]
Message-ID: <1236349318.8765.3.camel@localhost.localdomain> (raw)
In-Reply-To: <20090306132509.GA32564@host0.dyn.jankratochvil.net>
El vie, 06-03-2009 a las 14:25 +0100, Jan Kratochvil escribió:
> On Fri, 06 Mar 2009 04:35:18 +0100, Thiago Jung Bauermann wrote:
> > El jue, 05-03-2009 a las 23:58 +0100, Jan Kratochvil escribió:
> > > python print 'result =', f0.read_var ('b')
> > > result = {i = {0, 1068498944}, d = 0.0625}
> > > (gdb) FAIL: gdb.python/python-frame.exp: test Frame.read_var - error
> >
> > This is weird. python-frame.c doesn't have a b variable in f2, which is
> > where the testcase stops for the tests. It does have an argument named b
> > in f1, but it surely doesn't have such type. It's a plain int.
>
> I could have investigated it more first (and curious you do not have
> glibc-debuginfo installed):
I actually do have it, but Debian's debuginfo for libc is minimal,
unfortunately.
> OK to checkin the patch below?
Fine by me. Thanks for working on this.
--
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center
next prev parent reply other threads:[~2009-03-06 14:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 19:48 [python] " Jan Kratochvil
2009-03-04 17:02 ` Thiago Jung Bauermann
2009-03-05 22:58 ` Jan Kratochvil
2009-03-06 3:35 ` Thiago Jung Bauermann
2009-03-06 13:25 ` [python] [approval request] " Jan Kratochvil
2009-03-06 14:22 ` Thiago Jung Bauermann [this message]
2009-03-06 14:28 ` Thiago Jung Bauermann
2009-03-06 14:31 ` Jan Kratochvil
2009-03-06 15:04 ` Thiago Jung Bauermann
2009-03-06 23:41 ` 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=1236349318.8765.3.camel@localhost.localdomain \
--to=bauerman@br.ibm.com \
--cc=archer@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).