From: "Stone, Joshua I" <joshua.i.stone@intel.com>
To: "William Cohen" <wcohen@redhat.com>,
"Roland McGrath" <roland@redhat.com>
Cc: "SystemTap" <systemtap@sources.redhat.com>
Subject: SystemTap vs. FC5 Xen kernels (was: 03-23-2006 Meeting minutes)
Date: Thu, 30 Mar 2006 01:05:00 -0000 [thread overview]
Message-ID: <CBDB88BFD06F7F408399DBCF8776B3DC06CD0D51@scsmsx403.amr.corp.intel.com> (raw)
William Cohen wrote:
> Roland McGrath wrote:
>>> I tried this on x86_64 - and immediately ran into a problem with the
>>> debuginfo.
>>
>>
>> This was already noticed and is some problem in the kernel rpm specs.
>> There may be an fc5 bug report for it already on bugzilla.redhat.com,
>> I'm not sure.
>
> Xen x86_64 kernels in kernel debuginfo package do not contain dwarf
> symbols
>
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=185662
I found two differences in the config files that will prevent SystemTap
from running on the Xen kernels. In 2054_FC5 and 2054_FC5kdump, the
config files have:
CONFIG_KPROBES=y
...
CONFIG_DEBUG_INFO=y
Whereas in 2054_FC5xen0 and 2054_xenU, the config files have:
# CONFIG_KPROBES is not set
... with no mention of CONFIG_DEBUG_INFO. This might explain the
missing dwarf info in the kernel-debuginfo package. And of course for
SystemTap we need CONFIG_KPROBES=y.
Josh
next reply other threads:[~2006-03-30 1:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-30 1:05 Stone, Joshua I [this message]
2006-03-30 14:44 ` William Cohen
2006-03-30 21:18 Stone, Joshua I
2006-03-31 2:36 Stone, Joshua I
2006-03-31 14:07 ` William Cohen
2006-03-31 20:38 Stone, Joshua I
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=CBDB88BFD06F7F408399DBCF8776B3DC06CD0D51@scsmsx403.amr.corp.intel.com \
--to=joshua.i.stone@intel.com \
--cc=roland@redhat.com \
--cc=systemtap@sources.redhat.com \
--cc=wcohen@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).