public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: David Taylor <taylor@cygnus.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: lduperval@sprint.ca,
	Insight Mailing List <insight@sourceware.cygnus.com>
Subject: Re: Debugging a fork()ed process
Date: Thu, 24 Feb 2000 07:36:00 -0000	[thread overview]
Message-ID: <200002241534.KAA11763@texas.cygnus.com> (raw)

    Date: Thu, 24 Feb 2000 19:21:47 +1100
    From: Andrew Cagney <ac131313@cygnus.com>

    lduperval@sprint.ca wrote:
    > 
    > Hi,
    > 
    > Subject (almost) says it all: how to I debug a forked process? I still
    > trying to find that problem I'm having with a GIMP plugin and it looks
    > like the problem shows up in a forked process. But the forked process
    > stays around for less than 1 second. Is there a good technique to catch
    > this process and debug it? I on Linux is that changes anything.

    HP contributed code to ``follow fork''.
    I believe, however, that it is still only implemented under HPUX.

Correct; it is only implemented on HPUX.

The Solaris /proc interface certainly has the necessary OS support to
allow it to be implemented for Solaris.

The Linux man pages are rather skimpy on details; but, I don't think
that Linux has the necessary OS support.

             reply	other threads:[~2000-02-24  7:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-24  7:36 David Taylor [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-02-21 22:17 lduperval
2000-02-24  0:24 ` Andrew Cagney
2000-02-24  5:16   ` laurent.duperval

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=200002241534.KAA11763@texas.cygnus.com \
    --to=taylor@cygnus.com \
    --cc=ac131313@cygnus.com \
    --cc=insight@sourceware.cygnus.com \
    --cc=lduperval@sprint.ca \
    /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).