From: Daniel Jacobowitz <drow@false.org>
To: bjgnu@sunnorth.com.cn
Cc: gdb@sourceware.org
Subject: Re: long_long.exp FAIL problem
Date: Fri, 07 Mar 2008 08:16:00 -0000 [thread overview]
Message-ID: <20080307062501.GA22901@caradoc.them.org> (raw)
In-Reply-To: <OF98243913.12A1F716-ON48257405.001068E3-48257405.001167D0@sunnorth.com.cn>
On Fri, Mar 07, 2008 at 11:10:09AM +0800, bjgnu@sunnorth.com.cn wrote:
> Hello,
>
> long_long.exp ERROR when running GDB testsuite. It always show "Process no
> longer exists".
> But, it is confused that this test pattern PASS sometimes and ERROR other
> times.
> The following is segment of testing sequence.
>
> p/f *(long long *)ll^M
> $65 = 3.5127005640885037e-303^M
> (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.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-03-07 6:25 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 [this message]
2008-03-07 8:56 ` ligang
2008-03-10 12:05 ` Markus Deuling
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=20080307062501.GA22901@caradoc.them.org \
--to=drow@false.org \
--cc=bjgnu@sunnorth.com.cn \
--cc=gdb@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox