Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [rfa:ppc64gnulinux] Call ".malloc"
Date: Fri, 14 Nov 2003 01:13:00 -0000	[thread overview]
Message-ID: <1031114011301.ZM6012@localhost.localdomain> (raw)
In-Reply-To: Andrew Cagney <ac131313@redhat.com> "[rfa:ppc64gnulinux] Call ".malloc"" (Nov 13,  7:56pm)

On Nov 13,  7:56pm, Andrew Cagney wrote:

> When only minimal symbol information is available, the symbol "malloc", 
> which is found in a data section because it's a descriptor, gets turns 
> into a 32-bit int variable.  Consequently, an attempt to call "malloc" 
> is turned into to jump to the code designated by that 32-bit integer 
> value found at malloc.
> 
> This patch avoids that problem entirely by specifying that on PPC64 
> GNU/Linux, the "malloc" function has the name ".malloc" (which is really 
> the function's start address).
> 
> ok?

Sounds good to me.

Kevin


  reply	other threads:[~2003-11-14  1:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-14  0:56 Andrew Cagney
2003-11-14  1:13 ` Kevin Buettner [this message]
2003-11-14 14:23   ` 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=1031114011301.ZM6012@localhost.localdomain \
    --to=kevinb@redhat.com \
    --cc=ac131313@redhat.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