Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: Joel Brobecker <brobecker@gnat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: New target method returning the name of the malloc function?
Date: Fri, 06 Sep 2002 11:04:00 -0000	[thread overview]
Message-ID: <3D78EE3B.18907230@redhat.com> (raw)
In-Reply-To: <20020906002319.GW1169@gnat.com>

Joel Brobecker wrote:
> 
> Hello,
> 
> The name of the function used to allocate some memory in the inferior is
> currently hard-coded to "malloc" in valops.c:
> 
>      struct value *
>      value_allocate_space_in_inferior (int len)
>      {
>        struct value *blocklen;
>        struct value *val = find_function_in_inferior ("malloc");
>                                                        ^^^^^^
> 
> Unfortunately, on interix, the malloc function is not always there.
> Quoting Donn Terry:
> <<
> malloc() won't necessarily be present; the way our namespace pollution
> prevention stuff works, if the user application doesn't call an entry
> point at all, it just won't be there.  However, _malloc is always
> present (at least in any real program) because it's called from within
> the library.
> >>
> 
> May I suggest a new architecture method called for instance
> NAME_OF_MALLOC or MALLOC_FUNCTION_NAME? The default would be to return
> "malloc", but we could then change it to "_malloc" for the interix
> target.

Joel, 

This is a known limitation.  Certain things in GDB simply will not
work if the target program doesn't contain malloc.  It's been like 
that for 10 years.


      parent reply	other threads:[~2002-09-06 18:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-05 17:23 Joel Brobecker
2002-09-06  0:22 ` Pierre Muller
2002-09-06  6:03   ` Daniel Jacobowitz
2002-09-06  9:14   ` Kevin Buettner
2002-09-09  9:48     ` Joel Brobecker
2002-09-09 13:10     ` Andrew Cagney
2002-09-09 15:44       ` muller
2002-09-09 21:06         ` Andrew Cagney
2002-09-06 11:04 ` Michael Snyder [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=3D78EE3B.18907230@redhat.com \
    --to=msnyder@redhat.com \
    --cc=brobecker@gnat.com \
    --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