public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "srinivasa at in dot ibm dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug runtime/6562] $SYSTEMTAP_DEBUGINFO_PATH does not work
Date: Thu, 29 May 2008 12:17:00 -0000	[thread overview]
Message-ID: <20080529055747.30205.qmail@sourceware.org> (raw)
In-Reply-To: <20080526073449.6562.prasad@linux.vnet.ibm.com>


------- Additional Comments From srinivasa at in dot ibm dot com  2008-05-29 05:57 -------
(In reply to comment #5)
> Srini,
> Will your patch work for modules? Do we still look under /lib/modules/`uname -r`/?
> If so, great!

Elfutils doesn't allow us to specify different paths for vmlinux and modules(
except in one case where vmlinux is searched in /boot and modules in
/lib/modules/uname -r, this because these paths are hardcoded).

So when we specify path in SYSTEMTAP_DEBUGINFO_PATH, elfutils searches modules
in that path, 
for eg:- [root@llm27lp1 src]# export
SYSTEMTAP_DEBUGINFO_PATH=/home/srini/systemtap/linux-2.6.26-rc3

Then elfutils searches modules in subdirs of /home/srini/systemtap/linux-2.6.26-rc3

[root@llm27lp1 src]# ./stap -vvv -e 'probe
module("ext3").function("ext3_group_extend") { printf("hi\n")}'
........................................
 .......................................
focused on module 'ext3 = [0x4f0200-0x518100, bias 0x0] file
/home/srini/systemtap/linux-2.6.26-rc3/fs/ext3/ext3.ko ELF machine ppc64 (code 21)
...........................
====================================

> 
> Another option for helping folks who'd want to use SystemTap with their self
> built kernels, but without sufficient /boot/ space is to make elfutils
> intelligent to look for /lib/modules/`uname -r`/build/vmlinux

This can be solved by above patch, just set
export SYSTEMTAP_DEBUGINFO_PATH=/lib/modules/`uname -r`/build/, elfutils
searches vmlinux and modules in same dir.


> 
> Ananth



-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=6562

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

  parent reply	other threads:[~2008-05-29  5:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-27  1:34 [Bug runtime/6562] New: " prasad at linux dot vnet dot ibm dot com
2008-05-27 19:26 ` Wenji Huang
2008-05-27 19:31 ` [Bug runtime/6562] " wenji dot huang at oracle dot com
2008-05-27 19:41 ` prasad at linux dot vnet dot ibm dot com
2008-05-28 16:57 ` srinivasa at in dot ibm dot com
2008-05-28 17:20 ` fche at redhat dot com
2008-05-28 17:24 ` ananth at in dot ibm dot com
2008-05-29 12:17 ` srinivasa at in dot ibm dot com [this message]
2008-05-29 12:23 ` ananth at in dot ibm dot com
2008-06-03 23:41 ` fche at redhat dot com
2008-07-10 16:49 ` fche at redhat dot com
2008-07-11  3:23 ` wenji dot huang at oracle dot com
2008-07-11 10:47 ` srinivasa at in dot ibm dot com
2008-10-20 15:15 ` fche at redhat dot com
2008-10-20 18:59 ` mjw at redhat dot com
2008-10-21  6:33 ` srinivasa at in dot ibm dot com
2009-02-03  5:36 ` srikar at linux dot vnet dot ibm dot com
2009-02-03  6:08 ` srikar at linux dot vnet dot ibm dot com
     [not found] <bug-6562-6586@http.sourceware.org/bugzilla/>
2014-03-19 22:21 ` lars at pixar dot com
2014-03-19 23:21   ` Josh Stone
2014-03-19 23:35     ` Lars R. Damerow
2021-08-30 16:48 ` fche at redhat dot com

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=20080529055747.30205.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --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).