From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32542 invoked by alias); 31 Dec 2012 12:18:18 -0000 Received: (qmail 32506 invoked by uid 22791); 31 Dec 2012 12:18:14 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Received: from mail-la0-f51.google.com (HELO mail-la0-f51.google.com) (209.85.215.51) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 31 Dec 2012 12:18:10 +0000 Received: by mail-la0-f51.google.com with SMTP id fj20so3705131lab.24 for ; Mon, 31 Dec 2012 04:18:08 -0800 (PST) MIME-Version: 1.0 Received: by 10.152.110.18 with SMTP id hw18mr38965041lab.22.1356956288620; Mon, 31 Dec 2012 04:18:08 -0800 (PST) Received: by 10.112.11.38 with HTTP; Mon, 31 Dec 2012 04:18:08 -0800 (PST) In-Reply-To: <50E00806.2090906@tu-dortmund.de> References: <50E00806.2090906@tu-dortmund.de> Date: Mon, 31 Dec 2012 12:18:00 -0000 Message-ID: Subject: Re: Unknown symbol error using stap in 2.6.31 on ARM From: Cipher Chen To: Alexander Lochmann Cc: systemtap@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2012-q4/txt/msg00312.txt.bz2 hi, Alexander Just as what i mentioned below, it didnt work. On Sun, Dec 30, 2012 at 5:23 PM, Alexander Lochmann wrote: > Hi, > > try to run stap with "--compatible=1.8". > Stap needs uprobe support for some builtin functions as weel. Using this > option it will use old fashion builtin function. > > Greetings > Alex > > > On 12/30/2012 02:55 AM, Cipher Chen wrote: >> >> Hi, >> I met the same problem descripted here: >> >> http://sourceware-org.1504.n7.nabble.com/Unknown-symbol-error-using-stap-in-RHEL-5-4-td176251.html >> >> What's different is that it's an ARM target. After i got >> ntfs_watching.ko, "staprun ntfs_watching.ko" on that, it told me: >> dmesg here: >> ntfs_watching: Unknown symbol utrace_control >> ntfs_watching: Unknown symbol utrace_barrier >> ntfs_watching: Unknown symbol __utrace_engine_release >> ntfs_watching: Unknown symbol unregister_uretprobe >> ntfs_watching: Unknown symbol register_uprobe >> ntfs_watching: Unknown symbol unmap_uretprobe >> ntfs_watching: Unknown symbol utrace_attach_task >> ntfs_watching: Unknown symbol register_uretprobe >> ntfs_watching: Unknown symbol unmap_uprobe >> ntfs_watching: Unknown symbol utrace_set_events >> ntfs_watching: Unknown symbol unregister_uprobe >> >> So i tried something mentioned in that thread, it didnt work since >> it's linux-2.6.31.5 without CONFIG_UPROBES. >> It doesnt have any modules running. >> Can we say that staprun ran with its own uprobes.ko? >> >> Then I also copied the uprobes.ko in /tmp/stap**** generated on host >> to the ARM target, and "insmod uprobes.ko" >> dmesg here: >> uprobes: Unknown symbol utrace_control >> uprobes: Unknown symbol utrace_attach_pid >> uprobes: Unknown symbol utrace_set_events >> ("staprun ntfs_watching -u" told me these too) >> >> Any thoughts on what might be causing this problem? >> >> >> >> Thanks! > >