[17154] in Kerberos_V5_Development
Re: Debugging kdcs and signals
daemon@ATHENA.MIT.EDU (Greg Hudson)
Sat Sep 10 16:29:31 2011
From: Greg Hudson <ghudson@mit.edu>
To: Sam Hartman <hartmans@mit.edu>
In-Reply-To: <tsl1uvourer.fsf@mit.edu>
Date: Sat, 10 Sep 2011 16:29:23 -0400
Message-ID: <1315686563.718.119.camel@t410>
Mime-Version: 1.0
Cc: "krbdev@mit.edu" <krbdev@mit.edu>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
On Sat, 2011-09-10 at 15:30 -0400, Sam Hartman wrote:
> With the verfto merge, I find that when I'm debugging the KDC, I tend to
> get interrupted by signals a lot more than I used to.
I haven't noticed this yet, and there are no kill() calls in libev or
libverto. So, it would be helpful to collect more information.
The one case where I've seen something like this is when I'm debugging a
k5test.py or dejagnu test case and I let the script terminate. For
example, if I use k5test.py's --stop-before=N, attach to the KDC, and
then let the script continue, the client program will typically time
out, causing the script to fail out and kill the KDC. I work around
this by using --stop-after=N in addition to --stop-before=N. I would
guess that this isn't the case you're seeing, but I'm mentioning it just
in case.
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
