Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@gnat.com>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/testsuite] Some feedback about bigcore.exp...
Date: Fri, 19 Mar 2004 00:09:00 -0000	[thread overview]
Message-ID: <20040313044202.GH1135@gnat.com> (raw)
In-Reply-To: <20040313020758.511364B104@berman.michael-chastain.com>

> I'm running red hat linux 8 with kernel 2.4.8-14 on an ext3 file system
> and my core files are sparse.  What kernel/file-system do you have
> where the core files actually take up that much space?

I didn't know about this feature. On my linux laptop (2.6 kernel with
ext3), ls says I get a corefile of the following size: 2014404608.
However, the execution of the test is almost instantaneous, so I suspect
it's sparse too. Is there a way to know the physical size?

However, I also regularly run the testsuite on other platforms,
and it did hurt :-/...

-- 
Joel


WARNING: multiple messages have this Message-ID
From: Joel Brobecker <brobecker@gnat.com>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/testsuite] Some feedback about bigcore.exp...
Date: Sat, 13 Mar 2004 04:42:00 -0000	[thread overview]
Message-ID: <20040313044202.GH1135@gnat.com> (raw)
Message-ID: <20040313044200.cxo11BYFUES-0qAl8ZW32Dz1aALEf_DSv9r5OY7UbwA@z> (raw)
In-Reply-To: <20040313020758.511364B104@berman.michael-chastain.com>

> I'm running red hat linux 8 with kernel 2.4.8-14 on an ext3 file system
> and my core files are sparse.  What kernel/file-system do you have
> where the core files actually take up that much space?

I didn't know about this feature. On my linux laptop (2.6 kernel with
ext3), ls says I get a corefile of the following size: 2014404608.
However, the execution of the test is almost instantaneous, so I suspect
it's sparse too. Is there a way to know the physical size?

However, I also regularly run the testsuite on other platforms,
and it did hurt :-/...

-- 
Joel


  parent reply	other threads:[~2004-03-13  4:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-19  0:09 Michael Elizabeth Chastain
2004-03-13  2:08 ` Michael Elizabeth Chastain
2004-03-19  0:09 ` Joel Brobecker [this message]
2004-03-13  4:42   ` Joel Brobecker
2004-03-19  0:09   ` Daniel Jacobowitz
2004-03-13 16:58     ` Daniel Jacobowitz
2004-03-19  0:09 Joel Brobecker
2004-03-12 22:21 ` Joel Brobecker
2004-03-19  0:09 ` Andrew Cagney
2004-03-15 16:26   ` 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=20040313044202.GH1135@gnat.com \
    --to=brobecker@gnat.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