Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: gdb@sourceware.org
Subject: bigcore.exp on 64-bit systems
Date: Sat, 13 Jan 2007 14:09:00 -0000	[thread overview]
Message-ID: <u4pqvhvby.fsf@gnu.org> (raw)

I'm trying to run the testsuite on a 64-bit machine that identifies
itself thusly:

    Linux fencepost 2.6.16.29-xen #1 SMP Wed Dec 6 07:32:36 EST 2006 x86_64 GNU/Linux

On this machine, bigcore.exp is a pest: it runs for a very long time,
produces a humongous core file (so large that I expect the sysadmins
to send me angry emails), and eventually fails (or so it seems).
Here's what gdb.sum says about it:

    Running ../.././gdb/testsuite/gdb.base/bigcore.exp ...
    PASS: gdb.base/bigcore.exp: set print sevenbit-strings; bigcore
    PASS: gdb.base/bigcore.exp: set width 0; bigcore
    PASS: gdb.base/bigcore.exp: tbreak 264
    PASS: gdb.base/bigcore.exp: continue
    PASS: gdb.base/bigcore.exp: next
    PASS: gdb.base/bigcore.exp: extract next heap (stop at 50)
    PASS: gdb.base/bigcore.exp: extract prev heap (stop at 50)
    PASS: gdb.base/bigcore.exp: save heap size
    PASS: gdb.base/bigcore.exp: grab pid
    FAIL: gdb.base/bigcore.exp: signal SIGABRT (timeout)
    FAIL: gdb.base/bigcore.exp: check core size (timeout)
    UNTESTED: gdb.base/bigcore.exp: check core size (system does not support large corefiles)

Is this normal?  What is the meaning of SIGABRT (timeout), and what,
if anything, should I do about the last line?

TIA


             reply	other threads:[~2007-01-13 14:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-13 14:09 Eli Zaretskii [this message]
2007-01-13 14:16 ` Joel Brobecker
2007-01-13 14:50 ` Mark Kettenis
2007-01-13 15:16   ` Eli Zaretskii
2007-01-13 18:31   ` Ulrich Weigand
2007-01-13 19:23     ` Daniel Jacobowitz
2007-01-13 19:33       ` Mark Kettenis
2007-01-13 21:16       ` Eli Zaretskii
2007-01-13 15:21 ` Daniel Jacobowitz
2007-01-13 17:57   ` Eli Zaretskii
2007-01-13 18:01     ` Daniel Jacobowitz

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=u4pqvhvby.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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