From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Subject: Re: Crash regression [Re: [4/5] implement "info vtable"]
Date: Mon, 19 Mar 2012 18:13:00 -0000 [thread overview]
Message-ID: <87bonsmpcg.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20120316081005.GA17525@host2.jankratochvil.net> (Jan Kratochvil's message of "Fri, 16 Mar 2012 09:10:05 +0100")
>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
Jan> Crash regression for: gdb.cp/virtfunc.exp
Jan> Expecting due to -lmcheck.
Jan> Reproducible on x86_64-fedora16-linux-gnu.
I'm checking in the appended.
I verified that this fixes it using valgrind.
Tom
2012-03-19 Tom Tromey <tromey@redhat.com>
* gnu-v3-abi.c (gnuv3_print_vtable): Initialize 'result_vec'.
diff --git a/gdb/gnu-v3-abi.c b/gdb/gnu-v3-abi.c
index 72ca2a1..1095c60 100644
--- a/gdb/gnu-v3-abi.c
+++ b/gdb/gnu-v3-abi.c
@@ -907,7 +907,7 @@ gnuv3_print_vtable (struct value *value)
struct value_print_options opts;
htab_t offset_hash;
struct cleanup *cleanup;
- VEC (value_and_voffset_p) *result_vec;
+ VEC (value_and_voffset_p) *result_vec = NULL;
struct value_and_voffset *iter;
int i, count;
next prev parent reply other threads:[~2012-03-19 18:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 21:48 [4/5] implement "info vtable" Tom Tromey
2012-02-29 18:20 ` Eli Zaretskii
2012-03-01 14:52 ` Pedro Alves
2012-03-01 17:36 ` Tom Tromey
2012-03-01 20:18 ` Pedro Alves
2012-03-15 15:43 ` Tom Tromey
2012-03-16 8:10 ` Crash regression [Re: [4/5] implement "info vtable"] Jan Kratochvil
2012-03-19 18:13 ` Tom Tromey [this message]
2012-07-19 9:34 ` [4/5] implement "info vtable" Andreas Schwab
2012-07-19 17:01 ` Tom Tromey
2012-07-20 8:33 ` Andreas Schwab
2012-07-20 14:24 ` Tom Tromey
2012-07-20 14:29 ` Andreas Schwab
2012-07-20 16:23 ` Tom Tromey
2012-07-20 17:34 ` Andreas Schwab
2012-07-20 17:48 ` Tom Tromey
2012-07-20 18:08 ` Andreas Schwab
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=87bonsmpcg.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=palves@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