From: Mark Kettenis <kettenis@chello.nl>
To: gdb-patches@sources.redhat.com
Subject: [PATCH] Don't include <malloc.h>
Date: Wed, 18 Feb 2004 17:25:00 -0000 [thread overview]
Message-ID: <200402181724.i1IHOtM3024273@elgar.kettenis.dyndns.org> (raw)
Including <malloc.h> is a no-no. The FreeBSD <malloc.h> makes GCC
warn about its usage ("use <stdlib.h> instead") which makes a compile
with -Werror fail. This stuff should be handled properly by our
"defs.h" anyway.
Committed as obvious,
Mark
Index: ChangeLog
from Mark Kettenis <kettenis@gnu.org>
* tui/tui.c: Don't include <malloc.h>.
Index: tui/tui.c
===================================================================
RCS file: /cvs/src/src/gdb/tui/tui.c,v
retrieving revision 1.46
diff -u -p -r1.46 tui.c
--- tui/tui.c 10 Feb 2004 19:08:19 -0000 1.46
+++ tui/tui.c 18 Feb 2004 17:22:18 -0000
@@ -25,7 +25,6 @@
#include <stdio.h>
#include <stdlib.h>
#include <ctype.h>
-#include <malloc.h>
#ifdef HAVE_TERM_H
#include <term.h>
#endif
next reply other threads:[~2004-02-18 17:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 17:25 Mark Kettenis [this message]
2004-02-18 18:38 ` Andrew Cagney
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=200402181724.i1IHOtM3024273@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=gdb-patches@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