public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
* Debugging a fork()ed process
@ 2000-02-21 22:17 lduperval
  2000-02-24  0:24 ` Andrew Cagney
  0 siblings, 1 reply; 4+ messages in thread
From: lduperval @ 2000-02-21 22:17 UTC (permalink / raw)
  To: Insight Mailing List

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.

Thanks,

L


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Debugging a fork()ed process
  2000-02-21 22:17 Debugging a fork()ed process lduperval
@ 2000-02-24  0:24 ` Andrew Cagney
  2000-02-24  5:16   ` laurent.duperval
  0 siblings, 1 reply; 4+ messages in thread
From: Andrew Cagney @ 2000-02-24  0:24 UTC (permalink / raw)
  To: lduperval; +Cc: Insight Mailing List

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.

	Andrew

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Debugging a fork()ed process
  2000-02-24  0:24 ` Andrew Cagney
@ 2000-02-24  5:16   ` laurent.duperval
  0 siblings, 0 replies; 4+ messages in thread
From: laurent.duperval @ 2000-02-24  5:16 UTC (permalink / raw)
  To: ac131313; +Cc: lduperval, insight

On 24 Feb, Andrew Cagney wrote:
> 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.
> 

THanks for the response. I eventually modified some of the code to pause
untill I press a key and that's helped me get around that problem.

L

-- 
Laurent Duperval                   "Montreal winters are an intelligence test,
CGI - SARM Project                        and we who are here have failed it."
Phone: (514) 350-3368                                            -Don Camilli
mailto:laurent.duperval@cgi.ca      Penguin Power!


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Debugging a fork()ed process
@ 2000-02-24  7:36 David Taylor
  0 siblings, 0 replies; 4+ messages in thread
From: David Taylor @ 2000-02-24  7:36 UTC (permalink / raw)
  To: Andrew Cagney; +Cc: lduperval, Insight Mailing List

    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.

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2000-02-24  7:36 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-02-21 22:17 Debugging a fork()ed process lduperval
2000-02-24  0:24 ` Andrew Cagney
2000-02-24  5:16   ` laurent.duperval
2000-02-24  7:36 David Taylor

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).