This is the mail archive of the
mailing list for the GDB project.
Re: How much should I cleanup?
On Sun, 16 Feb 2003 10:22:38 +0100, Andrew Cagney <email@example.com> said:
>> 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?
> Failed memory read, no frame.
>> 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
> Ah, yes. C++ `is the answer' :-^
Well, to handle this particular situation, a language with actual
garbage collection would be the most pleasant to program in. (Let's
rewrite GDB in Scheme!) But yes, C++'s improved support for
exceptions, memory management, and strings makes it much more pleasant
to program in compared to C when dealing with this sort of stuff. (At
least once you have your old C pointer-usage habits drilled out of
you: writing exception-safe code in C++ isn't hard, it just doesn't
look quite like C code.) Getting C++ to play well with GDB's existing
memory management/exception handling mechanisms would take a little
thought, though I don't see any reason why it couldn't be done.