Date: Wed, 31 Mar 1999 21:55:51 +0200 From: Gary Jennejohn <garyj@peedub.muc.de> To: Christoph Weber-Fahr <listmail@helena.callcenter.systemhaus.net> Cc: freebsd-isdn@freebsd.org Subject: Re: vanishing isdnd - what debug ? Message-ID: <199903311955.VAA03985@peedub.muc.de> In-Reply-To: Your message of "Wed, 31 Mar 1999 18:16:21 %2B0200." <199903311617.SAA12967@helena.otelo-call.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199903311955.VAA03985>