public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: fche@redhat.com (Frank Ch. Eigler)
To: Xiaokui Shu <subbyte@gmail.com>
Cc: systemtap@sourceware.org
Subject: Re: sendmail function probe registration error with systemtap
Date: Fri, 10 Jan 2014 18:46:00 -0000	[thread overview]
Message-ID: <y0mvbxrr7xl.fsf@fche.csb> (raw)
In-Reply-To: <CAMU3N_JxL8CFUOmiyuh0FMaVt_q3tF3b1ATSP+nW6HiS=dkV+g@mail.gmail.com> (Xiaokui Shu's message of "Thu, 9 Jan 2014 18:12:03 -0500")

Xiaokui Shu <subbyte@gmail.com> writes:

> [...] I start systemtap with a simple probe
> (shown below), I get two warnings in Pass 5. While running systemtap,
> [...]
> WARNING: probe process("/usr/sbin/sendmail.sendmail").function("mime_getchar_crlf.part.1")
> inode-offset 0005e620 registration error (rc -524)
> WARNING: probe process("/usr/sbin/sendmail.sendmail").function("frame_dummy")
> inode-offset 0001cc80 registration error (rc -524)

That's -ENOTSUPP; maybe there is some sort of instruction in there the
kernel doesn't like.

> I can send emails to the monitored host, but my mailbox on the host
> does not receive them. [...]  Can anyone help me to figure out what
> is the problem brought by the tracing?

This sounds should not happen.

> probe process(@1).function("*")
> {
>     printf ("%s:0x%x\n", probefunc (), ustack (1))
> }

You might try rerunning '# stap -DSTP_ALIBI foo.stp' to eliminate most
of the systemtap probe handler logic out of the script.  If the
userspace sendmail process still misbehaves, this helps incriminate
uprobes -- and vice versa.

Could you collect kernel / stap version information, or the whole
`stap-report` shebang?


- FChE

  reply	other threads:[~2014-01-10 18:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-09 23:12 Xiaokui Shu
2014-01-10 18:46 ` Frank Ch. Eigler [this message]
     [not found]   ` <CAMU3N_KaOPbsYQS1io=_v-g4PzzQ4mAbk0GAOveN2tf-dLmaCg@mail.gmail.com>
2014-01-10 20:27     ` Fwd: " Xiaokui Shu
2014-01-10 21:15     ` Frank Ch. Eigler
2014-01-10 21:43       ` Xiaokui Shu
2014-01-10 23:10         ` Xiaokui Shu

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=y0mvbxrr7xl.fsf@fche.csb \
    --to=fche@redhat.com \
    --cc=subbyte@gmail.com \
    --cc=systemtap@sourceware.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 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).