public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "guanglei at cn dot ibm dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug kprobes/2387] system crash on ppc64/2.6.15.4
Date: Thu, 02 Mar 2006 05:58:00 -0000	[thread overview]
Message-ID: <20060302055849.488.qmail@sourceware.org> (raw)
In-Reply-To: <20060223094047.2387.guanglei@cn.ibm.com>


------- Additional Comments From guanglei at cn dot ibm dot com  2006-03-02 05:58 -------
> Hmm, where did you put the #define?
> 
> I get these warnings if I put it at the bottom of relayfs.h, but putting it at
> the top, just above 
> 
> #ifdef RELAYFS_VERSION_GE_4
> #include <linux/relayfs_fs.h>
> ...
> 
> it works fine for me...

the file I used:

#ifndef _TRANSPORT_RELAYFS_H_ /* -*- linux-c -*- */
#define _TRANSPORT_RELAYFS_H_
#define RELAYFS_VERSION_GE_4 

/** @file relayfs.h
 * @brief Header file for relayfs transport
 */

#ifdef RELAYFS_VERSION_GE_4
#include <linux/relayfs_fs.h>
#else
#include "../relayfs/linux/relayfs_fs.h"
#endif /* RELAYFS_VERSION_GE_4 */

struct rchan *_stp_relayfs_open(unsigned n_subbufs,
                                unsigned subbuf_size,
                                int pid,
                                struct dentry **outdir);
void _stp_relayfs_close(struct rchan *chan, struct dentry *dir);

#endif /* _TRANSPORT_RELAYFS_H_ */

So is it due to the gcc version? My gcc is:
gcc version 3.4.5 20051201 (Red Hat 3.4.5-2)
I checked the codes, and it is just a warning of the assignment:
int *ptr <--- static int *ptr

But I met another problem, I use my testcase to stress test systemtap:

-bash-3.00# ./test.sh -f  lgl.cfg  -I tapsets/tapsets1/           
The tapsets is tapsets/tapsets1/
don't probe app : dbench
TIMES : 1
TIMES : 2
probe app : dbench
TIMES : 1
TIMES : 2
error opening file stpd_cpu0.
ERROR: couldn't unlink percpu file stpd_cpu0: errcode = No such file or directory

Do you have any ideas of such errors? I never met it before.
I raise the MAXDSKIPPED when running my testcases

-- 


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

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

  parent reply	other threads:[~2006-03-02  5:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-23  9:40 [Bug kprobes/2387] New: " guanglei at cn dot ibm dot com
2006-02-23 12:34 ` [Bug kprobes/2387] " fche at redhat dot com
2006-02-23 15:23 ` guanglei at cn dot ibm dot com
2006-03-01 14:41 ` guanglei at cn dot ibm dot com
2006-03-01 15:38   ` Frank Ch. Eigler
2006-03-01 16:25 ` jrs at us dot ibm dot com
2006-03-01 16:36 ` guanglei at cn dot ibm dot com
2006-03-01 16:56 ` zanussi at us dot ibm dot com
2006-03-02  5:08 ` zanussi at us dot ibm dot com
2006-03-02  5:36 ` guanglei at cn dot ibm dot com
2006-03-02  5:48 ` guanglei at cn dot ibm dot com
2006-03-02  5:53 ` zanussi at us dot ibm dot com
2006-03-02  5:58 ` guanglei at cn dot ibm dot com [this message]
2006-03-02  6:13 ` zanussi at us dot ibm dot com
2006-03-02  6:16 ` guanglei at cn dot ibm 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=20060302055849.488.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).