Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: RFC: find core dumps on Linux
Date: Thu, 22 May 2003 22:49:00 -0000	[thread overview]
Message-ID: <20030522224901.GA18777@nevyn.them.org> (raw)
In-Reply-To: <vt2u1bmr4jj.fsf@zenia.red-bean.com>

On Thu, May 22, 2003 at 05:37:52PM -0500, Jim Blandy wrote:
> 
> I didn't realize this, but for a very long time, gdb.base/coredump.exp
> has been broken on Linux.  Linux creates core files named 'core.PID';
> the test suite didn't know how to find them, so it suggested you check
> your 'ulimit -c' setting and skipped the tests.

Seems reasonable to me.  It'll clean up better than before, too.

> 2003-05-22  Jim Blandy  <jimb@redhat.com>
> 
> 	* gdb.base/corefile.exp: Find corefiles on Linux, which names them
> 	'core.PID'.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-05-22 22:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-22 22:30 Jim Blandy
2003-05-22 22:49 ` Daniel Jacobowitz [this message]
2003-05-29 23:02   ` Jim Blandy
2003-06-23 21:08 ` Elena Zannoni
2003-06-24  3:03 Michael Elizabeth Chastain

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=20030522224901.GA18777@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.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