From owner-freebsd-isdn Wed Mar 31 12:27:26 1999 Delivered-To: freebsd-isdn@freebsd.org Received: from peedub.muc.de (newpc.muc.ditec.de [194.120.126.33]) by hub.freebsd.org (Postfix) with ESMTP id 28DA71506B for ; Wed, 31 Mar 1999 12:27:01 -0800 (PST) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id VAA03985; Wed, 31 Mar 1999 21:55:52 +0200 (CEST) Message-Id: <199903311955.VAA03985@peedub.muc.de> X-Mailer: exmh version 2.0.2 2/24/98 To: Christoph Weber-Fahr Cc: freebsd-isdn@freebsd.org Subject: Re: vanishing isdnd - what debug ? Reply-To: Gary Jennejohn In-reply-to: Your message of "Wed, 31 Mar 1999 18:16:21 +0200." <199903311617.SAA12967@helena.otelo-call.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 31 Mar 1999 21:55:51 +0200 From: Gary Jennejohn Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Christoph Weber-Fahr writes: >> You could just turn on all the isdnd trace and hope that it provides a >> clue. > >Hm... I just hoped to get a hint on specific debug settings. >(Or, of course, on someone having seen this before...). > >Ok, I will try the -d0xf9, as given in the examples... > I'd turn on all bits (0x1ff) myself. Another possibility would be to turn on trace in the kernel (see isdndebug), but this could result in enormous quantities of useless trace. Another possiblty that occurs to me is for you to compile isdnd with -g and run it under gdb or attach to it after it's started. If it exits for some reason gdb will notice that and give you a chance to debug it. I've never seen any reports like this before, that's why I couldn't be more specific with hints. I've also never seen isdnd self-destruct, and I've been using isdn4bsd since before it was publically released. --- Gary Jennejohn Home - garyj@muc.de Work - garyj@fkr.dec.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message