public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "Michael Ellerman" <michael@ellerman.id.au>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: systemtap@sourceware.org
Subject: Re: elfutils on Debian?
Date: Thu, 16 Mar 2006 03:06:00 -0000	[thread overview]
Message-ID: <dc1166600603151906l28c3cdaemddcdcc44f06ba229@mail.gmail.com> (raw)
In-Reply-To: <20060316030039.GH22198@redhat.com>

On 3/16/06, Frank Ch. Eigler <fche@redhat.com> wrote:
> Hi -
>
> > Thanks, with that patch I can build elfutils and systemtap.
>
> Good.
>
> > Now I've just got to work out why all these tests are failing :)
>
> Look in the testresults/*.err files.  Chances are that
> systemtap/elfutils can't find the debugging information for your
> kernel.  Are debian kernels/modules stripped, and debugging
> information separated?  Where are they installed?

I'm actually running a custom kernel, so where am I supposed to put
debug info? And what exactly do I need, a vmlinux built with -g ?

cheers

  reply	other threads:[~2006-03-16  3:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-15  5:50 Michael Ellerman
2006-03-15  6:28 ` Ananth N Mavinakayanahalli
2006-03-15 14:00 ` Frank Ch. Eigler
2006-03-15 14:05   ` Michael K. Dolan Jr.
2006-03-15 14:15   ` Michael Ellerman
2006-03-15 14:35     ` Frank Ch. Eigler
2006-03-15 19:33       ` Roland McGrath
2006-03-16  2:53       ` Michael Ellerman
2006-03-16  3:00         ` Frank Ch. Eigler
2006-03-16  3:06           ` Michael Ellerman [this message]
2006-03-16  3:14             ` Frank Ch. Eigler
2006-03-16 16:02         ` William Cohen
     [not found]   ` <44181EE3.3030908@michaeldolan.com>
2006-03-15 14:19     ` Michael Ellerman
2006-03-15 14:35       ` Nathan DeBardeleben
2006-03-15 14:50         ` Frank Ch. Eigler
2006-03-15 15:38           ` Nathan DeBardeleben
2006-03-16  2:52             ` Michael Ellerman

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=dc1166600603151906l28c3cdaemddcdcc44f06ba229@mail.gmail.com \
    --to=michael@ellerman.id.au \
    --cc=fche@redhat.com \
    --cc=systemtap@sourceware.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).