From owner-freebsd-questions@FreeBSD.ORG  Thu Jun  8 01:04:15 2006
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
X-Original-To: freebsd-questions@freebsd.org
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 880D716D08B
	for <freebsd-questions@freebsd.org>;
	Wed,  7 Jun 2006 22:46:05 +0000 (UTC)
	(envelope-from jnelson@epicsol.org)
Received: from epicsol.org (epicsol.org [66.102.119.253])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 37F3543D45
	for <freebsd-questions@freebsd.org>;
	Wed,  7 Jun 2006 22:46:05 +0000 (GMT)
	(envelope-from jnelson@epicsol.org)
Received: from epicsol.org (jnelson@localhost [127.0.0.1])
	by epicsol.org (8.13.6/8.13.6) with ESMTP id k57Mk4xx023308
	for <freebsd-questions@freebsd.org>;
	Wed, 7 Jun 2006 17:46:04 -0500 (CDT)
	(envelope-from jnelson@epicsol.org)
Message-Id: <200606072246.k57Mk4xx023308@epicsol.org>
To: freebsd-questions@freebsd.org
Date: Wed, 07 Jun 2006 17:46:04 -0500
From: Jeremy Nelson <jnelson@epicsol.org>
Subject: Spontaneous reboot involving 6-stable, gdb, and -pthread
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Jun 2006 01:04:16 -0000


I am trying to collect enough information to file a bug report about a 
problem I am running into.  

I have two separate machines:
	Machine 1 is running 6.1-RC/amd64
	Machine 2 first was running 5.4-RELEASE/amd64
	Machine 2 then it ran 5-STABLE/amd64
	Machine 2 now it runs 6-STABLE/amd64 from monday.

If I build ftp://ftp.epicsol.org/pub/epic/EPIC5/epic5-0.2.0.tar.gz,
(the update for the irc/epic5 port hasn't been comitted yet) and manually
add -pthread to LDFLAGS, and run the binary under /usr/bin/gdb, the machine 
spontaneously reboots.  It doesn't appear to be a panic, because I've 
compiled a debugging kernel with DDB and KDB, etc, and it does not trap 
to the kernel debugger, just a reboot, as though I had hit the reset switch.

I've successfully reproduced this 100% of the time I've tried it on multiple
machines, on multiple branches of freebsd.  I have not (yet) been able to
test it on i386, so I don't (yet) know if it's amd64-related.

The last thing I see before the reboot is:
	[New Thread 0x<address> (LWP <number>)]

I've found I can avoid the panic by doing any one of:
	1) Don't run under /usr/bin/gdb
	2) Use /usr/ports/devel/gdb6 instead of /usr/bin/gdb
	3) Remove the need to have -pthread in LDFLAGS

I don't have an /etc/libmap.conf on either machine.

Before I file a bug report, are there any other hints anyone can give me
for what I might be running across here?

(I am trying to fix this, because linking against ruby1.8 requires -pthread,
 so this is something new that I'm getting bug reports for.)

Thanks,
Jeremy Nelson