From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org, Chris Moller <cmoller@redhat.com>
Subject: Re: [patch] Fix memory corruption on aborted object print
Date: Mon, 28 Jun 2010 17:00:00 -0000 [thread overview]
Message-ID: <20100628170026.GA9439@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <m3eifryuaz.fsf@fleche.redhat.com>
On Mon, 28 Jun 2010 18:51:32 +0200, Tom Tromey wrote:
> >>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
>
> Jan> 2010-06-28 Jan Kratochvil <jan.kratochvil@redhat.com>
> Jan> * cp-valprint.c (cp_print_value_fields) <recurse == 0>: Call
> Jan> obstack_begin after each obstack_free.
> Jan> 2010-06-28 Jan Kratochvil <jan.kratochvil@redhat.com>
> Jan> * gdb.cp/static-print-quit.exp, gdb.cp/static-print-quit.cc: New.
>
> This is ok. Thanks.
Checked-in:
http://sourceware.org/ml/gdb-cvs/2010-06/msg00191.html
Thanks,
Jan
prev parent reply other threads:[~2010-06-28 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-28 14:06 Jan Kratochvil
2010-06-28 16:51 ` Tom Tromey
2010-06-28 17:00 ` Jan Kratochvil [this message]
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=20100628170026.GA9439@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=cmoller@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