public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mjw@redhat.com>
To: elfutils-devel@lists.fedorahosted.org
Subject: Re: [RFC] elfutils: Checks for debuginfo file without .debug extension as well
Date: Tue, 16 Feb 2016 17:45:06 +0100	[thread overview]
Message-ID: <1455641106.9915.55.camel@redhat.com> (raw)
In-Reply-To: 1455639695-8350-1-git-send-email-ravi.bangoria@linux.vnet.ibm.com

[-- Attachment #1: Type: text/plain, Size: 1431 bytes --]

Hi Ravi,

On Tue, 2016-02-16 at 21:51 +0530, Ravi Bangoria wrote:
> Elfutils, looking for kernel debuginfo file, tries to find it at
> various places. If elfutils finds /boot/vmlinu*x* file, it checks
> for debufginfo section. If debuginfo is not present, it saves it as
> 'main elf' and continue looking for debuginfo file having .debug
> extension i.e. vmlinux-RELEASE.debug.
> 
> 'Ubuntu on powerpc' installs kernel as /boot/vmlinux and installs
> debuginfo without any extension as /usr/lib/debug/boot/vmlinux-RELEASE
> and hence, elfutils is not able to find the debuginfo file.
> 
> Here is the lunchpad bug for the same:
>   https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/1537125
> 
> This patch adds functionality to search for file without any extension
> followed by searching file having .debug extension.

Thanks for the analysis. I do have a question though.

The reason we are looking for the vmlinux-3.13.0-76-generic.debug
filename instead of the plain vmlinux-3.13.0-76-generic filename seems
to be because /boot/vmlinux contains a .gnu_debuginfo link with the name
of the debug file. But that name doesn't match?

What does eu-readelf --strings=.gnu_debuglink /boot/vmlinux* say?

Would it make sense to not put in the "correct" (without .debug suffix)
debugfile name in .gnu_debuglink or completely leaving .gnu_debuginfo
out (or is nothing found then?)

Thanks,

Mark

             reply	other threads:[~2016-02-16 16:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-16 16:45 Mark Wielaard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-02-22 19:54 Mark Wielaard
2016-02-22 17:12 Ravi Bangoria
2016-02-22 13:45 Mark Wielaard
2016-02-20 13:40 Ravi Bangoria
2016-02-19 15:11 Mark Wielaard
2016-02-19  9:37 Ravi Bangoria
2016-02-17 15:49 Mark Wielaard
2016-02-17  8:20 Ravi Bangoria
2016-02-16 16:21 Ravi Bangoria

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=1455641106.9915.55.camel@redhat.com \
    --to=mjw@redhat.com \
    --cc=elfutils-devel@lists.fedorahosted.org \
    /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).