From: Gurudas Pai <gurudas.pai@oracle.com>
To: Garrett Cooper <yanegomi@gmail.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] LTP-20100630:tcore.sh test fails
Date: Mon, 02 Aug 2010 12:13:32 +0530 [thread overview]
Message-ID: <4C566914.6070205@oracle.com> (raw)
In-Reply-To: <AANLkTinw4gJOzmkxf=0WVGGekfzecmW8CkwbKrKaad_o@mail.gmail.com>
> Try this:
>
> index 1b68291..7f1dc9f 100644
> --- a/testcases/misc/tcore_patch_test_suites/tcore.exp
> +++ b/testcases/misc/tcore_patch_test_suites/tcore.exp
> @@ -43,7 +43,7 @@ proc check_threads {} {
> set buf $expect_out(0,string)
> }
> timeout {
> - fail "timeout while run info threads"
> + puts stderr "timeout while run info threads"
> return 1
> }
> }
> @@ -111,7 +111,7 @@ proc check_fpu {num} {
> set buf $expect_out(0,string)
> }
> timeout {
> - fail "fail to check the xmm value(timeout)"
> + puts stderr "fail to check the xmm value(timeout)"
> return 1
> }
> }
Hi Garrett,
Thanks for the patch !
Running tests.......
<<<test_start>>>
tag=tcore stime=1280710300
cmdline="tcore.sh"
contacts=""
analysis=exit
<<<test_output>>>
incrementing stop
Test Tcore patch
/tmp/ltp-bNMTB13033/tmp.elSZn13135
Test whether we can generate the needed core file
PASS
/tmp/ltp-bNMTB13033/tmp.elSZn13135
Test whether the core support bt,fpu and threads commands
spawn gdb ./tcore ./corefile
info register
GNU gdb (GDB) Red Hat Enterprise Linux (7.0.1-23.el5)
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
./tcore: No such file or directory.
[New Thread 13143]
[New Thread 13139]
Core was generated by `/opt/ltp/testcases/bin//tcore'.
Program terminated with signal 11, Segmentation fault.
#0 0x000000000040129d in ?? ()
(gdb)
(gdb) info register
rax 0xc 12
rbx 0x1e08 7688
rcx 0x41776ee0 1098346208
rdx 0xc 12
rsi 0x402b39 4205369
rdi 0x41776ee0 1098346208
rbp 0x3353 0x3353
rsp 0x417770e0 0x417770e0
r8 0x0 0
r9 0x41776658 1098344024
r10 0x0 0
r11 0x0 0
r12 0x41777100 1098346752
r13 0x417770f0 1098346736
r14 0x41778000 1098350592
r15 0x1000 4096
rip 0x40129d 0x40129d
eflags 0x10206 [ PF IF RF ]
cs 0x33 51
ss 0x2b 43
ds 0x0 0
es 0x0 0
fs 0x63 99
gs 0x0 0
fctrl 0x37f 895
fstat 0x20 32
ftag 0xffff 65535
fiseg 0x0 0
fioff 0x40128b 4199051
foseg 0x0 0
fooff 0x417770e0 1098346720
fop 0x33c 828
mxcsr 0x1f80 [ IM DM ZM OM UM PM ]
(gdb)
rax 0xc 12
rbx 0x1e08 7688
rcx 0x41776ee0 1098346208
rdx 0xc 12
rsi 0x402b39 4205369
rdi 0x41776ee0 1098346208
rbp 0x3353 0x3353
rsp 0x417770e0 0x417770e0
r8 0x0 0
r9 0x41776658 1098344024
r10 0x0 0
r11 0x0 0
r12 0x41777100 1098346752
r13 0x417770f0 1098346736
r14 0x41778000 1098350592
r15 0x1000 4096
rip 0x40129d 0x40129d
eflags 0x10206 [ PF IF RF ]
cs 0x33 51
ss 0x2b 43
ds 0x0 0
es 0x0 0
fs 0x63 99
gs 0x0 0
fctrl 0x37f 895
fstat 0x20 32
ftag 0xffff 65535
fiseg 0x0 0
fioff 0x40128b 4199051
foseg 0x0 0
fooff 0x417770e0 1098346720
fop 0x33c 828
mxcsr 0x1f80 [ IM DM ZM OM UM PM ]
(gdb) fail to check the xmm value(timeout)
spawn gdb ./tcore ./corefile
info threads
GNU gdb (GDB) Red Hat Enterprise Linux (7.0.1-23.el5)
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
./tcore: No such file or directory.
[New Thread 13143]
[New Thread 13139]
Core was generated by `/opt/ltp/testcases/bin//tcore'.
Program terminated with signal 11, Segmentation fault.
#0 0x000000000040129d in ?? ()
(gdb) info threads
3 Thread 13139 0x0000003fc2807b35 in ?? ()
2 Thread 13143 0x0000003fc280aee9 in ?? ()
* 1 Thread 13144 0x000000000040129d in ?? ()
(gdb) timeout while run info threads
spawn gdb ./tcore ./corefile
check bt in coredump successfully<<<execution_status>>>
initiation_status="ok"
duration=23 termination_type=exited termination_id=3 corefile=no
cutime=6 cstime=12
<<<test_end>>>
INFO: ltp-pan reported some tests FAIL
LTP Version: LTP-20100630
Test is still failing , do you think this is an os issue ?
Thanks,
-Guru
------------------------------------------------------------------------------
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2010-08-02 6:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 6:23 [LTP] LTP-20100630:tcore.sh test fails Gurudas Pai
2010-08-02 6:39 ` Garrett Cooper
2010-08-02 6:43 ` Gurudas Pai [this message]
2010-08-02 7:15 ` Garrett Cooper
2010-08-02 7:07 ` Gurudas Pai
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=4C566914.6070205@oracle.com \
--to=gurudas.pai@oracle.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=yanegomi@gmail.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