Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: Michael Elizabeth Chastain <mec.gnu@mindspring.com>,
	gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc/testsuite] Test GDB on not-so-little core files
Date: Wed, 14 Jan 2004 15:44:00 -0000	[thread overview]
Message-ID: <20040114154418.GA7520@nevyn.them.org> (raw)
In-Reply-To: <40056277.8050209@redhat.com>

On Wed, Jan 14, 2004 at 10:38:31AM -0500, Andrew Cagney wrote:
> >
> >There are two things that make me really nervous about this test.  One
> >of them is systems with bad out-of-memory behavior, and the other is
> >systems that don't dump sparse corefiles.  That's some serious pounding
> >we'll be handing out...
> 
> Wicked.  Our testsuite could do with some serious real world pounding. 
> Otherwize we'll never find, fix and then maintain the edge cases those 
> tests can identify.

Well, my point is not that it will be pounding GDB, but that it will be
pounding the equipment used to test GDB; that's less obviously good :)

> BTW, I wrote:
> 
> > on some systems may not be so efficient at dumping core files making 
> the test too slow
> 
> and those systems may find it better to disable the test :-/

My fear is that it will vary by machine and configuration, not by OS.
I'll give it a shot first, but I may be asked by the maintainers of the
Debian autobuilder network to disable this test - normally I collect
test results from every architecture (that works reasonably well, I'd
been leaving off Sparc for 6.0...) when the package is built.

It's not a big deal for the FSF tree either way.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2004-01-14 15:44 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
2004-01-14 15:16   ` Daniel Jacobowitz
2004-01-14 15:38     ` Andrew Cagney
2004-01-14 15:44       ` Daniel Jacobowitz [this message]
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=20040114154418.GA7520@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=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