From owner-freebsd-ports@FreeBSD.ORG  Fri Jul 22 15:04:10 2011
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from apollo.emma.line.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by hub.freebsd.org (Postfix) with ESMTP id D68E71065673;
	Fri, 22 Jul 2011 15:04:09 +0000 (UTC)
	(envelope-from mandree@FreeBSD.org)
Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1])
	by apollo.emma.line.org (Postfix) with ESMTP id 1D16B23D0A9;
	Fri, 22 Jul 2011 12:33:55 +0200 (CEST)
Message-ID: <4E295212.3000702@FreeBSD.org>
Date: Fri, 22 Jul 2011 12:33:54 +0200
From: Matthias Andree <mandree@FreeBSD.org>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
	rv:1.9.2.18) Gecko/20110617 Mnenhy/0.8.3 Thunderbird/3.1.11
MIME-Version: 1.0
To: freebsd-ports@freebsd.org
References: <000001cc4855$b0850770$118f1650$@comcast.net>
In-Reply-To: <000001cc4855$b0850770$118f1650$@comcast.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: douglas@t2web.com.br, ET-SR@comcast.net
Subject: Re: FreeBSD Port: bnc-2.9.4
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jul 2011 15:04:10 -0000

Am 22.07.2011 11:56, schrieb ET-SR:
> Freebsd 8.2 64 bit o/s
> 
>  
> 
> Bnc2.9.4 compiles and runs - crashes (cores) on connect.  Logs don't show
> anything.
> 
>  
> 
> Is there a patch for freebsd 8.2 64 bit o/s?
> 
>  
> 
> If not would you like the core file?

The core file isn't useful because it's somewhat system-specific.

That would be useful BUT by default port corefiles aren't helpful
because most ports remove the debug information.

1. reinstall bnc from ports, adding WITH_DEBUG=yes:

   cd /usr/ports/*/bnc
   make WITH_DEBUG=yes all deinstall install clean

   You could alternatively use: portmaster -m WITH_DEBUG=yes irc/bnc
   (if you've got portmaster installed)

2. run it so that it creates a fresh .core file

3. obtain a backtrace:

   script backtrace gdb /usr/local/bin/bnc /path/to/bnc.core

   inside gdb, type:

   bt
   bt full
   quit

4. check if the bt contains variable and function names or just hex
   numbers (numbers containing letters a - f) and possibly starting
   with 0x.  If it's only numbers, go to step 7.  Else continue with 5.

5. review the new backtrace file if it contains sensitive information
   (passwords or other) and if yes, make it up in an obvious way, such
   as overtyping XX or 99 for letters/digits.

6. send the edited backtrace file to the maintainer,
   douglas@t2web.com.br; be sure
   to include irc/bnc early in the subject.

   ONLY file a PR with the backtrace if you're confident there is no
   sensitive information in it.  Omit step 7.
------

7. If the "bt" output did not contain function and variable names,
   that is a bug per se, but the core file and results aren't helpful
   for debugging, so just file that as a bug report together with the
   crash with send-pr (similar to step 6, add irc/bnc up front in the
   Subject or Synopsys line).

It's a bit of an effort but else the maintainer won't get the necessary
information.

Thanks a bunch!