[11533] in Kerberos-V5-bugs
[krbdev.mit.edu #6710] Re: [krbdev.mit.edu #6721] Compilation fails
daemon@ATHENA.MIT.EDU (Tom Yu via RT)
Thu May 13 14:25:06 2010
Mail-followup-to: rt@krbdev.mit.edu
mail-copies-to: never
From: "Tom Yu via RT" <rt-comment@krbdev.MIT.EDU>
In-Reply-To: <rt-6710@krbdev.mit.edu>
Message-ID: <rt-6710-32796.2.4795289855863@krbdev.mit.edu>
To: "'AdminCc of krbdev.mit.edu Ticket #6710'":;"'AdminCc of krbdev.mit.edu Ticket #6710'":;@MIT.EDU
Date: Thu, 13 May 2010 14:25:04 -0400 (EDT)
Reply-To: rt-comment@krbdev.MIT.EDU
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krb5-bugs-bounces@mit.edu
"Russ Allbery <rra@stanford.edu> via RT" <rt-comment@krbdev.mit.edu>
writes:
> I needed to build the current tree with -DDEBUG to debug a PKINIT issue
> and discovered when doing so that the kadmin code doesn't build with
> -DDEBUG. It defines a debugging macro to xprintf, which is not defined
> anywhere in the tree.
What's probably best is to run "make CPPFLAGS=-DDEBUG" in the
directory (pkinit?) where you want the debugging code turned on. I
think that's the general way that people operate when they're
debugging something they've added debugging code to. (and we should
document this better) Are there specific pieces of debugging code you
need working in kadmin?
_______________________________________________
krb5-bugs mailing list
krb5-bugs@mit.edu
https://mailman.mit.edu/mailman/listinfo/krb5-bugs
