From: David Carlton <carlton@math.stanford.edu>
To: gdb <gdb@sources.redhat.com>
Subject: How much should I cleanup?
Date: Tue, 11 Feb 2003 23:40:00 -0000 [thread overview]
Message-ID: <ro1d6lygzcs.fsf@jackfruit.Stanford.EDU> (raw)
When is it important to make sure that I have cleanups in place? My
understanding is that it's important if I have control of a block of
memory that I want to xfree() after doing some work, but where that
xfree() might not be reached because of exceptional circumstances.
So, if that's correct: what are 'exceptional circumstances'? I assume
error() and related functions count. I don't know exactly what QUIT
does; do I have to be careful if there are QUIT's in between the
xmalloc() and the xfree()? (Are those the only places where GDB pays
attention to ^C's?) Any other situations?
Sigh. C has its benefits, but ease of memory management isn't one of
them. Every time I have to write a cleanup function, every time I
have to think about whether to alloca() memory for a string or to
xmalloc() it (and every time I can't alloca() it because I'm returning
the string in question), I get another grey hair. (Though the grey
hair falls out soon thereafter, for better or for worse.)
David Carlton
carlton@math.stanford.edu
next reply other threads:[~2003-02-11 23:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-11 23:40 David Carlton [this message]
2003-02-17 14:58 ` Andrew Cagney
2003-02-17 16:46 ` David Carlton
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=ro1d6lygzcs.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--cc=gdb@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