public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: David Wilder <dwilder@us.ibm.com>
To: Roland McGrath <roland@redhat.com>
Cc: "Frank Ch. Eigler" <fche@redhat.com>,
	        SystemTAP <systemtap@sources.redhat.com>
Subject: Re: stap is getting a  segmentation fault on RHEL 5.1 bets
Date: Fri, 05 Oct 2007 17:37:00 -0000	[thread overview]
Message-ID: <47067651.20207@us.ibm.com> (raw)
In-Reply-To: <20071003210603.723F54D0544@magilla.localdomain>

Roland McGrath wrote:
>> Any idea what rpmbuild could be doing to the debuginfo files?
>> I looked through the kernel.spec file and found no clues, but I am 
>> unfamiliar with rpm spec files, so I may have missed something.
> 
> Some implicit magic happens after what's written in the spec file.
> Importantly, /usr/lib/rpm/find-debuginfo.sh runs to create the separate
> debuginfo files using eu-strip -f.

Thanks for the pointer.  When I run  "eu-strip --remove-comment" against 
the working file it creates a file that causes stap to fail.

Now I need to figure out if the debuginfo file is damaged by eu-strip, 
or it is a bug in elfutils relating to reading the striped file.

  reply	other threads:[~2007-10-05 17:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-27  0:42 stap is getting a segentation fault David Wilder
     [not found] ` <y0m641woqj7.fsf@ton.toronto.redhat.com>
2007-10-02 17:16   ` stap is getting a segmentation fault on RHEL 5.1 bets David Wilder
2007-10-02 17:51     ` Frank Ch. Eigler
2007-10-03 18:03       ` David Wilder
2007-10-03 21:06         ` Roland McGrath
2007-10-05 17:37           ` David Wilder [this message]
2007-10-05 20:30             ` Roland McGrath

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=47067651.20207@us.ibm.com \
    --to=dwilder@us.ibm.com \
    --cc=fche@redhat.com \
    --cc=roland@redhat.com \
    --cc=systemtap@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).