public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Luke Diamand <ldiamand@roku.com>,
	"elfutils-devel@sourceware.org"	 <elfutils-devel@sourceware.org>
Subject: Re: MIPS Elfutils support?
Date: Tue, 22 Jan 2019 14:50:00 -0000	[thread overview]
Message-ID: <2b0fb9e94118c740ad22e9baeb4b142b7bbd22b7.camel@klomp.org> (raw)
In-Reply-To: <BN7PR01MB39539BDE0D767B5601A5FED8B09E0@BN7PR01MB3953.prod.exchangelabs.com>

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:
> 
https://sources.debian.org/src/elfutils/0.175-2/debian/patches/mips_backend.diff/
> 
> 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:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794488
Which made me somewhat suspicious about this backend.

Best would be to discuss with the Debian maintainer, Kurt Roeckx <
kurt@roeckx.be>, how to move this forward/upstream.

Thanks,

Mark

  reply	other threads:[~2019-01-22 14:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-20 16:42 Luke Diamand
2019-01-22 14:50 ` Mark Wielaard [this message]
2019-10-11  0:20   ` Indu Bhagat

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=2b0fb9e94118c740ad22e9baeb4b142b7bbd22b7.camel@klomp.org \
    --to=mark@klomp.org \
    --cc=elfutils-devel@sourceware.org \
    --cc=ldiamand@roku.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).