From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: Daniel Jacobowitz <drow@false.org>, gdb-patches@sourceware.org
Subject: Re: A couple of uses of xmalloc and xfree in a couple of .y files
Date: Sat, 25 Oct 2008 15:54:00 -0000 [thread overview]
Message-ID: <20081025155358.GG29998@adacore.com> (raw)
In-Reply-To: <200810250336.30073.pedro@codesourcery.com>
> 2008-10-25 Pedro Alves <pedro@codesourcery.com>
>
> * Makefile.in (.y.c, .l.c): sed free to xfree.
I think it would be useful. The nice thing about using xmalloc/xfree etc
is that it could be turned into a poor man's memory tracking device.
I worked on a double-deallocation problem on Windows once, and all the
tools I tried out there simply were not able to handle the size of my
project. With xfree/xmalloc etc, I could augment their implementation
to log every memory allocation/deallocation from GDB. It won't be
perfect, but it might help narrow down where to look.
--
Joel
next prev parent reply other threads:[~2008-10-25 15:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-24 22:58 Pedro Alves
2008-10-25 0:14 ` Joel Brobecker
2008-10-25 1:58 ` Daniel Jacobowitz
2008-10-25 2:37 ` Pedro Alves
2008-10-25 6:33 ` Daniel Jacobowitz
2008-10-25 15:54 ` Joel Brobecker [this message]
2008-10-27 11:48 ` Pedro Alves
2008-10-27 22:38 ` Pedro Alves
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=20081025155358.GG29998@adacore.com \
--to=brobecker@adacore.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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