From: Andrew Cagney <ac131313@redhat.com>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc/testsuite] Test GDB on not-so-little core files
Date: Wed, 14 Jan 2004 15:07:00 -0000 [thread overview]
Message-ID: <40055B49.70003@redhat.com> (raw)
In-Reply-To: <20040114145701.9034A4B104@berman.michael-chastain.com>
>> testcase /house/chastain/gdb/s1/gdb/testsuite/gdb.base/bigcore.exp completed in 183 seconds
>> testcase src/gdb/testsuite/gdb.base/bigcore.exp completed in 4 seconds
>
>
> Figures prove: Linux dumps core faster! :)
>
> Part of the difference is that I'm using an NFS file system.
Nope. I'm using NFS on a weasly little 450mhz P2.
> But a lot of it may be sparse file support in Linux.
Yep. While sparse file support is a standard part of UFS, it appears
that only the Linux Kernel thought to exploit it when writing the core file!
> I can't comment on the program itself right now, maybe later.
Hmm, can you think of an efficient way of soaking up most of the stack
...? :-) On GNU/Linux, alloca() proved to be useless :-(
Andrew
next prev parent reply other threads:[~2004-01-14 15:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 14:56 Michael Elizabeth Chastain
2004-01-14 15:07 ` Andrew Cagney [this message]
2004-01-14 15:16 ` Daniel Jacobowitz
2004-01-14 15:38 ` Andrew Cagney
2004-01-14 15:44 ` Daniel Jacobowitz
2004-01-15 19:09 ` Andrew Cagney
2004-01-15 19:13 ` Daniel Jacobowitz
2004-01-20 22:02 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2004-01-21 8:18 Michael Elizabeth Chastain
2004-01-21 4:42 Michael Elizabeth Chastain
2004-01-21 5:23 ` Andrew Cagney
2004-01-14 3:11 Michael Elizabeth Chastain
2004-01-14 14:48 ` Andrew Cagney
2004-01-14 2:40 Andrew Cagney
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=40055B49.70003@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec.gnu@mindspring.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