From owner-freebsd-current@FreeBSD.ORG Sun Jun 23 20:36:18 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 2809EA33 for ; Sun, 23 Jun 2013 20:36:18 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from smtpauth4.wiscmail.wisc.edu (wmauth4.doit.wisc.edu [144.92.197.145]) by mx1.freebsd.org (Postfix) with ESMTP id 04B0B1C70 for ; Sun, 23 Jun 2013 20:36:17 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Received: from avs-daemon.smtpauth4.wiscmail.wisc.edu by smtpauth4.wiscmail.wisc.edu (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) id <0MOV00A004XEY900@smtpauth4.wiscmail.wisc.edu> for freebsd-current@freebsd.org; Sun, 23 Jun 2013 15:36:11 -0500 (CDT) X-Spam-PmxInfo: Server=avs-4, Version=6.0.2.2308539, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2013.6.23.202133, SenderIP=0.0.0.0 X-Spam-Report: AuthenticatedSender=yes, SenderIP=0.0.0.0 Received: from comporellon.tachypleus.net (unknown [76.210.63.131]) by smtpauth4.wiscmail.wisc.edu (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) with ESMTPSA id <0MOV00AA458ANT00@smtpauth4.wiscmail.wisc.edu> for freebsd-current@freebsd.org; Sun, 23 Jun 2013 15:36:10 -0500 (CDT) Message-id: <51C75C39.8060100@freebsd.org> Date: Sun, 23 Jun 2013 15:36:09 -0500 From: Nathan Whitehorn User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130615 Thunderbird/17.0.6 To: freebsd-current@freebsd.org Subject: Re: dialog4ports crashing in head recently References: In-reply-to: X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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: Sun, 23 Jun 2013 20:36:18 -0000 On 06/23/13 14:52, Dan Mack wrote: > dialog4ports has been crashing on all of my systems for about the last > week. I rebuilt it with debug symbols and this is what I got (doesn't > matter which port is using it). > > Anyone else seeing this? > libdialog was updated recently. I had to rebuild dialog4ports after that to keep it from crashing. Maybe you have the same issue? -Nathan