From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@gnat.com>
Cc: Michael Elizabeth Chastain <mec.gnu@mindspring.com>,
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: <20040313165817.GA24188@nevyn.them.org> (raw)
In-Reply-To: <20040313044202.GH1135@gnat.com>
On Fri, Mar 12, 2004 at 08:42:02PM -0800, Joel Brobecker wrote:
> > 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?
Yes: try 'du core'.
> However, I also regularly run the testsuite on other platforms,
> and it did hurt :-/...
I still think we should require a whitelist for this test as a matter
of pragmatism. It's not nice to our users if they download GDB 6.1,
build it on Some Supported Non-Linux Operating System, run "make
check", and it eats their machine alive.
Does anyone know of any operating system _other_ than Linux that supports
dumping cores as sparse files?
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
WARNING: multiple messages have this Message-ID
From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@gnat.com>
Cc: Michael Elizabeth Chastain <mec.gnu@mindspring.com>,
gdb-patches@sources.redhat.com
Subject: Re: [RFA/testsuite] Some feedback about bigcore.exp...
Date: Sat, 13 Mar 2004 16:58:00 -0000 [thread overview]
Message-ID: <20040313165817.GA24188@nevyn.them.org> (raw)
Message-ID: <20040313165800.RE2ULg2IDB6kM43WTiXIHgnZ8GJFtSnowZL8vEGmTrQ@z> (raw)
In-Reply-To: <20040313044202.GH1135@gnat.com>
On Fri, Mar 12, 2004 at 08:42:02PM -0800, Joel Brobecker wrote:
> > 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?
Yes: try 'du core'.
> However, I also regularly run the testsuite on other platforms,
> and it did hurt :-/...
I still think we should require a whitelist for this test as a matter
of pragmatism. It's not nice to our users if they download GDB 6.1,
build it on Some Supported Non-Linux Operating System, run "make
check", and it eats their machine alive.
Does anyone know of any operating system _other_ than Linux that supports
dumping cores as sparse files?
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-03-13 16:58 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
2004-03-13 4:42 ` Joel Brobecker
2004-03-19 0:09 ` Daniel Jacobowitz [this message]
2004-03-13 16:58 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
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=20040313165817.GA24188@nevyn.them.org \
--to=drow@false.org \
--cc=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