From: Darren Hart <dvhltc@us.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "lkml, " <linux-kernel@vger.kernel.org>
Subject: trace-cmd memory corruption
Date: Wed, 26 Aug 2009 12:52:22 -0700 [thread overview]
Message-ID: <4A959276.3080000@us.ibm.com> (raw)
Hi Steven,
From latest trace-cmd git as of today. prio-wake is from the LTP
realtime testsuite testcases/realtime/func/prio-wake.
$ sudo ~/bin/trace-cmd record -p sched_switch -d ./prio-wake
plugin sched_switch
*** glibc detected *** /home/dvhart/bin/trace-cmd: malloc(): memory
corruption: 0x00000000006cc0c0 ***
======= Backtrace: =========
/lib64/libc.so.6[0x7f80d34a14ac]
/lib64/libc.so.6(__libc_malloc+0x7a)[0x7f80d34a302a]
/home/dvhart/bin/trace-cmd[0x401893]
/home/dvhart/bin/trace-cmd[0x401af1]
/home/dvhart/bin/trace-cmd[0x401f11]
/home/dvhart/bin/trace-cmd[0x403b24]
/lib64/libc.so.6(__libc_start_main+0xf4)[0x7f80d344c974]
/home/dvhart/bin/trace-cmd[0x4014b9]
======= Memory map: ========
00400000-0040f000 r-xp 00000000 08:03 538635
/home/dvhart/bin/trace-cmd
0060e000-0060f000 rw-p 0000e000 08:03 538635
/home/dvhart/bin/trace-cmd
006cb000-006ec000 rw-p 00000000 00:00 0
[heap]
7f80cc000000-7f80cc021000 rw-p 00000000 00:00 0
7f80cc021000-7f80d0000000 ---p 00000000 00:00 0
7f80d3221000-7f80d322e000 r-xp 00000000 08:03 114522
/lib64/libgcc_s-4.1.2-20080825.so.1
7f80d322e000-7f80d342e000 ---p 0000d000 08:03 114522
/lib64/libgcc_s-4.1.2-20080825.so.1
7f80d342e000-7f80d342f000 rw-p 0000d000 08:03 114522
/lib64/libgcc_s-4.1.2-20080825.so.1
7f80d342f000-7f80d357b000 r-xp 00000000 08:03 114301
/lib64/libc-2.5.so
7f80d357b000-7f80d377b000 ---p 0014c000 08:03 114301
/lib64/libc-2.5.so
7f80d377b000-7f80d377f000 r--p 0014c000 08:03 114301
/lib64/libc-2.5.so
7f80d377f000-7f80d3780000 rw-p 00150000 08:03 114301
/lib64/libc-2.5.so
7f80d3780000-7f80d3785000 rw-p 00000000 00:00 0
7f80d3785000-7f80d37a1000 r-xp 00000000 08:03 114508
/lib64/ld-2.5.so
7f80d3987000-7f80d3989000 rw-p 00000000 00:00 0
7f80d399e000-7f80d39a0000 rw-p 00000000 00:00 0
7f80d39a0000-7f80d39a1000 r--p 0001b000 08:03 114508
/lib64/ld-2.5.so
7f80d39a1000-7f80d39a2000 rw-p 0001c000 08:03 114508
/lib64/ld-2.5.so
7fffcba0c000-7fffcba21000 rw-p 00000000 00:00 0
[stack]
7fffcba3c000-7fffcba3d000 r-xp 00000000 00:00 0
[vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0
[vsyscall]
Aborted
If it's relevant:
$ cat /debug/tracing/available_tracers
syscall blk power function_graph wakeup_rt wakeup function sysprof
sched_switch nop
--
Darren Hart
IBM Linux Technology Center
Real-Time Linux Team
reply other threads:[~2009-08-26 19:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4A959276.3080000@us.ibm.com \
--to=dvhltc@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.