This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: run time error - how to debug?
- From: "Peter Teoh" <htmldeveloper at gmail dot com>
- To: systemtap at sources dot redhat dot com
- Date: Sun, 18 May 2008 16:10:27 +0800
- Subject: Re: run time error - how to debug?
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=oxz7t/RxKKapgZdnZf5Vhrv4FRY9f1RuUOQTpiRcaLg=; b=QXA0AhEBEwFvtAVAsgQraZUHmLp0f6ONZ3yVXZfDaPv66wcH2Wdz7hOEmKWgbGnwj2TPHIoHdDUT7ewD2tszrRyHo52cses6Sf6dVGXNVMtkkfbayXeONfUzOqcndqXtRVO1/9wbQNQ5VXofBxOP2oA//lxEZAuFZy26rQ5TcbA=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=iN1K0Sr4OWZzXEe2a55q8rJoMhbWFDwXpThbVg9K6wfZ+RkZL6kf1YK8fLBpEeE/+Y8nVrMLY0l6XUchr+3mZBjJdXvtqA9r2SuWZiXLmlzEm065MLN8C09herH5ZDtOec8H+BxaO7tcb5HiMvFmSyK5cx5pt8lai9RHAWk3Xak=
- References: <804dabb00805171925v77023c9by3a69f90f0f8505bd@mail.gmail.com>
Let me try again (after rebooting the system):
a. Run the stap probe:
probe kernel.function("*@mm/swapfile.c").call {
printf ("%s -> %s\n", thread_indent(1), probefunc())
print_backtrace();
printf("\n");
}
probe kernel.function("*@mm/swapfile.c").return {
printf ("%s <- %s\n", thread_indent(-1), probefunc())
printf("\n");
}
b. It got through pass5, and loaded as module into kernel, and lsmod gives:
stap_861c1a9009233ff719572d129f564e06_12247 451808 1
but still failed as:
Pass 5: run failed. Try again with more '-v' (verbose) options.
c. dmesg gives:
BUG: unable to handle kernel paging request at 40000000
IP: [<40000000>]
*pde = 00000000
Oops: 0000 [#1] SMP
Pid: 4516, comm: staprun Not tainted (2.6.26-rc2 #8)
EIP: 0060:[<40000000>] EFLAGS: 00010246 CPU: 0
EIP is at 0x40000000
EAX: 00000000 EBX: f7917b00 ECX: 00000000 EDX: f3669e70
ESI: c122a8c0 EDI: f8e551dc EBP: f8ef2800 ESP: f3669d64
DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
Process staprun (pid: 4516, ti=f3669000 task=f69bab50 task.ti=f3669000)
Stack: f8e8d3f6 00000001 f3e84e44 74737973 61746d65 c2000070 00000286 c0434c61
51518c1a 0000014e 00000286 ffffffff c2012780 f780c6c0 00000001 c04d8ce2
f3669df0 00000009 00000001 70617473 3136385f 39613163 32393030 66663333
Call Trace:
[<f8e8d3f6>] _stp_transport_init+0x3a3/0x4cd
[stap_861c1a9009233ff719572d129f564e06_12247]
[<c0434c61>] hrtimer_start+0xf4/0x10d
[<c04d8ce2>] idr_get_empty_slot+0x11e/0x1ef
[<c04a63a7>] sysfs_ilookup_test+0x0/0xd
[<c0411b1b>] native_smp_call_function_mask+0xab/0xe8
[<c0411f43>] do_flush_tlb_all+0x0/0x40
[<c0411f43>] do_flush_tlb_all+0x0/0x40
[<c04533a4>] free_pages_bulk+0x129/0x18e
[<c043fb4c>] sys_init_module+0x1844/0x19b4
[<c04b92b1>] avc_has_perm+0x3c/0x46
[<c04dc01e>] simple_strtoull+0x0/0xdc
[<c04b611a>] security_capset_set+0xe/0x11
[<c040380d>] sysenter_past_esp+0x6a/0x91
[<c0610000>] yenta_probe+0x201/0x567
=======================
Code: Bad EIP value.
EIP: [<40000000>] 0x40000000 SS:ESP 0068:f3669d64
---[ end trace 145d18014bdbe738 ]---
What I don't understand is why EIP is at 0x40000000? as for
_stp_transport_init().....