This is the mail archive of the
mailing list for the elfutils project.
Re: MIPS Elfutils support?
- From: Indu Bhagat <ibhagatgnu at gmail dot com>
- To: Mark Wielaard <mark at klomp dot org>, Kurt Roeckx <kurt at roeckx dot be>
- Cc: Luke Diamand <ldiamand at roku dot com>, "elfutils-devel at sourceware dot org" <elfutils-devel at sourceware dot org>
- Date: Thu, 10 Oct 2019 17:20:36 -0700
- Subject: Re: MIPS Elfutils support?
- References: <BN7PR01MB39539BDE0D767B5601A5FED8B09E0@BN7PR01MB3953.prod.exchangelabs.com> <email@example.com>
On Tue, Jan 22, 2019 at 6:50 AM Mark Wielaard <firstname.lastname@example.org> wrote:
> Hi Luke,
> On Sun, 2019-01-20 at 16:42 +0000, Luke Diamand wrote:
> > I was hoping to use elfutils on some MIPS core files. So I was
> > wondering what the status is?
> > There is a patch in Debian (apparently originally from RedHat?) here:
> > That's not in the mainline code though, and also lacks unwind support
> > (?).
> > I also have a small patch needed to pick up the shared library
> > process map - instead of using DT_DEBUG, MIPS targets use
> > DT_MIPS_RLD_MAP in core files.
> The status of that port is somewhat unclear.
> Although the files state they are copyrighted Red Hat, I believe that
> is wrong. They might be derived from some other backend which was. But
> I think the original authors have disappeared.
> The other problem has been that we don't seem to have anybody with MIPS
> experience/setups that can help test/integrate the port.
> Also, in the past the port made changes to the generic libelf code that
> caused bugs on other architectures:
> Which made me somewhat suspicious about this backend.
> Best would be to discuss with the Debian maintainer, Kurt Roeckx <
> email@example.com>, how to move this forward/upstream.
( + Kurt )
I am interesting in knowing the state of the MIPS port as well. What
are the plans for upstreaming this ?