From: fche@redhat.com (Frank Ch. Eigler)
To: kernelnewbies@lists.kernelnewbies.org
Subject: system tap unable to refer a structure definition
Date: Sun, 07 May 2017 11:16:59 -0400 [thread overview]
Message-ID: <87shkg3dec.fsf@redhat.com> (raw)
In-Reply-To: <CAKJ7aR63eL8y7FC5XComwGZY60jG3D8Ggcp+UhRu2E8BPiMuOQ@mail.gmail.com> (Gadre Nayan's message of "Wed, 3 May 2017 16:29:45 +0530")
gadrenayan wrote:
> [...]
> c = @cast($frags[0]->f_addr, "volioship_hdr_t",
> "/root/ngadre/unixvm-cvs/src/common/kernel/vxvm/ioship_cvm.h")
> [...]
> The header file is locally available on the machine.
> [...]
> semantic error: type definition 'volioship_hdr_t' not found in '
> /root/ngadre/unixvm-cvs/src/common/kernel/vxvm/ioship_cvm.h': operator
> '@cast' at :46:6
> [...]
> How do I make system tap refer to this structure.
@cast requires use of the syntax "kernel<header.h>" to process such
files, because they involve different compiler invocations. That may
not be all there is to it. Rerun stap with --vp 04 or somesuch to
get some verbose tracing of its attempts to process that header.
- FChE
prev parent reply other threads:[~2017-05-07 15:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 10:59 system tap unable to refer a structure definition Gadre Nayan
2017-05-07 15:16 ` Frank Ch. Eigler [this message]
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=87shkg3dec.fsf@redhat.com \
--to=fche@redhat.com \
--cc=kernelnewbies@lists.kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.