[29252] in Kerberos

home help back first fref pref prev next nref lref last post

Re: kadmin.local segfault gdb output (valgrind output)

daemon@ATHENA.MIT.EDU (Ken Raeburn)
Wed Feb 13 23:17:56 2008

In-Reply-To: <368759.26672.qm@web38503.mail.mud.yahoo.com>
Mime-Version: 1.0 (Apple Message framework v753)
Message-Id: <B6E6F3C0-AAA8-44F0-AA8B-AD0A08EC6AD2@mit.edu>
From: Ken Raeburn <raeburn@mit.edu>
Date: Wed, 13 Feb 2008 23:17:26 -0500
To: Steven Miller <stevenraymillerjr@yahoo.com>
Cc: kerberos@mit.edu
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@mit.edu

On Feb 13, 2008, at 20:57, Steven Miller wrote:
> Very weird, when running kadmin.local under valgrind,
> it does NOT segfault. I am including the valgrind
> output.

Here, valgrind is complaining about some uninitialized fields, and in  
the gdb stack trace, the program was copying data based on one of  
those same fields having a nonzero value.  If the uninitialized  
length field was nonzero, and the data pointer was null or garbage,  
the copy would fail.  So, it looks like valgrind did dig up a little  
more information on this bug.

Thanks, I'll see if I can track down what's going on.

Ken
________________________________________________
Kerberos mailing list           Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos

home help back first fref pref prev next nref lref last post