From: "mmlnx at us dot ibm dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug runtime/3051] New: print_backtrace() prints most of stack on a single line on ppc64
Date: Mon, 14 Aug 2006 22:35:00 -0000 [thread overview]
Message-ID: <20060814223547.3051.mmlnx@us.ibm.com> (raw)
print_backtrace() prints most of the stack on a single line on ppc64, making it
difficult to read. For example, the following stap script:
probe kernel.function("schedule@kernel/sched.c") {
print_backtrace();
}
prints the following output:
trace for 21638 (stpd)
0xc00000000036c494 : .schedule+0x54/0xe48 []
[c0000000d1e6f868] [d00000000075b198] 0xd00000000075b198 :
.ipv6_netfilter_init+0x239a0c/0x0 [ipv6] (unreliable)[c0000000d1e6fae0]
[c0000000d1e6fb80] 0xc0000000d1e6fb80 :
__initramfs_end+0xd1a3bafd/0xfffffffffbf0f7d [][c0000000d1e6fbf0]
[d0000000006b75dc] 0xd0000000006b75dc : .ipv6_netfilter_init+0x195e50/0x0
[ipv6][c0000000d1e6fcf0] [c0000000000c5d68] 0xc0000000000c5d68 :
.vfs_read+0x128/0x20c [][c0000000d1e6fd90] [c0000000000c6248] 0xc0000000000c6248
: .sys_read+0x4c/0x8c [][c0000000d1e6fe30] [c00000000000871c] 0xc00000000000871c
: syscall_exit+0x0/0x40 []--- Exception: c01 at 0xffd7738
LR =0x10003110
trace for 20900 (sshd)
0xc00000000036c494 : .schedule+0x54/0xe48 []
[c0000000d8307668] [7fffffffffffffff] 0x7fffffffffffffff
(unreliable)[c0000000d83078e0] [c000000000056540] 0xc000000000056540 :
.__wake_up+0x54/0x88 [][c0000000d83079f0] [c00000000036e078] 0xc00000000036e078
: .schedule_timeout+0x40/0xec [][c0000000d8307ac0] [c0000000000e0ab4]
0xc0000000000e0ab4 : .do_select+0x3d4/0x488 [][c0000000d8307c10]
[c0000000000fefc0] 0xc0000000000fefc0 : .compat_core_sys_select+0x17c/0x224
[][c0000000d8307d00] [c0000000001012a4] 0xc0000000001012a4 :
.compat_sys_select+0xd0/0x188 [][c0000000d8307dc0] [c000000000015ba8]
0xc000000000015ba8 : .ppc32_select+0x14/0x28 [][c0000000d8307e30]
[c00000000000871c] 0xc00000000000871c : syscall_exit+0x0/0x40 []--- Exception:
c01 at 0x7a9b704
... and so on.
On i386, each stack entry is printed on a separate line.
--
Summary: print_backtrace() prints most of stack on a single line
on ppc64
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: mmlnx at us dot ibm dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=3051
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2006-08-14 22:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-14 22:35 mmlnx at us dot ibm dot com [this message]
2006-10-12 16:42 ` [Bug runtime/3051] " hunt at redhat dot com
2006-10-12 16:42 ` hunt at redhat 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=20060814223547.3051.mmlnx@us.ibm.com \
--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).