Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!know!zaphod.mps.ohio-state.edu!sdd.hp.com!hp-pcd!hpfcso!bruno
From: bruno@hpfcso.HP.COM (Bruno Melli)
Newsgroups: comp.sys.hp
Subject: Re: Motif and xdb problem
Message-ID: <7370208@hpfcso.HP.COM>
Date: 20 Sep 90 15:59:41 GMT
References: <9474@uhccux.uhcc.Hawaii.Edu>
Organization: Hewlett-Packard, Fort Collins, CO, USA
Lines: 20

>   death of child (no ignore) at 0xa1ff0
>   (file unknown): _sigprocmask +0x8: (line unknown)

If you do a stack trace at this point, you most likely get something
like this:

 0 _sigprocmask + 0x8 (0xffeff1d4, 0x400, 0x1430, 0xffeff1d4, 0x400)
 1 _getcwd + 0x16 (0xeae6c, 0x1, 0x1a8, 0xffefda04, 0xd6888)
                        [ more stuff here ]
 7 _XmCreateFileSelectionDialog + 0x52 (0xd0edc, 0x98011, 0, 0, 0xd21b8)
 8 main (argc = 1, argv = 0xffeffb44)    [t.c: 34]

getcwd(3C) does a fork(). The death of child signal you get is when the
child process of the fork() exits. Xdb gets notified because the
child process of the fork() is in the same group ID.

So that doesn't mean there is anything wrong with your program. Continuing
the program as you are doing is the right thing to do.

bruno.