From: Markus Deuling <deuling@de.ibm.com>
To: ligang@sunnorth.com.cn
Cc: Daniel Jacobowitz <drow@false.org>, gdb@sourceware.org
Subject: Re: long_long.exp FAIL problem
Date: Mon, 10 Mar 2008 12:05:00 -0000 [thread overview]
Message-ID: <47D507F4.2020408@de.ibm.com> (raw)
In-Reply-To: <OF119C2B0D.19B81040-ON48257405.002D210A-48257405.002D6B75@sunnorth.com.cn>
ligang@sunnorth.com.cn schrieb:
>>> (gdb) PASS: gdb.base/long_long.exp: p/f *(long long *)ll
>>> p/c *(long long *)ll^M
>>> $66 = -17 'ERROR: Process no longer exists
>>> UNRESOLVED: gdb.base/long_long.exp: p/c *(long long *)ll
>> That looks to me like GDB crashed. Check your ulimit, check for
>> core dumps in the testsuite directory.
>
> I confirm it is not GDB crash.
> Sometimes, this test pattern PASS, othertimes ERROR. I am confused.
>
Increase verbosity of dejagnu:
make RUNTESTFLAGS="gdb.base/long_long.exp -v -v" check
and check your log file in gdb/testsuite/gdb.log. Maybe you try
to do the failing operation per hand and see if GDB crashes.
--
Markus Deuling
GNU Toolchain for Linux on Cell BE
deuling@de.ibm.com
prev parent reply other threads:[~2008-03-10 10:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-07 6:25 bjgnu
2008-03-07 8:16 ` Daniel Jacobowitz
2008-03-07 8:56 ` ligang
2008-03-10 12:05 ` Markus Deuling [this message]
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=47D507F4.2020408@de.ibm.com \
--to=deuling@de.ibm.com \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
--cc=ligang@sunnorth.com.cn \
/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