From owner-freebsd-current@FreeBSD.ORG Mon Jul 2 15:02:04 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 85FFA16A421 for ; Mon, 2 Jul 2007 15:02:04 +0000 (UTC) (envelope-from dfr@rabson.org) Received: from mail.qubesoft.com (gate.qubesoft.com [217.169.36.34]) by mx1.freebsd.org (Postfix) with ESMTP id 25B2113C46E for ; Mon, 2 Jul 2007 15:02:03 +0000 (UTC) (envelope-from dfr@rabson.org) Received: from [10.201.19.245] (doug02.dyn.qubesoft.com [10.201.19.245]) by mail.qubesoft.com (8.13.3/8.13.3) with ESMTP id l62F1vHq029573; Mon, 2 Jul 2007 16:01:57 +0100 (BST) (envelope-from dfr@rabson.org) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <51FE1AA5-8025-4FF3-94F5-617646464214@rabson.org> Content-Transfer-Encoding: 7bit From: Doug Rabson Date: Mon, 2 Jul 2007 16:01:56 +0100 To: Ian FREISLICH X-Mailer: Apple Mail (2.752.2) X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.0.4 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.qubesoft.com X-Virus-Scanned: ClamAV 0.86.2/3574/Mon Jul 2 09:07:06 2007 on mail.qubesoft.com X-Virus-Status: Clean Cc: current@freebsd.org Subject: Re: ssh coredump if gssapi-with-mic preferred, but no kinit done (yet)? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jul 2007 15:02:04 -0000 On 2 Jul 2007, at 15:17, Ian FREISLICH wrote: > Ian FREISLICH wrote: >> Doug Rabson wrote: >>> On 1 Jul 2007, at 19:38, David Wolfskill wrote: >>> >>>> I'm willing to try some things on the machine to help diagnose the >>>> problem(s) under CURRENT, but there are some things I'd like to do >>>> with it (that will take a few hours,such as a "make release") that >>>> I'd much rather do while it's running STABLE. And Sundays are >>>> about the >>>> only days I can really count on being able to do anything with >>>> CURRENT >>>> on the machine. (I'm in US/PAcific time zone.) >>>> >>>> So: clues? Would building a debugging version of ssh be a >>>> reasonable >>>> step? >>> >>> I may have broken this with my last commit to the gss-api code. I'll >>> try to take a look at this as soon as I fix my FreeBSD scratch >>> box (I >>> managed to fry its motherboard yesterday). In the meantime, could >>> you >>> get a stack-trace so I can at least see where its crashing. If you >>> can build libgssapi with debugging information that would probably >>> help a lot. >> >> It's quite a mangled stack trace. I saw a similar trace in the >> recent nmh core dump problem - not sure if you followed that thread. > > Not sure why the list truncated the stack trace. Hopefully this > makes it through. > > 0 0x280eec71 in _gss_oid_equal () from /usr/lib/libgssapi.so.8 > (gdb) bt > 0 0x280eec71 in _gss_oid_equal () from /usr/lib/libgssapi.so.8 > 1 0x280eeb78 in _gss_find_mech_switch () from /usr/lib/libgssapi.so.8 > 2 0x280ecffd in gss_display_status () from /usr/lib/libgssapi.so.8 It looks like I did break it. I should be able to repro and fix this as soon as I put my FreeBSD box back together (probably tomorrow). In the meantime, you can avoid this by rolling src/lib/libgssapi back to about last Friday or so.