From: "Frank Ch. Eigler" <fche@redhat.com>
To: Dave Brolley <brolley@redhat.com>
Cc: sid@sources.redhat.com
Subject: Re: [patch] ELF loader
Date: Fri, 13 Feb 2004 17:57:00 -0000 [thread overview]
Message-ID: <20040213175717.GD26355@redhat.com> (raw)
In-Reply-To: <402CEA85.9010109@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 418 bytes --]
Hi -
brolley wrote:
> [...]
> I used xrealloc to allocate loadAreas and textSections. It used to be an
> unchecked hard coded limit of 100 elements each. [...]
The code doesn't have to be modified to avoid libiberty.
(If I were to write the code though, I might have opted to
move stuff away from the old elfload.c module, and into C++
file where one can use std::vector<> etc. for such data.)
- FChE
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-02-13 17:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-12 20:29 Dave Brolley
2004-02-12 20:45 ` Dave Brolley
2004-02-12 22:49 ` Ben Elliston
2004-02-13 3:09 ` Ben Elliston
2004-02-13 15:17 ` Dave Brolley
2004-02-13 17:57 ` Frank Ch. Eigler [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=20040213175717.GD26355@redhat.com \
--to=fche@redhat.com \
--cc=brolley@redhat.com \
--cc=sid@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).