From: Tom Tromey <tromey@redhat.com>
To: Aleksandar Ristovski <aristovski@qnx.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch] Fix SIGSEGV in gdb when printing ctor of non-virtual class
Date: Mon, 02 Mar 2009 15:24:00 -0000 [thread overview]
Message-ID: <m3zlg4uevs.fsf@fleche.redhat.com> (raw)
In-Reply-To: <gogqdi$qfm$1@ger.gmane.org> (Aleksandar Ristovski's message of "Mon\, 02 Mar 2009 09\:28\:01 -0500")
>>>>> "Aleksandar" == Aleksandar Ristovski <aristovski@qnx.com> writes:
Aleksandar> An old patch. Gdb still SIGSEGV on this testcase, but I
Aleksandar> haven't got any replies.
Aleksandar> + /* Constructors of non-virtual classes will not have block. */
This seems weird. Is this a gcc bug or something?
Should this somehow be fixed elsewhere? I don't know.
Aleksandar> + release_value (v);
I don't think you want release_value here. You can just drop the
value, it will automatically be freed later.
Tom
prev parent reply other threads:[~2009-03-02 15:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 17:29 Aleksandar Ristovski
2008-09-26 17:32 ` Aleksandar Ristovski
2009-03-02 14:28 ` Aleksandar Ristovski
2009-03-02 15:24 ` Tom Tromey [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=m3zlg4uevs.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=aristovski@qnx.com \
--cc=gdb-patches@sources.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