From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/9991] New: on-the-fly kernel debuginfo construction
Date: Mon, 23 Mar 2009 21:15:00 -0000 [thread overview]
Message-ID: <20090323210503.9991.fche@redhat.com> (raw)
mingo idea, paraphrased:
Given kernel sources & build tree, systemtap could invoke a
% make CONFIG_DEBUG_INFO=y foo/bar.o
on the fly to generate debuginfo-laden object code.
Some complications:
- different compiler versions may generate different code;
though maybe build-id matching would work
- we may not know which object files to rebuild for a basic
symbolic probe like:
probe kernel.function("foo_bar")
since these can occur in any old compilation unit.
Plus consider:
probe kernel.statement("*@include/bar.h:333")
- mapping module("foo") to the right path name is not obvious;
might require parsing of kernel **/Makefile
--
Summary: on-the-fly kernel debuginfo construction
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: translator
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: fche at redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=9991
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2009-03-23 21:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 21:15 fche at redhat dot com [this message]
2009-03-24 5:47 ` [Bug translator/9991] " wcohen at redhat dot com
2009-03-24 6:40 ` fche at redhat dot com
2009-03-24 9:10 ` fche at redhat dot com
2009-04-08 18:10 ` 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=20090323210503.9991.fche@redhat.com \
--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).