public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Haley <aph@cambridge.redhat.com>
To: "Göran Thyni" <goran@kirra.net>
Cc: Bryce McKinlay <bryce@waitaki.otago.ac.nz>,
	devl@freenetproject.org, java@gcc.gnu.org
Subject: Re: gcj/freenet status 20020504
Date: Tue, 07 May 2002 08:58:00 -0000	[thread overview]
Message-ID: <15575.63922.20199.717508@cuddles.cambridge.redhat.com> (raw)
In-Reply-To: <20020507144622.GA13506@kirra.net>

=?iso-8859-1?Q?G=F6ran?= Thyni writes:
 > I'm out of town so I can just speculated until I have an oppotunity
 > to investigate things closer
 > 
 > On Tue, May 07, 2002 at 01:28:48PM +0100, Andrew Haley wrote:
 > > What will cause that to happen?  If the child process blocks on
 > > output, when eventually its parent exits it will be owned by exec
 > > which will patiently wait for it to terminate.
 > 
 > More patient than me, :-)
 > I killed them manually.
 > They propabably waits for something from their dead father,
 > I would guess that an "out of memory" exception kills fred
 > and leaves his children orphaned.

That's possible.  Once the system runs out of memory it's hard to
terminate cleanly.

 > > It sounds to me like "addr2line" and "c++filt" are buggy.  There's no
 > > reason they should be large.
 > 
 > At least addr2line is working against fred's pid file the /proc file system.
 > If it maps the process, addr2line itself will be very large since
 > fred is large himself.

addr2line doesn't map the process, just the executable file.  But
indeed, that could be large.

Andrew.

      reply	other threads:[~2002-05-07 15:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-04  2:41 Goran Thyni
2002-05-04 17:42 ` Bryce McKinlay
2002-05-07  5:29   ` Andrew Haley
2002-05-07  7:46     ` Göran Thyni
2002-05-07  8:58       ` Andrew Haley [this message]

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=15575.63922.20199.717508@cuddles.cambridge.redhat.com \
    --to=aph@cambridge.redhat.com \
    --cc=bryce@waitaki.otago.ac.nz \
    --cc=devl@freenetproject.org \
    --cc=goran@kirra.net \
    --cc=java@gcc.gnu.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).