From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Khoo Yit Phang <khooyp@cs.umd.edu>, gdb@sourceware.org
Subject: Re: xfree/make_cleanup memory leak pattern?
Date: Wed, 11 Jan 2012 14:31:00 -0000 [thread overview]
Message-ID: <m38vle9upn.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20120111003215.GA11968@host2.jankratochvil.net> (Jan Kratochvil's message of "Wed, 11 Jan 2012 01:32:15 +0100")
>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
Jan> Yes, I agree. immediate_quit is not well handled.
I think it is only used in selected spots.
I wonder if we could enhance the exception checker to look for problems
in this area.
Tom
prev parent reply other threads:[~2012-01-11 14:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 0:25 Khoo Yit Phang
2012-01-11 0:31 ` Jan Kratochvil
2012-01-11 0:32 ` Jan Kratochvil
2012-01-11 14:31 ` 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=m38vle9upn.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=khooyp@cs.umd.edu \
/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