From: Andrew Cagney <cagney@gnu.org>
To: Andrew Cagney <cagney@gnu.org>, Nathanael Nerode <neroden@twcny.rr.com>
Cc: gdb@sources.redhat.com
Subject: Re: Removing leftover traces of mmalloc?
Date: Tue, 10 Aug 2004 15:51:00 -0000 [thread overview]
Message-ID: <4118EF0F.9000502@gnu.org> (raw)
In-Reply-To: <41139C3D.3080502@gnu.org>
>> With the removal of mmalloc support from gdb, nothing in src or gcc is
>> actually using mmalloc. Furthermore, support appears to have been removed
>> prior to the branching of GDB 6.1.
>>
>> Would it be appropriate to delete the mmalloc directory and all the trailing
>> references thereto? If not, would it at any rate be appropriate to stop
>> shipping it with GDB and delete the various trailing references?
>
>
> I think it is fine to break the the GDB <-> mmalloc connection (by zapping it from config et.al.).
Hmm, I just noted some lingering calls to [x]mmalloc in the objfile
reader. I'll replace them (their reason for being there is gone).
Since GDB works around the lack of mmalloc this wouldn't have been noticed.
Andrew
> As for removing it (cvs rm -f), perhaphs we can avoid it (although I don't care).
>
> GDB has a growing list of top-level src directories that it doesn't need to be included in a distro (src/mmalloc/ is one). I think its time to prune the `gdb' module (which, I know, is not a very backward compatible thing to do).
>
> Andrew
>
> PS: But `what-if' GDB needs to replace obstacks with something more like mmalloc (ah, the irony)? We can then revive it - here we need to deal with `what-is' :-)
prev parent reply other threads:[~2004-08-10 15:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-05 21:07 Nathanael Nerode
2004-08-06 14:57 ` Andrew Cagney
2004-08-10 15:51 ` Andrew Cagney [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=4118EF0F.9000502@gnu.org \
--to=cagney@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=neroden@twcny.rr.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