From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: [patch] New FAIL in gdb.python/py-type.exp [Re: fix PR python/10676]
Date: Tue, 24 Aug 2010 16:29:00 -0000 [thread overview]
Message-ID: <20100824162902.GA9808@host1.dyn.jankratochvil.net> (raw)
In-Reply-To: <m3pqxcykmi.fsf@fleche.redhat.com>
On Sat, 21 Aug 2010 00:39:17 +0200, Tom Tromey wrote:
> + gdb_test "python print c.type == gdb.parse_and_eval('d').type" "False"
python print c.type == gdb.parse_and_eval('d').type
./python/py-type.c:902: internal-error: VEC_type_equality_entry_d_quick_push: Assertion `quick_push' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) FAIL: gdb.python/py-type.exp: python print c.type == gdb.parse_and_eval('d').type (GDB internal error)
On Fedora 13 x86_64 for example with `./configure; make'.
It PASSes with the fix. Tested only gdb.python/py-type.exp on
x86_64-fedora14snapshot-linux-gnu.
OK to check-in?
Thanks,
Jan
gdb/
2010-08-24 Jan Kratochvil <jan.kratochvil@redhat.com>
* python/py-type.c (typy_richcompare): Initialize worklist.
--- a/gdb/python/py-type.c
+++ b/gdb/python/py-type.c
@@ -892,7 +892,7 @@ typy_richcompare (PyObject *self, PyObject *other, int op)
else
{
struct bcache *cache;
- VEC (type_equality_entry_d) *worklist;
+ VEC (type_equality_entry_d) *worklist = NULL;
struct type_equality_entry entry;
cache = bcache_xmalloc ();
next prev parent reply other threads:[~2010-08-24 16:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-20 22:39 fix PR python/10676 Tom Tromey
2010-08-24 16:29 ` Jan Kratochvil [this message]
2010-08-24 17:21 ` [patch] New FAIL in gdb.python/py-type.exp [Re: fix PR python/10676] Tom Tromey
2010-08-24 17:25 ` Jan Kratochvil
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=20100824162902.GA9808@host1.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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