From: Andrew Cagney <ac131313@cygnus.com>
To: Stephane Carrez <Stephane.Carrez@worldnet.fr>
Cc: Michael Snyder <msnyder@cygnus.com>,
Keith Seitz <keiths@cygnus.com>,
gdb-patches@sources.redhat.com
Subject: Re: [RFA]: Fix gdb.base/callfwmall.exp for platforms without malloc
Date: Wed, 06 Jun 2001 09:07:00 -0000 [thread overview]
Message-ID: <3B1E468E.4050407@cygnus.com> (raw)
In-Reply-To: <3B098795.1CD78B21@worldnet.fr>
> Hum... if I understand, the only good fix is to fix GDB so that it no longer
> calls 'malloc'. I would be very happy to see that fix in GDB. You cannot rely
> on a possible 'malloc'. I have two examples in mind here: 68HC11 programs
> and... ChorusOS kernel.
A patch to call sbrk() or rgnAllocate(ulgh!) et.al. instead of malloc()
would be interesting.
Andrew
next prev parent reply other threads:[~2001-06-06 9:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3B07B042.6BAD93A0@worldnet.fr>
2001-05-21 10:43 ` Michael Snyder
2001-05-21 10:56 ` Keith Seitz
2001-05-21 11:10 ` Michael Snyder
2001-05-21 14:20 ` Stephane Carrez
2001-05-21 14:58 ` Michael Snyder
2001-05-21 22:45 ` Jim Blandy
2001-06-06 9:07 ` Andrew Cagney [this message]
2001-05-22 9:16 Michael Elizabeth Chastain
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=3B1E468E.4050407@cygnus.com \
--to=ac131313@cygnus.com \
--cc=Stephane.Carrez@worldnet.fr \
--cc=gdb-patches@sources.redhat.com \
--cc=keiths@cygnus.com \
--cc=msnyder@cygnus.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