From owner-freebsd-amd64@FreeBSD.ORG Sun May 30 12:53:17 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C30C16A4CE; Sun, 30 May 2004 12:53:17 -0700 (PDT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 334AE43D3F; Sun, 30 May 2004 12:53:17 -0700 (PDT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 2058972DCB; Sun, 30 May 2004 12:53:17 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 1E02D72DB5; Sun, 30 May 2004 12:53:17 -0700 (PDT) Date: Sun, 30 May 2004 12:53:17 -0700 (PDT) From: Doug White To: Sean McNeil In-Reply-To: <1085733682.1155.15.camel@server.mcneil.com> Message-ID: <20040530125215.O87435@carver.gumbysoft.com> References: <1085733682.1155.15.camel@server.mcneil.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: migrating -current machine to amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 May 2004 19:53:17 -0000 On Fri, 28 May 2004, Sean McNeil wrote: > Hi Folks, > > I just replaced my motherboard with an athlon64 and got everything > working great in 32-bit mode. I'm very interested in gradually moving > everything to 64-bit. So I tried the following: > > make TARGET_ARCH=amd64 buildworld > make TARGET_ARCH=amd64 buildkernel > make TARGET_ARCH=amd64 installkernel > > This gave me an amd64 kernel that started to boot but had some problems > looking for /libexec/ld-elf32.so.1. I tried copying ld-elf.so.1 to > ld-elf32.so.1 and got farther. But then later it core dumped with > swapon and sh. I can drop into sh, though, so I'm not sure why it core > dumped. amd64 doens't currently support a 32-bit world too well. You'll need to replace everything, which is hard to do iwith an upgrade-in-place. I'd recommend just reinstalling or upgrading via a CD. I know peter's been working on the mixed 32 bit mode stuff but I don't know what the status of that is. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Sun May 30 17:04:31 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A77F416A4CE for ; Sun, 30 May 2004 17:04:31 -0700 (PDT) Received: from mail.mcneil.com (rrcs-west-24-199-45-54.biz.rr.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 975BE43D31 for ; Sun, 30 May 2004 17:04:31 -0700 (PDT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 668D9FD095 for ; Sun, 30 May 2004 17:04:31 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00703-06 for ; Sun, 30 May 2004 17:04:31 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 0DBB9FD093 for ; Sun, 30 May 2004 17:04:30 -0700 (PDT) From: Sean McNeil To: freebsd-amd64@freebsd.org Content-Type: text/plain Message-Id: <1085961870.10347.0.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Sun, 30 May 2004 17:04:30 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com Subject: /lib32 or /lib/i386? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 May 2004 00:04:31 -0000 I've read some older threads that discussed the i386 compatability. Changes to are in place for using /libexec/ld-elf32.so.1 and mods to rtld-elf exist to support 32-bit libraries. Only, I see that the suggestions to use /lib/i386 and /usr/lib/i386 have not been incorporated. They are still /lib32 and /usr/lib32. What is the final decision on this? I am looking to go beyond bleeding edge here and don't want to end up doing things that are not the approved way. Sean From owner-freebsd-amd64@FreeBSD.ORG Mon May 31 10:46:08 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C378916A4CE for ; Mon, 31 May 2004 10:46:08 -0700 (PDT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1613743D39 for ; Mon, 31 May 2004 10:46:08 -0700 (PDT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 145D51FFDD3 for ; Mon, 31 May 2004 19:45:40 +0200 (CEST) Received: by transport.cksoft.de (Postfix, from userid 66) id 1FCBF1FF931; Mon, 31 May 2004 19:45:38 +0200 (CEST) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 60DBA154E2; Mon, 31 May 2004 17:44:59 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id 560911539E for ; Mon, 31 May 2004 17:45:00 +0000 (UTC) Date: Mon, 31 May 2004 17:45:00 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: FreeBSD amd64 mailing list Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Subject: crash: sysctls in dependend modules crash machine X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 May 2004 17:46:08 -0000 Hi, let's say module a defines a new sysctl node (SYSCTL_DECL in shared header file): --- cut a.c --- SYSCTL_NODE (, OID_AUTO, testsysctl, CTLFLAG_RW, 0, "Test kld dependend sysctls"); SYSCTL_NODE(_testsysctl, OID_AUTO, modulea, CTLFLAG_RW, 0, "module a"); int a = 1; SYSCTL_INT(_testsysctl_modulea, OID_AUTO, a, CTLFLAG_RW, &a, 0, "a"); --- / a.c --- and module b depends on module a and adds following: --- cut b.c --- SYSCTL_NODE(_testsysctl, OID_AUTO, moduleb, CTLFLAG_RW, 0, "module b"); int b = 1; SYSCTL_INT(_testsysctl_moduleb, OID_AUTO, b, CTLFLAG_RW, &b, 0, "b"); --- / b.c --- loading module a will work: noc# kldload -v ./test_sysctl_base.ko test_sysctl_base KLD loaded. Loaded ./test_sysctl_base.ko, id=4 noc# kldstat Id Refs Address Size Name 1 2 0xffffffff80100000 830ad8 kernel 4 1 0xffffffff98d76000 2c7 test_sysctl_base.ko BUT: loading module b will crash the machine: noc# cd ../b/ noc# kldload -v ./test_sysctl_b.ko (handwritten bt): sysctl_find_oidname+0x14 sysctl_register_oid+0x19 linker_file_register_sysctls+0x3c linker_load_file+0xe7 linker_load_module+0xd8 kldload+0xf3 sysctl+0x358 ... To reproduce you can find two quickly hacked up sample modules at http://sources.zabbadoz.net/freebsd/amd64/amd64-modules-sysctl.tbz tar xjvf amd64-modules-sysctl.tbz cd amd64-modules-sysctl/a make su kldload -v ./test_sysctl_base.ko exit kldstat cd ../b make su echo "be sure to mount your partitions ro now; I will crash" mount -u -o ro ... /usr / kldload -v ./test_sysctl_b.ko -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-amd64@FreeBSD.ORG Mon May 31 11:02:02 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6CAD216A4CE for ; Mon, 31 May 2004 11:02:02 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6708B43D1D for ; Mon, 31 May 2004 11:02:02 -0700 (PDT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.11/8.12.11) with ESMTP id i4VI1iTV022658 for ; Mon, 31 May 2004 11:01:44 -0700 (PDT) (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i4VI1hgf022652 for freebsd-amd64@freebsd.org; Mon, 31 May 2004 11:01:43 -0700 (PDT) (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 31 May 2004 11:01:43 -0700 (PDT) Message-Id: <200405311801.i4VI1hgf022652@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-amd64@FreeBSD.org Subject: Current problem reports assigned to you X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 May 2004 18:02:02 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/11/26] amd64/59713 amd64 Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 07C3216A4CE for ; Tue, 1 Jun 2004 07:23:30 -0700 (PDT) Received: from ns.fujimori.cache.waseda.ac.jp (ns.fujimori.cache.waseda.ac.jp [133.9.152.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7163243D48 for ; Tue, 1 Jun 2004 07:23:29 -0700 (PDT) (envelope-from fujimori@ns.fujimori.cache.waseda.ac.jp) Received: from ns.fujimori.cache.waseda.ac.jp (localhost [127.0.0.1]) i51ENRqT004666 for ; Tue, 1 Jun 2004 23:23:28 +0900 (JST) (envelope-from fujimori@ns.fujimori.cache.waseda.ac.jp) Message-Id: <200406011423.i51ENRqT004666@ns.fujimori.cache.waseda.ac.jp> To: freebsd-amd64@freebsd.org Date: Tue, 01 Jun 2004 23:23:27 +0900 From: Yoriaki FUJIMORI Subject: EPOX 8HDA3+ onboard 1Gb lan X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jun 2004 14:23:30 -0000 Dear folks, I am running FreeBSD 5.2 on EPOX8HDA3+ with 3com Gb ether by FreeBSD 5.2R. The motherboard is plugged with an amd64 cg core cpu with L2/1M. The bios is updated to the latest one. The box is a diskless PC, and I try to boot it via 3com 1Gb lan. But, at the end of boot process, the kernel panics and the system continues rebooting forever. The same kernel boots and runs perfectly on the same motherboard via 100mb fast ether. The same kernel runs perfectly also on other diskless PCs, which have got older amd64 (no cg core) and older bios. So, my guess is there is something wrong in the combination of FreeBSD5.2 3com driver and EPOX board. Has anyone of you got a similar experience? Thank you for your attention. yoriaki fujimori From owner-freebsd-amd64@FreeBSD.ORG Tue Jun 1 14:26:08 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D620016A4CE; Tue, 1 Jun 2004 14:26:08 -0700 (PDT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C34C43D54; Tue, 1 Jun 2004 14:26:08 -0700 (PDT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 0B42F1FFDD3; Tue, 1 Jun 2004 23:26:06 +0200 (CEST) Received: by transport.cksoft.de (Postfix, from userid 66) id 12DF61FF931; Tue, 1 Jun 2004 23:26:04 +0200 (CEST) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id F121515615; Tue, 1 Jun 2004 21:25:14 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id E621115600; Tue, 1 Jun 2004 21:25:14 +0000 (UTC) Date: Tue, 1 Jun 2004 21:25:14 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: Peter Wemm Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de cc: FreeBSD amd64 mailing list Subject: patch|hack: amd64 native cvsup with compress working X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jun 2004 21:26:09 -0000 Hi, I have compiled ezm3 and cvsup-without-gui from the sources with the files from http://people.freebsd.org/~peter/ezm3-amd64/ . As discussed in this thread[1] there still is a problem with compression (libz). [1] http://lists.freebsd.org/pipermail/freebsd-amd64/2004-February/thread.html#669 The following hack makes cvsup work with compression: --- hack/patch --- ! ! the problem seems to be that Ugzip.Z_BUF_ERROR = -5 but ! if status = -5 it actually is 4294967291 and not -5 ! ! most likely other negative values might have the same problem. ! --- suplib/src/GzipWr.m3.orig Tue Mar 4 19:26:23 2003 +++ suplib/src/GzipWr.m3 Tue Jun 1 21:06:41 2004 @@ -125,8 +125,8 @@ 0, ADR(self.wr.buff[self.wr.st]) + self.wr.cur - self.wr.lo, self.wr.hi - self.wr.cur, - Ugzip.Z_PARTIAL_FLUSH); - IF status # Ugzip.Z_OK AND status # Ugzip.Z_BUF_ERROR THEN + Ugzip.Z_SYNC_FLUSH); (* Z_PARTIAL_FLUSH will go away according to zlib.h*) + IF status # Ugzip.Z_OK AND status # 4294967291 AND status # Ugzip.Z_BUF_ERROR THEN RAISE Wr.Failure(GzipError.FromStatus(status)); END; self.wr.cur := self.wr.hi - self.strmp.avail_out; --- suplib/src/GzipRd.m3.orig Tue Jun 1 21:02:48 2004 +++ suplib/src/GzipRd.m3 Tue Jun 1 21:03:30 2004 @@ -168,7 +168,7 @@ ELSE RETURN RdClass.SeekResult.Eof; END; - ELSIF status # Ugzip.Z_OK AND status # Ugzip.Z_BUF_ERROR THEN + ELSIF status # Ugzip.Z_OK AND status # 4294967291 AND status # Ugzip.Z_BUF_ERROR THEN RAISE Rd.Failure(GzipError.FromStatus(status)); END; --- /hack/patch --- while one can reproduce the problem by using a Logger to print Fmt.Int(status) (* 4294967291 *) Fmt.Int(-5) (* -5 *) Fmt.Int(Ugzip.Z_BUF_ERROR) (* -5 *) I am still unsure where the problem comes from; but that's been my first hours looking at m3 and I will most likely not further dig into this. here my test. I picked out one file of those and it looked ok. --- cut --- bz@noc:/u2/ports/net/cvsup-without-gui/work/cvsup-snap-16.1h/client/FBSD_AMD64> ./cvsup -g -L2 -z -s /u2/test/distrib-supfile Parsing supfile "/u2/test/distrib-supfile" Connecting to cvsup2.de.FreeBSD.org Connected to cvsup2.de.FreeBSD.org Server software version: SNAP_16_1h Negotiating file attribute support Exchanging collection information Establishing multiplexed-mode data connection Running Updating collection distrib/cvs Mkdir distrib Mkdir distrib/cvsup Mkdir distrib/cvsup/sup Create distrib/cvsup/sup/README,v Mkdir distrib/cvsup/sup/cvs-all Create distrib/cvsup/sup/cvs-all/list.cvs,v Create distrib/cvsup/sup/cvs-all/releases,v ... SetAttrs distrib/cvsup/sup/www SetAttrs distrib/cvsup/sup Create distrib/cvsup/supfile,v SetAttrs distrib/cvsup SetAttrs distrib Shutting down connection to server Finished successfully --- cut --- -- Greetings Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-amd64@FreeBSD.ORG Tue Jun 1 19:07:56 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A14A216A4CE for ; Tue, 1 Jun 2004 19:07:56 -0700 (PDT) Received: from mail.mcneil.com (rrcs-west-24-199-45-54.biz.rr.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 79FAE43D2D for ; Tue, 1 Jun 2004 19:07:54 -0700 (PDT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 2EFACFD079 for ; Tue, 1 Jun 2004 19:07:53 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 03704-05 for ; Tue, 1 Jun 2004 19:07:28 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id B262BFD01A for ; Tue, 1 Jun 2004 19:07:27 -0700 (PDT) From: Sean McNeil To: freebsd-amd64@freebsd.org Content-Type: text/plain Message-Id: <1086142046.36268.5.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Tue, 01 Jun 2004 19:07:27 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com Subject: cvsup.... help! X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 02:07:56 -0000 I've managed to almost convert (almost) everything over to amd64 now on my machine. There are several issues, but the most pressing at the moment is that I don't have a good cvsup. The ports Makefile that I had was trying to grab a binary that wasn't there and it will not build one when I try to hack it. Can someone supply me with good a good Makefile for cvsup and ezm3 or a static cvsup that I can use to bring my ports and src up-to-date? Thanks in advance, Sean From owner-freebsd-amd64@FreeBSD.ORG Tue Jun 1 19:12:57 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7997916A4CE; Tue, 1 Jun 2004 19:12:57 -0700 (PDT) Received: from mail.mcneil.com (rrcs-west-24-199-45-54.biz.rr.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 653F243D2F; Tue, 1 Jun 2004 19:12:57 -0700 (PDT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 28C40FD079; Tue, 1 Jun 2004 19:12:57 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 03704-06; Tue, 1 Jun 2004 19:12:56 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id A4326FD01A; Tue, 1 Jun 2004 19:12:56 -0700 (PDT) From: Sean McNeil To: freebsd-amd64@freebsd.org, freebsd-gnome@freebsd.org, freebsd-ports@freebsd.org Content-Type: text/plain Message-Id: <1086142376.36268.12.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Tue, 01 Jun 2004 19:12:56 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com Subject: Bad links with *.a libs for shared objects and bad patch X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 02:12:57 -0000 While compiling all the ports over from i386 to amd64 arch, I found a few I use had issues with making shared libraries with non-shared libs that were compiled without -fPIC. These were: multimedia/mpeg4ip mail/evolution What I ended up doing to get these to build was add the following to my /etc/make.conf temporarily to build them: CFLAGS= -O -pipe -fPIC Also, there is a patch to multimedia/gxine that is no good for amd64: files/patch-src::spidermonkey::jsprf.c Deleting this patch will allow gxine to compile. Cheers, Sean From owner-freebsd-amd64@FreeBSD.ORG Tue Jun 1 19:27:09 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0EAF416A4CE; Tue, 1 Jun 2004 19:27:09 -0700 (PDT) Received: from creme-brulee.marcuscom.com (rrcs-midsouth-24-172-16-118.biz.rr.com [24.172.16.118]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E2C543D5E; Tue, 1 Jun 2004 19:27:08 -0700 (PDT) (envelope-from marcus@marcuscom.com) Received: from [192.168.1.4] (shumai.marcuscom.com [192.168.1.4]) i522QqlT025518; Tue, 1 Jun 2004 22:26:52 -0400 (EDT) (envelope-from marcus@marcuscom.com) From: Joe Marcus Clarke To: Sean McNeil In-Reply-To: <1086142376.36268.12.camel@server.mcneil.com> References: <1086142376.36268.12.camel@server.mcneil.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-esRCoLMZVWcE258bDtIm" Organization: MarcusCom, Inc. Message-Id: <1086143225.21857.8.camel@shumai.marcuscom.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Tue, 01 Jun 2004 22:27:05 -0400 X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on creme-brulee.marcuscom.com cc: freebsd-ports@freebsd.org cc: freebsd-gnome@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: Bad links with *.a libs for shared objects and bad patch X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 02:27:09 -0000 --=-esRCoLMZVWcE258bDtIm Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Tue, 2004-06-01 at 22:12, Sean McNeil wrote: > While compiling all the ports over from i386 to amd64 arch, I found a > few I use had issues with making shared libraries with non-shared libs > that were compiled without -fPIC. >=20 > These were: >=20 > multimedia/mpeg4ip > mail/evolution Evolution-1.4.6 should compile out of the box on FreeBSD amd64. I recently pulled some amd64 patches after being told by one amd64 user that they were no longer needed. Joe >=20 --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-esRCoLMZVWcE258bDtIm Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBAvTr5b2iPiv4Uz4cRAldLAKCvhKG9HsG8R0QhPVPCzaW9NXrP9gCgjHg/ 8JentiSray3xFOw2fMYg3Ts= =BWUs -----END PGP SIGNATURE----- --=-esRCoLMZVWcE258bDtIm-- From owner-freebsd-amd64@FreeBSD.ORG Tue Jun 1 19:47:47 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C8D8E16A4CE for ; Tue, 1 Jun 2004 19:47:47 -0700 (PDT) Received: from smtp01.syd.iprimus.net.au (smtp01.syd.iprimus.net.au [210.50.30.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0220343D31 for ; Tue, 1 Jun 2004 19:47:47 -0700 (PDT) (envelope-from tim@robbins.dropbear.id.au) Received: from robbins.dropbear.id.au (210.50.80.90) by smtp01.syd.iprimus.net.au (7.0.024) id 40B7A0DA0014753A; Wed, 2 Jun 2004 12:47:45 +1000 Received: by robbins.dropbear.id.au (Postfix, from userid 1000) id B91BA41CE; Wed, 2 Jun 2004 12:48:38 +1000 (EST) Date: Wed, 2 Jun 2004 12:48:38 +1000 From: Tim Robbins To: Sean McNeil Message-ID: <20040602024838.GA8782@cat.robbins.dropbear.id.au> References: <1086142046.36268.5.camel@server.mcneil.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1086142046.36268.5.camel@server.mcneil.com> User-Agent: Mutt/1.4.1i cc: freebsd-amd64@freebsd.org Subject: Re: cvsup.... help! X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 02:47:47 -0000 On Tue, Jun 01, 2004 at 07:07:27PM -0700, Sean McNeil wrote: > I've managed to almost convert (almost) everything over to amd64 now on > my machine. There are several issues, but the most pressing at the > moment is that I don't have a good cvsup. The ports Makefile that I had > was trying to grab a binary that wasn't there and it will not build one > when I try to hack it. > > Can someone supply me with good a good Makefile for cvsup and ezm3 or a > static cvsup that I can use to bring my ports and src up-to-date? This one works fine as long as you don't use compression: http://people.freebsd.org/~peter/cvsup-without-gui-16.1h.tbz Tim From owner-freebsd-amd64@FreeBSD.ORG Tue Jun 1 20:00:51 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A21016A4CE; Tue, 1 Jun 2004 20:00:51 -0700 (PDT) Received: from smtp01.syd.iprimus.net.au (smtp01.syd.iprimus.net.au [210.50.30.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7ECD743D49; Tue, 1 Jun 2004 20:00:50 -0700 (PDT) (envelope-from tim@robbins.dropbear.id.au) Received: from robbins.dropbear.id.au (210.50.80.90) by smtp01.syd.iprimus.net.au (7.0.024) id 40B7A0DA0014805B; Wed, 2 Jun 2004 13:00:49 +1000 Received: by robbins.dropbear.id.au (Postfix, from userid 1000) id 675DB41CE; Wed, 2 Jun 2004 13:01:30 +1000 (EST) Date: Wed, 2 Jun 2004 13:01:30 +1000 From: Tim Robbins To: Sean McNeil Message-ID: <20040602030130.GB8782@cat.robbins.dropbear.id.au> References: <1086142376.36268.12.camel@server.mcneil.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1086142376.36268.12.camel@server.mcneil.com> User-Agent: Mutt/1.4.1i cc: freebsd-ports@freebsd.org cc: freebsd-gnome@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: Bad links with *.a libs for shared objects and bad patch X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 03:00:51 -0000 On Tue, Jun 01, 2004 at 07:12:56PM -0700, Sean McNeil wrote: > While compiling all the ports over from i386 to amd64 arch, I found a > few I use had issues with making shared libraries with non-shared libs > that were compiled without -fPIC. > > These were: > > multimedia/mpeg4ip > mail/evolution > > What I ended up doing to get these to build was add the following to my > /etc/make.conf temporarily to build them: > > CFLAGS= -O -pipe -fPIC multimedia/mpeg4ip is (unfortunately) known to be broken on amd64 right now. Hopefully I will find some time to fix it this week. Tim From owner-freebsd-amd64@FreeBSD.ORG Tue Jun 1 20:35:39 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8E1F816A4CE for ; Tue, 1 Jun 2004 20:35:39 -0700 (PDT) Received: from mail.mcneil.com (rrcs-west-24-199-45-54.biz.rr.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DE0143D58 for ; Tue, 1 Jun 2004 20:35:37 -0700 (PDT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id CA488FD0C9 for ; Tue, 1 Jun 2004 20:35:36 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 53419-09 for ; Tue, 1 Jun 2004 20:35:36 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 01318FD0C8 for ; Tue, 1 Jun 2004 20:35:35 -0700 (PDT) From: Sean McNeil To: freebsd-amd64@freebsd.org Content-Type: text/plain Message-Id: <1086147335.27863.1.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Tue, 01 Jun 2004 20:35:35 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com Subject: gdb? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 03:35:39 -0000 I noticed that gdb isn't built for amd64. Is there debugger support for this architecture? What should I use to track down problems? Sean From owner-freebsd-amd64@FreeBSD.ORG Tue Jun 1 21:07:20 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CA8BC16A4CE for ; Tue, 1 Jun 2004 21:07:20 -0700 (PDT) Received: from smtp01.syd.iprimus.net.au (smtp01.syd.iprimus.net.au [210.50.30.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 42A5943D4C for ; Tue, 1 Jun 2004 21:07:20 -0700 (PDT) (envelope-from tim@robbins.dropbear.id.au) Received: from robbins.dropbear.id.au (210.50.80.90) by smtp01.syd.iprimus.net.au (7.0.024) id 40B7A0DA0014CD30; Wed, 2 Jun 2004 14:07:12 +1000 Received: by robbins.dropbear.id.au (Postfix, from userid 1000) id 93EE541D0; Wed, 2 Jun 2004 14:08:05 +1000 (EST) Date: Wed, 2 Jun 2004 14:08:05 +1000 From: Tim Robbins To: Sean McNeil Message-ID: <20040602040805.GC8782@cat.robbins.dropbear.id.au> References: <1086147335.27863.1.camel@server.mcneil.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1086147335.27863.1.camel@server.mcneil.com> User-Agent: Mutt/1.4.1i cc: freebsd-amd64@freebsd.org Subject: Re: gdb? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 04:07:20 -0000 On Tue, Jun 01, 2004 at 08:35:35PM -0700, Sean McNeil wrote: > I noticed that gdb isn't built for amd64. Is there debugger support for > this architecture? What should I use to track down problems? Install devel/gdb6 from ports. Apparently gdb 5 doesn't support amd64, and we're holding off importing gdb 6 into base for the moment (I don't know the reason.) Tim From owner-freebsd-amd64@FreeBSD.ORG Tue Jun 1 21:52:29 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EF54416A4CE for ; Tue, 1 Jun 2004 21:52:29 -0700 (PDT) Received: from mail.mcneil.com (rrcs-west-24-199-45-54.biz.rr.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id B710943D2D for ; Tue, 1 Jun 2004 21:52:29 -0700 (PDT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id E55BFFD05A; Tue, 1 Jun 2004 21:52:25 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 82868-06; Tue, 1 Jun 2004 21:52:25 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 67737FD01A; Tue, 1 Jun 2004 21:52:25 -0700 (PDT) From: Sean McNeil To: Tim Robbins In-Reply-To: <20040602040805.GC8782@cat.robbins.dropbear.id.au> References: <1086147335.27863.1.camel@server.mcneil.com> <20040602040805.GC8782@cat.robbins.dropbear.id.au> Content-Type: text/plain Message-Id: <1086151945.1411.3.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Tue, 01 Jun 2004 21:52:25 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com cc: freebsd-amd64@freebsd.org Subject: Re: gdb? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 04:52:30 -0000 On Tue, 2004-06-01 at 21:08, Tim Robbins wrote: > On Tue, Jun 01, 2004 at 08:35:35PM -0700, Sean McNeil wrote: > > > I noticed that gdb isn't built for amd64. Is there debugger support for > > this architecture? What should I use to track down problems? > > Install devel/gdb6 from ports. Apparently gdb 5 doesn't support amd64, > and we're holding off importing gdb 6 into base for the moment (I don't > know the reason.) > > > Tim Thanks, Tim. Unfortunately I cannot install gdb6 right now. The current snapshot is nowhere to be found (2004-05-11). Sean From owner-freebsd-amd64@FreeBSD.ORG Tue Jun 1 22:01:23 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E516C16A4CE for ; Tue, 1 Jun 2004 22:01:23 -0700 (PDT) Received: from mail.mcneil.com (rrcs-west-24-199-45-54.biz.rr.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id ABAED43D48 for ; Tue, 1 Jun 2004 22:01:23 -0700 (PDT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 7540EFD05A for ; Tue, 1 Jun 2004 22:01:23 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 26229-05 for ; Tue, 1 Jun 2004 22:01:23 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 3506DFD01A for ; Tue, 1 Jun 2004 22:01:23 -0700 (PDT) From: Sean McNeil To: freebsd-amd64@freebsd.org Content-Type: text/plain Message-Id: <1086152483.1411.14.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Tue, 01 Jun 2004 22:01:23 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com Subject: core dumps with bash, nautilus, and gnome-vfs-daemon X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 05:01:24 -0000 This happens with -CURRENT and all recent ports built on an amd64 arch. I have the core files and will do a trace when I get a working debugger. bash core dumps when I resize a gnome-terminal window. gnome-vfs-daemon and nautilus core dump when I try to start nautilus. If I do it from a gnome-terminal, I get the following output: nautilus in free(): error: junk pointer, too high to make sense nautilus in malloc(): error: recursive call nautilus in malloc(): error: recursive call Abort trap (core dumped) Cheers, Sean From owner-freebsd-amd64@FreeBSD.ORG Tue Jun 1 22:04:25 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 95F9A16A4CE for ; Tue, 1 Jun 2004 22:04:25 -0700 (PDT) Received: from carebears.mine.nu (ti400720a080-10274.bb.online.no [83.108.232.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4044843D45 for ; Tue, 1 Jun 2004 22:04:25 -0700 (PDT) (envelope-from solskogen@carebears.mine.nu) Received: from localhost (unknown [127.0.0.1]) by carebears.mine.nu (Postfix) with ESMTP id CBF2F483CAC for ; Wed, 2 Jun 2004 07:02:54 +0200 (CEST) Received: from carebears.mine.nu ([127.0.0.1]) by localhost (wish.carebears.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 59177-02 for ; Wed, 2 Jun 2004 07:02:49 +0200 (CEST) Received: from [192.168.0.9] (funshine.carebears.net [192.168.0.9]) by carebears.mine.nu (Postfix) with ESMTP id 23EC0483C66 for ; Wed, 2 Jun 2004 07:02:49 +0200 (CEST) From: Christer Solskogen To: freebsd-amd64@freebsd.org In-Reply-To: <1086152483.1411.14.camel@server.mcneil.com> References: <1086152483.1411.14.camel@server.mcneil.com> Content-Type: text/plain Message-Id: <1086152642.38535.0.camel@funshine.carebears.net> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 02 Jun 2004 07:04:02 +0200 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavis at wish.carebears.net Subject: Re: core dumps with bash, nautilus, and gnome-vfs-daemon X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 05:04:25 -0000 On Wed, 2004-06-02 at 07:01, Sean McNeil wrote: > This happens with -CURRENT and all recent ports built on an amd64 arch. > I have the core files and will do a trace when I get a working debugger. > Just switched to CURRENT? Try reinstall all of your ports. (portupgrade -af) -- Med Vennlig Hilsen / Best regards Christer Solskogen http://carebears.mine.nu/~solskogen It's always the wrong time of the month. From owner-freebsd-amd64@FreeBSD.ORG Tue Jun 1 22:18:23 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3BD4116A4CE; Tue, 1 Jun 2004 22:18:23 -0700 (PDT) Received: from mail.mcneil.com (rrcs-west-24-199-45-54.biz.rr.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 25E5843D55; Tue, 1 Jun 2004 22:18:23 -0700 (PDT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id DC719FD05A; Tue, 1 Jun 2004 22:18:22 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 56260-01; Tue, 1 Jun 2004 22:18:22 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 5F23BFD01A; Tue, 1 Jun 2004 22:18:22 -0700 (PDT) From: Sean McNeil To: Joe Marcus Clarke In-Reply-To: <1086152746.21857.12.camel@shumai.marcuscom.com> References: <1086152406.1411.12.camel@server.mcneil.com> <1086152746.21857.12.camel@shumai.marcuscom.com> Content-Type: text/plain Message-Id: <1086153502.41019.4.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Tue, 01 Jun 2004 22:18:22 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com cc: freebsd-gnome@freebsd.org cc: freebsd-ports@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: core dumps with bash, nautilus, and gnome-vfs-daemon X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 05:18:23 -0000 sorry for the dup, but want to make sure it goes out the othe right mailing lists. I had a typo before.... On Tue, 2004-06-01 at 22:05, Joe Marcus Clarke wrote: > On Wed, 2004-06-02 at 01:00, Sean McNeil wrote: > > This happens with -CURRENT and all recent ports built on an amd64 arch. > > I have the core files and will do a trace when I get a working debugger. > > > > bash core dumps when I resize a gnome-terminal window. > > > > gnome-vfs-daemon and nautilus core dump when I try to start nautilus. > > If I do it from a gnome-terminal, I get the following output: > > > > nautilus in free(): error: junk pointer, too high to make sense > > nautilus in malloc(): error: recursive call > > nautilus in malloc(): error: recursive call > > Abort trap (core dumped) > > These are standard malloc issues. If you do ln -s aj /etc/malloc.conf, > do these crashes go away? > > Joe When I do that, I no longer get core, but I get nautilus nautilus in free(): warning: junk pointer, too high to make sense nautilus in free(): warning: junk pointer, too high to make sense and then the application error dialog asking to restart, close, or send report. Sean From owner-freebsd-amd64@FreeBSD.ORG Tue Jun 1 23:48:52 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3392216A4CE for ; Tue, 1 Jun 2004 23:48:52 -0700 (PDT) Received: from VARK.homeunix.com (ar59.lsanca2-4.27.98.47.lsanca2.dsl-verizon.net [4.27.98.47]) by mx1.FreeBSD.org (Postfix) with ESMTP id E63BA43D1D for ; Tue, 1 Jun 2004 23:48:51 -0700 (PDT) (envelope-from das@FreeBSD.ORG) Received: from VARK.homeunix.com (localhost [127.0.0.1]) by VARK.homeunix.com (8.12.10/8.12.10) with ESMTP id i526mlkj006232 for ; Tue, 1 Jun 2004 23:48:47 -0700 (PDT) (envelope-from das@FreeBSD.ORG) Received: (from das@localhost) by VARK.homeunix.com (8.12.11/8.12.10/Submit) id i526ml8G006231 for amd64@FreeBSD.ORG; Tue, 1 Jun 2004 23:48:47 -0700 (PDT) (envelope-from das@FreeBSD.ORG) Date: Tue, 1 Jun 2004 23:48:46 -0700 From: David Schultz To: amd64@FreeBSD.ORG Message-ID: <20040602064846.GA6124@VARK.homeunix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: Initial FP exception flags incorrect on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 06:48:52 -0000 I discovered that new processes on amd64 have the inexact flag raised by default, at least on sledge. However, all the sticky flags should be clear initially. Here is a program that demonstrates the problem: #include int main(int argc, char *argv[]) { int r; __asm("stmxcsr %0" : "=m" (r)); printf("got 0x%02x, expecting 0x00\n", r & 0x3f); } I don't have any amd64 hardware of my own to test kernel patches on, but if I were to make a wild guess as to how to solve the problem, it would be the following patch. I would appreciate it if someone could address the problem, or at least let me know whether my proposed fix works. Index: sys/amd64/amd64/fpu.c =================================================================== RCS file: /cvs/src/sys/amd64/amd64/fpu.c,v retrieving revision 1.149 diff -u -r1.149 fpu.c --- fpu.c 5 Apr 2004 21:25:51 -0000 1.149 +++ fpu.c 2 Jun 2004 06:08:34 -0000 @@ -73,6 +73,7 @@ #define fnstsw(addr) __asm __volatile("fnstsw %0" : "=m" (*(addr))) #define fxrstor(addr) __asm("fxrstor %0" : : "m" (*(addr))) #define fxsave(addr) __asm __volatile("fxsave %0" : "=m" (*(addr))) +#define stmxcsr(addr) __asm("stmxcsr %0" : "=m" (*(addr))) #define start_emulating() __asm("smsw %%ax; orb %0,%%al; lmsw %%ax" \ : : "n" (CR0_TS) : "ax") #define stop_emulating() __asm("clts") @@ -119,6 +120,8 @@ fninit(); control = __INITIAL_FPUCW__; fldcw(&control); + control = __INITIAL_MXCSR__; + stmxcsr(&control); fxsave(&fpu_cleanstate); start_emulating(); fpu_cleanstate_ready = 1; From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 2 02:19:00 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3014516A4CE for ; Wed, 2 Jun 2004 02:19:00 -0700 (PDT) Received: from mail.mcneil.com (rrcs-west-24-199-45-54.biz.rr.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0CA3743D58 for ; Wed, 2 Jun 2004 02:18:58 -0700 (PDT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 21E3EFD03A for ; Wed, 2 Jun 2004 02:19:00 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00849-01 for ; Wed, 2 Jun 2004 02:18:59 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 8C981FD020 for ; Wed, 2 Jun 2004 02:18:59 -0700 (PDT) From: Sean McNeil To: freebsd-amd64@freebsd.org Content-Type: text/plain Message-Id: <1086167939.2511.9.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 02 Jun 2004 02:18:59 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com Subject: firefox dies when anything typed in search or test fields X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 09:19:00 -0000 I'm not getting any core dump or other indication of an error, but when I type a single character into the search text widget or if I go to google.com and type a character in the search for that then firefox will crash. Sean From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 2 02:33:24 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CF9AF16A4CF for ; Wed, 2 Jun 2004 02:33:24 -0700 (PDT) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id B2C4943D31 for ; Wed, 2 Jun 2004 02:33:23 -0700 (PDT) (envelope-from adridg@cs.kun.nl) Received: from odin.cs.kun.nl [131.174.33.33] (helo=localhost.ebn.kun.nl) by pandora.cs.kun.nl (8.12.10/3.67) with ESMTP id i529XMKa012254 for ; Wed, 2 Jun 2004 11:33:22 +0200 (MEST) From: Adriaan de Groot To: freebsd-amd64@freebsd.org Date: Wed, 2 Jun 2004 11:34:16 +0200 User-Agent: KMail/1.6.52 References: <1086142376.36268.12.camel@server.mcneil.com> In-Reply-To: <1086142376.36268.12.camel@server.mcneil.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <200406021134.18117.adridg@cs.kun.nl> Subject: Re: Bad links with *.a libs for shared objects and bad patch X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 09:33:25 -0000 On Wednesday 02 June 2004 04:12, Sean McNeil wrote: > What I ended up doing to get these to build was add the following to my > /etc/make.conf temporarily to build them: > > CFLAGS=3D -O -pipe -fPIC Just so long as you always always remember to take them out of make.conf=20 afterwards, lest you be labeled a moron (like I was when I forgot 'em, and= =20 couldn't build world afterwards). Setting CFLAGS on the make command line o= r=20 in the environment may have the same effect, and be safer. =2D-=20 "On top of that [watching KDE CVS] is interesting in a perverse=20 way, like watching sausage get made. By very smart people." - dkite From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 2 02:50:35 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 30E9D16A540; Wed, 2 Jun 2004 02:50:35 -0700 (PDT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C95643D1D; Wed, 2 Jun 2004 02:50:10 -0700 (PDT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id D89211FFDD5; Wed, 2 Jun 2004 11:50:08 +0200 (CEST) Received: by transport.cksoft.de (Postfix, from userid 66) id 097C21FFDD4; Wed, 2 Jun 2004 11:50:07 +0200 (CEST) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 24D6915600; Wed, 2 Jun 2004 09:41:14 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id 212EE154E5; Wed, 2 Jun 2004 09:41:15 +0000 (UTC) Date: Wed, 2 Jun 2004 09:41:15 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: Peter Wemm In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de cc: FreeBSD amd64 mailing list Subject: Re: patch: amd64 native cvsup with compress working X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 09:50:35 -0000 On Tue, 1 Jun 2004, Bjoern A. Zeeb wrote: Sorry for replying to myself but attached is an updated patch for amd64 cvsup to work with compression. The problem seems that zlib deflate returns an (c native) int that gets somehow mapped to an INTEGER directly or indirectly through the RETURN statements with the PROCEDURE returning an INTEGER. INTEGER on amd64 seems to be a long and not an int thus some conversion from the zlib return into m3 seems to lose signedness. The workaround is to use a Ctypes.int variable to temporary safe the return code from zlib and do the type convertion entirely in m3 which seems to work fine here. cvsupping release=cvs, src-all at the moment. --- cut --- --- suplib/src/GzipWr.m3.orig Tue Jun 1 21:09:44 2004 +++ suplib/src/GzipWr.m3 Wed Jun 2 08:59:02 2004 @@ -32,7 +32,7 @@ UNSAFE MODULE GzipWr; IMPORT GzipError, OSError, StreamWrClass, Thread, Ugzip, Wr, WrClass; -FROM Ctypes IMPORT unsigned_char_star; +FROM Ctypes IMPORT unsigned_char_star, int; REVEAL T = Public BRANDED OBJECT @@ -102,12 +102,15 @@ PROCEDURE Deflate(strmp: Ugzip.z_stream_ (* Call "Ugzip.deflate", making sure that pointers into the (traced) input and output buffers are on the stack or in registers. This ensures that the collector will not move the buffers. *) + VAR + rc: int; BEGIN strmp.next_in := next_in; strmp.avail_in := avail_in; strmp.next_out := next_out; strmp.avail_out := avail_out; - RETURN Ugzip.deflate(strmp, flush); + rc := Ugzip.deflate(strmp, flush); + RETURN rc; END Deflate; PROCEDURE Flush(self: T) --- suplib/src/GzipRd.m3.orig Tue Mar 4 19:26:22 2003 +++ suplib/src/GzipRd.m3 Wed Jun 2 08:59:22 2004 @@ -32,7 +32,7 @@ UNSAFE MODULE GzipRd; IMPORT GzipError, OSError, Rd, RdClass, StreamRdClass, Thread, Ugzip; -FROM Ctypes IMPORT unsigned_char_star; +FROM Ctypes IMPORT unsigned_char_star, int; REVEAL T = Public BRANDED OBJECT @@ -83,12 +83,15 @@ PROCEDURE Inflate(strmp: Ugzip.z_stream_ (* Call "Ugzip.inflate", making sure that pointers into the (traced) input and output buffers are on the stack or in registers. This ensures that the collector will not move the buffers. *) + VAR + rc: int; BEGIN strmp.next_in := next_in; strmp.avail_in := avail_in; strmp.next_out := next_out; strmp.avail_out := avail_out; - RETURN Ugzip.inflate(strmp, flush); + rc := Ugzip.inflate(strmp, flush); + RETURN rc; END Inflate; PROCEDURE Init(self: T; --- cut --- -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 2 02:50:36 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E55FC16A4DA for ; Wed, 2 Jun 2004 02:50:35 -0700 (PDT) Received: from smtp01.syd.iprimus.net.au (smtp01.syd.iprimus.net.au [210.50.30.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 23CB443D5F for ; Wed, 2 Jun 2004 02:50:22 -0700 (PDT) (envelope-from tim@robbins.dropbear.id.au) Received: from robbins.dropbear.id.au (210.50.80.204) by smtp01.syd.iprimus.net.au (7.0.024) id 40B7A0DA00162CFC; Wed, 2 Jun 2004 19:50:20 +1000 Received: by robbins.dropbear.id.au (Postfix, from userid 1000) id E3D3F41D0; Wed, 2 Jun 2004 19:51:15 +1000 (EST) Date: Wed, 2 Jun 2004 19:51:15 +1000 From: Tim Robbins To: Sean McNeil Message-ID: <20040602095115.GA10734@cat.robbins.dropbear.id.au> References: <1086167939.2511.9.camel@server.mcneil.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1086167939.2511.9.camel@server.mcneil.com> User-Agent: Mutt/1.4.1i cc: freebsd-amd64@freebsd.org Subject: Re: firefox dies when anything typed in search or test fields X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 09:50:36 -0000 On Wed, Jun 02, 2004 at 02:18:59AM -0700, Sean McNeil wrote: > I'm not getting any core dump or other indication of an error, but when > I type a single character into the search text widget or if I go to > google.com and type a character in the search for that then firefox will > crash. This has been frustrating me a lot lately. It seems to be a known problem with Firefox 0.8 on amd64 (not specific to FreeBSD): http://forums.gentoo.org/viewtopic.php?t=146823&highlight=firefox+amd64 http://bugzilla.mozilla.org/show_bug.cgi?id=244577 (???) The Gentoo forum posts suggest that turning off "Saved Form Information" and "Saved Passwords" (in Privacy options) and "Use Find As You Type" (in Advanced / Accessibility options) may help, but it didn't improve anything for me. I'm going to try plain Mozilla instead. Tim From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 2 03:22:06 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C57016A4CE for ; Wed, 2 Jun 2004 03:22:06 -0700 (PDT) Received: from mail.mcneil.com (rrcs-west-24-199-45-54.biz.rr.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id CAE0543D1D for ; Wed, 2 Jun 2004 03:22:05 -0700 (PDT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 25633FD020; Wed, 2 Jun 2004 03:21:54 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00849-04; Wed, 2 Jun 2004 03:21:53 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id AF1FCFD01A; Wed, 2 Jun 2004 03:21:53 -0700 (PDT) From: Sean McNeil To: Tim Robbins In-Reply-To: <20040602095115.GA10734@cat.robbins.dropbear.id.au> References: <1086167939.2511.9.camel@server.mcneil.com> <20040602095115.GA10734@cat.robbins.dropbear.id.au> Content-Type: text/plain Message-Id: <1086171713.37043.0.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 02 Jun 2004 03:21:53 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com cc: freebsd-amd64@freebsd.org Subject: Re: firefox dies when anything typed in search or test fields X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 10:22:06 -0000 On Wed, 2004-06-02 at 02:51, Tim Robbins wrote: > On Wed, Jun 02, 2004 at 02:18:59AM -0700, Sean McNeil wrote: > > > I'm not getting any core dump or other indication of an error, but when > > I type a single character into the search text widget or if I go to > > google.com and type a character in the search for that then firefox will > > crash. > > This has been frustrating me a lot lately. It seems to be a known problem > with Firefox 0.8 on amd64 (not specific to FreeBSD): > http://forums.gentoo.org/viewtopic.php?t=146823&highlight=firefox+amd64 > http://bugzilla.mozilla.org/show_bug.cgi?id=244577 (???) > > The Gentoo forum posts suggest that turning off "Saved Form Information" > and "Saved Passwords" (in Privacy options) and "Use Find As You Type" > (in Advanced / Accessibility options) may help, but it didn't improve > anything for me. I'm going to try plain Mozilla instead. > > > Tim Mozilla will probably work. Galeon doesn't have any issues for me so far. Sean From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 2 12:07:48 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 93FA616A55C; Wed, 2 Jun 2004 12:07:47 -0700 (PDT) Received: from mail.mcneil.com (rrcs-west-24-199-45-54.biz.rr.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 37AB343D48; Wed, 2 Jun 2004 12:07:47 -0700 (PDT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 5B87CFD03A; Wed, 2 Jun 2004 12:07:49 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 64856-05; Wed, 2 Jun 2004 12:07:49 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id E3211FD01A; Wed, 2 Jun 2004 12:07:48 -0700 (PDT) From: Sean McNeil To: freebsd-current@freebsd.org, freebsd-amd64@freebsd.org, freebsd-ports@freebsd.org Content-Type: text/plain Message-Id: <1086203268.18422.20.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 02 Jun 2004 12:07:48 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com Subject: bash core dump on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 19:07:49 -0000 I ended up compiling gdb from cvs in order to get a version I could work with and got a trace from my bash core dump when I try to resize a gnome-terminal window: (gdb) bt #0 0x00000002016ffab3 in sigaction () from /usr/lib/libpthread.so.1 #1 0x00000002006ae9b0 in _rl_savestring () from /lib/libreadline.so.4 #2 #3 0x0000000200a822ec in read () from /lib/libc.so.5 #4 0x00000002006ab113 in rl_getc () from /lib/libreadline.so.4 #5 0x00000002006ab0c9 in rl_read_key () from /lib/libreadline.so.4 #6 0x00000002006bdeb7 in readline_internal_char () from /lib/libreadline.so.4 #7 0x00000002006be045 in readline_internal_char () from /lib/libreadline.so.4 #8 0x00000002006be060 in readline_internal_char () from /lib/libreadline.so.4 #9 0x00000002006bdc1e in readline () from /lib/libreadline.so.4 #10 0x0000000000415072 in yy_input_name () #11 0x0000000000414fde in yy_input_name () #12 0x0000000000415885 in read_secondary_line () #13 0x000000000041633e in reset_parser () #14 0x0000000000415e22 in execute_prompt_command () #15 0x0000000000413b1a in yyparse () #16 0x00000000004138ab in parse_command () #17 0x000000000041395b in read_command () #18 0x0000000000413701 in reader_loop () #19 0x0000000000411e8d in main () It would appear that because I use nss_ldap the pthread library is getting involved for a signal handler. Not sure if this is the issue, but the end result is that resize causes core dump of bash. Cheers, Sean From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 2 12:15:19 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B253D16A4CE; Wed, 2 Jun 2004 12:15:19 -0700 (PDT) Received: from mail.mcneil.com (rrcs-west-24-199-45-54.biz.rr.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 86FAD43D46; Wed, 2 Jun 2004 12:15:19 -0700 (PDT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id E0CCDFD03A; Wed, 2 Jun 2004 12:15:21 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 64835-06; Wed, 2 Jun 2004 12:15:21 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 4B642FD01A; Wed, 2 Jun 2004 12:15:21 -0700 (PDT) From: Sean McNeil To: freebsd-amd64@freebsd.org, freebsd-gnome@freebsd.org Content-Type: text/plain Message-Id: <1086203721.60191.2.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 02 Jun 2004 12:15:21 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com Subject: backtrace of nautilus core dump on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 19:15:19 -0000 Here is a core dump of nautilus. The only interesting difference in my environment is that I use ldap/nss_ldap. Other than that, everything should be just like everyone else: (gdb) bt #0 0x00000002049632ec in pthread_testcancel () from /usr/lib/libpthread.so.1 #1 0x0000000204955d33 in sigaction () from /usr/lib/libpthread.so.1 #2 0x0000000204956151 in sigaction () from /usr/lib/libpthread.so.1 #3 0x0000000204950a93 in pthread_kill () from /usr/lib/libpthread.so.1 #4 0x0000000204950473 in raise () from /usr/lib/libpthread.so.1 #5 0x0000000204d11441 in abort () from /lib/libc.so.5 #6 0x0000000204cbd73e in ldexp () from /lib/libc.so.5 #7 0x0000000204cbd778 in ldexp () from /lib/libc.so.5 #8 0x0000000204cbe119 in ldexp () from /lib/libc.so.5 #9 0x0000000204cbe2ac in malloc () from /lib/libc.so.5 #10 0x0000000204957fd2 in pthread_mutex_init () from /usr/lib/libpthread.so.1 #11 0x000000020495858a in pthread_mutex_destroy () from /usr/lib/libpthread.so.1 #12 0x0000000204959bb1 in _pthread_mutex_lock () from /usr/lib/libpthread.so.1 #13 0x0000000204d12f7d in flockfile () from /lib/libc.so.5 #14 0x0000000204d0880e in vfprintf () from /lib/libc.so.5 #15 0x0000000204cf7c4c in fprintf () from /lib/libc.so.5 #16 0x000000020143c053 in libgnomeui_module_info_get () from /usr/X11R6/lib/libgnomeui-2.so.600 #17 0x0000000204954f2e in sigaction () from /usr/lib/libpthread.so.1 #18 0x0000000204954de9 in sigaction () from /usr/lib/libpthread.so.1 #19 0x00000002049557be in sigaction () from /usr/lib/libpthread.so.1 #20 0x0000000204955a00 in sigaction () from /usr/lib/libpthread.so.1 ---Type to continue, or q to quit--- #21 0x000000020495bc75 in pthread_mutexattr_init () from /usr/lib/libpthread.so.1 #22 0x0000000204963a3f in pthread_testcancel () from /usr/lib/libpthread.so.1 #23 0x0000000204950a9e in pthread_kill () from /usr/lib/libpthread.so.1 #24 0x0000000204950473 in raise () from /usr/lib/libpthread.so.1 #25 0x0000000204d113ee in abort () from /lib/libc.so.5 #26 0x0000000204cbd73e in ldexp () from /lib/libc.so.5 #27 0x0000000204cbd778 in ldexp () from /lib/libc.so.5 #28 0x0000000204cbe119 in ldexp () from /lib/libc.so.5 #29 0x0000000204cbe2ac in malloc () from /lib/libc.so.5 #30 0x0000000204699c3d in _XEnq () from /usr/X11R6/lib/libX11.so.6 #31 0x0000000204699447 in _XReply () from /usr/X11R6/lib/libX11.so.6 #32 0x0000000204694c8f in XSync () from /usr/X11R6/lib/libX11.so.6 #33 0x0000000202476e3d in gdk_flush () from /usr/X11R6/lib/libgdk-x11-2.0.so.400 #34 0x000000020143c079 in libgnomeui_module_info_get () from /usr/X11R6/lib/libgnomeui-2.so.600 #35 0x0000000204954f2e in sigaction () from /usr/lib/libpthread.so.1 #36 0x0000000204954de9 in sigaction () from /usr/lib/libpthread.so.1 #37 0x00000002049557be in sigaction () from /usr/lib/libpthread.so.1 #38 0x0000000204955a00 in sigaction () from /usr/lib/libpthread.so.1 #39 0x000000020495bc75 in pthread_mutexattr_init () from /usr/lib/libpthread.so.1 ---Type to continue, or q to quit--- #40 0x0000000204963a3f in pthread_testcancel () from /usr/lib/libpthread.so.1 #41 0x0000000204950a9e in pthread_kill () from /usr/lib/libpthread.so.1 #42 0x0000000204950473 in raise () from /usr/lib/libpthread.so.1 #43 0x0000000204d113ee in abort () from /lib/libc.so.5 #44 0x0000000204cbd73e in ldexp () from /lib/libc.so.5 #45 0x0000000204cbd778 in ldexp () from /lib/libc.so.5 #46 0x0000000204cbe095 in ldexp () from /lib/libc.so.5 #47 0x0000000204cbe1de in ldexp () from /lib/libc.so.5 #48 0x0000000204cbe2c9 in free () from /lib/libc.so.5 #49 0x00000002040b5e0f in g_free () from /usr/local/lib/libglib-2.0.so.400 #50 0x0000000203ae5c95 in ORBit_free_T () from /usr/local/lib/libORBit-2.so.0 #51 0x0000000203ae5b0e in ORBit_freekids_via_TypeCode_T () from /usr/local/lib/libORBit-2.so.0 #52 0x0000000203ae5a41 in ORBit_freekids_via_TypeCode_T () from /usr/local/lib/libORBit-2.so.0 #53 0x0000000203ae5caa in ORBit_free_T () from /usr/local/lib/libORBit-2.so.0 #54 0x0000000203ae5b2d in ORBit_freekids_via_TypeCode_T () from /usr/local/lib/libORBit-2.so.0 #55 0x0000000203ae5caa in ORBit_free_T () from /usr/local/lib/libORBit-2.so.0 #56 0x0000000203ae5d0c in ORBit_free () from /usr/local/lib/libORBit-2.so.0 #57 0x0000000203ae5c29 in CORBA_free () from /usr/local/lib/libORBit-2.so.0 #58 0x000000020386cd79 in gnome_vfs_volume_monitor_client_get_type () from /usr/X11R6/lib/libgnomevfs-2.so.600 ---Type to continue, or q to quit--- #59 0x000000020386ce91 in gnome_vfs_volume_monitor_client_get_type () from /usr/X11R6/lib/libgnomevfs-2.so.600 #60 0x0000000203c41987 in g_type_create_instance () from /usr/local/lib/libgobject-2.0.so.400 #61 0x0000000203c2e731 in g_object_constructor () from /usr/local/lib/libgobject-2.0.so.400 #62 0x0000000203c2e0a6 in g_object_newv () from /usr/local/lib/libgobject-2.0.so.400 #63 0x0000000203c2e40d in g_object_new_valist () from /usr/local/lib/libgobject-2.0.so.400 #64 0x0000000203c2dcb4 in g_object_new () from /usr/local/lib/libgobject-2.0.so.400 #65 0x000000020386ed5c in gnome_vfs_volume_monitor_unref () from /usr/X11R6/lib/libgnomevfs-2.so.600 #66 0x000000020386edd2 in gnome_vfs_get_volume_monitor () from /usr/X11R6/lib/libgnomevfs-2.so.600 #67 0x0000000000429cc2 in nautilus_application_get_spatial_window_list () #68 0x0000000203c41987 in g_type_create_instance () from /usr/local/lib/libgobject-2.0.so.400 #69 0x0000000203c2e731 in g_object_constructor () from /usr/local/lib/libgobject-2.0.so.400 #70 0x000000020359bdb9 in bonobo_object_constructor () from /usr/local/lib/libbonobo-2.so.0 ---Type to continue, or q to quit--- #71 0x0000000203c2e0a6 in g_object_newv () from /usr/local/lib/libgobject-2.0.so.400 #72 0x0000000203c2e40d in g_object_new_valist () from /usr/local/lib/libgobject-2.0.so.400 #73 0x0000000203c2dcb4 in g_object_new () from /usr/local/lib/libgobject-2.0.so.400 #74 0x0000000000429d91 in nautilus_application_new () #75 0x0000000000434c3d in main () (gdb) From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 2 12:21:21 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C28616A4CE; Wed, 2 Jun 2004 12:21:21 -0700 (PDT) Received: from creme-brulee.marcuscom.com (rrcs-midsouth-24-172-16-118.biz.rr.com [24.172.16.118]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF39E43D45; Wed, 2 Jun 2004 12:21:20 -0700 (PDT) (envelope-from marcus@marcuscom.com) Received: from [10.2.1.70] (vpn-client-70.marcuscom.com [10.2.1.70]) i52JKxG1034621; Wed, 2 Jun 2004 15:20:59 -0400 (EDT) (envelope-from marcus@marcuscom.com) From: Joe Marcus Clarke To: Sean McNeil In-Reply-To: <1086203721.60191.2.camel@server.mcneil.com> References: <1086203721.60191.2.camel@server.mcneil.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-0/oaX1X+tEUJme/HKk8L" Organization: MarcusCom, Inc. Message-Id: <1086204118.514.11.camel@gyros> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 02 Jun 2004 15:21:58 -0400 X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on creme-brulee.marcuscom.com cc: freebsd-gnome@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: backtrace of nautilus core dump on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 19:21:21 -0000 --=-0/oaX1X+tEUJme/HKk8L Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Wed, 2004-06-02 at 15:15, Sean McNeil wrote: > Here is a core dump of nautilus. The only interesting difference in my > environment is that I use ldap/nss_ldap. Other than that, everything > should be just like everyone else: There are no symbols in this backtrace. Please recompile everything with debugging flags. Also, try disabling nss_ldap, and see if it makes a difference. Joe >=20 > (gdb) bt > #0 0x00000002049632ec in pthread_testcancel () from > /usr/lib/libpthread.so.1 > #1 0x0000000204955d33 in sigaction () from /usr/lib/libpthread.so.1 > #2 0x0000000204956151 in sigaction () from /usr/lib/libpthread.so.1 > #3 0x0000000204950a93 in pthread_kill () from /usr/lib/libpthread.so.1 > #4 0x0000000204950473 in raise () from /usr/lib/libpthread.so.1 > #5 0x0000000204d11441 in abort () from /lib/libc.so.5 > #6 0x0000000204cbd73e in ldexp () from /lib/libc.so.5 > #7 0x0000000204cbd778 in ldexp () from /lib/libc.so.5 > #8 0x0000000204cbe119 in ldexp () from /lib/libc.so.5 > #9 0x0000000204cbe2ac in malloc () from /lib/libc.so.5 > #10 0x0000000204957fd2 in pthread_mutex_init () from > /usr/lib/libpthread.so.1 > #11 0x000000020495858a in pthread_mutex_destroy () > from /usr/lib/libpthread.so.1 > #12 0x0000000204959bb1 in _pthread_mutex_lock () from > /usr/lib/libpthread.so.1 > #13 0x0000000204d12f7d in flockfile () from /lib/libc.so.5 > #14 0x0000000204d0880e in vfprintf () from /lib/libc.so.5 > #15 0x0000000204cf7c4c in fprintf () from /lib/libc.so.5 > #16 0x000000020143c053 in libgnomeui_module_info_get () > from /usr/X11R6/lib/libgnomeui-2.so.600 > #17 0x0000000204954f2e in sigaction () from /usr/lib/libpthread.so.1 > #18 0x0000000204954de9 in sigaction () from /usr/lib/libpthread.so.1 > #19 0x00000002049557be in sigaction () from /usr/lib/libpthread.so.1 > #20 0x0000000204955a00 in sigaction () from /usr/lib/libpthread.so.1 > ---Type to continue, or q to quit--- > #21 0x000000020495bc75 in pthread_mutexattr_init () > from /usr/lib/libpthread.so.1 > #22 0x0000000204963a3f in pthread_testcancel () from > /usr/lib/libpthread.so.1 > #23 0x0000000204950a9e in pthread_kill () from /usr/lib/libpthread.so.1 > #24 0x0000000204950473 in raise () from /usr/lib/libpthread.so.1 > #25 0x0000000204d113ee in abort () from /lib/libc.so.5 > #26 0x0000000204cbd73e in ldexp () from /lib/libc.so.5 > #27 0x0000000204cbd778 in ldexp () from /lib/libc.so.5 > #28 0x0000000204cbe119 in ldexp () from /lib/libc.so.5 > #29 0x0000000204cbe2ac in malloc () from /lib/libc.so.5 > #30 0x0000000204699c3d in _XEnq () from /usr/X11R6/lib/libX11.so.6 > #31 0x0000000204699447 in _XReply () from /usr/X11R6/lib/libX11.so.6 > #32 0x0000000204694c8f in XSync () from /usr/X11R6/lib/libX11.so.6 > #33 0x0000000202476e3d in gdk_flush () > from /usr/X11R6/lib/libgdk-x11-2.0.so.400 > #34 0x000000020143c079 in libgnomeui_module_info_get () > from /usr/X11R6/lib/libgnomeui-2.so.600 > #35 0x0000000204954f2e in sigaction () from /usr/lib/libpthread.so.1 > #36 0x0000000204954de9 in sigaction () from /usr/lib/libpthread.so.1 > #37 0x00000002049557be in sigaction () from /usr/lib/libpthread.so.1 > #38 0x0000000204955a00 in sigaction () from /usr/lib/libpthread.so.1 > #39 0x000000020495bc75 in pthread_mutexattr_init () > from /usr/lib/libpthread.so.1 > ---Type to continue, or q to quit--- > #40 0x0000000204963a3f in pthread_testcancel () from > /usr/lib/libpthread.so.1 > #41 0x0000000204950a9e in pthread_kill () from /usr/lib/libpthread.so.1 > #42 0x0000000204950473 in raise () from /usr/lib/libpthread.so.1 > #43 0x0000000204d113ee in abort () from /lib/libc.so.5 > #44 0x0000000204cbd73e in ldexp () from /lib/libc.so.5 > #45 0x0000000204cbd778 in ldexp () from /lib/libc.so.5 > #46 0x0000000204cbe095 in ldexp () from /lib/libc.so.5 > #47 0x0000000204cbe1de in ldexp () from /lib/libc.so.5 > #48 0x0000000204cbe2c9 in free () from /lib/libc.so.5 > #49 0x00000002040b5e0f in g_free () from > /usr/local/lib/libglib-2.0.so.400 > #50 0x0000000203ae5c95 in ORBit_free_T () from > /usr/local/lib/libORBit-2.so.0 > #51 0x0000000203ae5b0e in ORBit_freekids_via_TypeCode_T () > from /usr/local/lib/libORBit-2.so.0 > #52 0x0000000203ae5a41 in ORBit_freekids_via_TypeCode_T () > from /usr/local/lib/libORBit-2.so.0 > #53 0x0000000203ae5caa in ORBit_free_T () from > /usr/local/lib/libORBit-2.so.0 > #54 0x0000000203ae5b2d in ORBit_freekids_via_TypeCode_T () > from /usr/local/lib/libORBit-2.so.0 > #55 0x0000000203ae5caa in ORBit_free_T () from > /usr/local/lib/libORBit-2.so.0 > #56 0x0000000203ae5d0c in ORBit_free () from > /usr/local/lib/libORBit-2.so.0 > #57 0x0000000203ae5c29 in CORBA_free () from > /usr/local/lib/libORBit-2.so.0 > #58 0x000000020386cd79 in gnome_vfs_volume_monitor_client_get_type () > from /usr/X11R6/lib/libgnomevfs-2.so.600 > ---Type to continue, or q to quit--- > #59 0x000000020386ce91 in gnome_vfs_volume_monitor_client_get_type () > from /usr/X11R6/lib/libgnomevfs-2.so.600 > #60 0x0000000203c41987 in g_type_create_instance () > from /usr/local/lib/libgobject-2.0.so.400 > #61 0x0000000203c2e731 in g_object_constructor () > from /usr/local/lib/libgobject-2.0.so.400 > #62 0x0000000203c2e0a6 in g_object_newv () > from /usr/local/lib/libgobject-2.0.so.400 > #63 0x0000000203c2e40d in g_object_new_valist () > from /usr/local/lib/libgobject-2.0.so.400 > #64 0x0000000203c2dcb4 in g_object_new () > from /usr/local/lib/libgobject-2.0.so.400 > #65 0x000000020386ed5c in gnome_vfs_volume_monitor_unref () > from /usr/X11R6/lib/libgnomevfs-2.so.600 > #66 0x000000020386edd2 in gnome_vfs_get_volume_monitor () > from /usr/X11R6/lib/libgnomevfs-2.so.600 > #67 0x0000000000429cc2 in nautilus_application_get_spatial_window_list > () > #68 0x0000000203c41987 in g_type_create_instance () > from /usr/local/lib/libgobject-2.0.so.400 > #69 0x0000000203c2e731 in g_object_constructor () > from /usr/local/lib/libgobject-2.0.so.400 > #70 0x000000020359bdb9 in bonobo_object_constructor () > from /usr/local/lib/libbonobo-2.so.0 > ---Type to continue, or q to quit--- > #71 0x0000000203c2e0a6 in g_object_newv () > from /usr/local/lib/libgobject-2.0.so.400 > #72 0x0000000203c2e40d in g_object_new_valist () > from /usr/local/lib/libgobject-2.0.so.400 > #73 0x0000000203c2dcb4 in g_object_new () > from /usr/local/lib/libgobject-2.0.so.400 > #74 0x0000000000429d91 in nautilus_application_new () > #75 0x0000000000434c3d in main () > (gdb) >=20 >=20 > _______________________________________________ > freebsd-gnome@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-gnome > To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@freebsd.org" --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-0/oaX1X+tEUJme/HKk8L Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBAvijWb2iPiv4Uz4cRAljSAKCDRGlAUoAvGW1jAXHNfJO0dE8l+ACfU5DL ETIZsLXoEFquuoz0b6sw2dw= =9fa0 -----END PGP SIGNATURE----- --=-0/oaX1X+tEUJme/HKk8L-- From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 2 12:24:22 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CDA6B16A4D0; Wed, 2 Jun 2004 12:24:22 -0700 (PDT) Received: from lakermmtao07.cox.net (lakermmtao07.cox.net [68.230.240.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 43A0143D54; Wed, 2 Jun 2004 12:24:22 -0700 (PDT) (envelope-from mezz7@cox.net) Received: from mezz ([68.103.32.140]) by lakermmtao07.cox.net (InterMail vM.6.01.03.02 201-2131-111-104-20040324) with ESMTP id <20040602192421.TYCK15361.lakermmtao07.cox.net@mezz>; Wed, 2 Jun 2004 15:24:21 -0400 Date: Wed, 02 Jun 2004 14:24:59 -0500 To: "Sean McNeil" References: <1086203721.60191.2.camel@server.mcneil.com> From: "Jeremy Messenger" Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: In-Reply-To: <1086203721.60191.2.camel@server.mcneil.com> User-Agent: Opera M2/7.50 (Linux, build 673) cc: freebsd-gnome@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: backtrace of nautilus core dump on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 19:24:23 -0000 On Wed, 02 Jun 2004 12:15:21 -0700, Sean McNeil wrote: > Here is a core dump of nautilus. The only interesting difference in my > environment is that I use ldap/nss_ldap. Other than that, everything > should be just like everyone else: I noticed your other emails with backtraces, but they all will not help that much so here too. Because, you need to recompile everything with the debug to get the better backtraces. Add those in the /etc/make.conf: CFLAGS= -O -pipe -g STRIP= Then, rebuild all your apps. Do not forget to disable above when you are doing buildworld. See my email in freebsd-gnome archive called 'Few apps crashed with librsvg2-2.7.1..' to see example of the backtraces that look different, because I compile everything with the debug. Cheers, Mezz > =(gdb) bt > #0 0x00000002049632ec in pthread_testcancel () from > /usr/lib/libpthread.so.1 > #1 0x0000000204955d33 in sigaction () from /usr/lib/libpthread.so.1 > #2 0x0000000204956151 in sigaction () from /usr/lib/libpthread.so.1 > #3 0x0000000204950a93 in pthread_kill () from /usr/lib/libpthread.so.1 > #4 0x0000000204950473 in raise () from /usr/lib/libpthread.so.1 > #5 0x0000000204d11441 in abort () from /lib/libc.so.5 > #6 0x0000000204cbd73e in ldexp () from /lib/libc.so.5 > #7 0x0000000204cbd778 in ldexp () from /lib/libc.so.5 > #8 0x0000000204cbe119 in ldexp () from /lib/libc.so.5 > #9 0x0000000204cbe2ac in malloc () from /lib/libc.so.5 > #10 0x0000000204957fd2 in pthread_mutex_init () from > /usr/lib/libpthread.so.1 > #11 0x000000020495858a in pthread_mutex_destroy () > from /usr/lib/libpthread.so.1 > #12 0x0000000204959bb1 in _pthread_mutex_lock () from > /usr/lib/libpthread.so.1 > #13 0x0000000204d12f7d in flockfile () from /lib/libc.so.5 > #14 0x0000000204d0880e in vfprintf () from /lib/libc.so.5 > #15 0x0000000204cf7c4c in fprintf () from /lib/libc.so.5 > #16 0x000000020143c053 in libgnomeui_module_info_get () > from /usr/X11R6/lib/libgnomeui-2.so.600 > #17 0x0000000204954f2e in sigaction () from /usr/lib/libpthread.so.1 > #18 0x0000000204954de9 in sigaction () from /usr/lib/libpthread.so.1 > #19 0x00000002049557be in sigaction () from /usr/lib/libpthread.so.1 > #20 0x0000000204955a00 in sigaction () from /usr/lib/libpthread.so.1 > ---Type to continue, or q to quit--- > #21 0x000000020495bc75 in pthread_mutexattr_init () > from /usr/lib/libpthread.so.1 > #22 0x0000000204963a3f in pthread_testcancel () from > /usr/lib/libpthread.so.1 > #23 0x0000000204950a9e in pthread_kill () from /usr/lib/libpthread.so.1 > #24 0x0000000204950473 in raise () from /usr/lib/libpthread.so.1 > #25 0x0000000204d113ee in abort () from /lib/libc.so.5 > #26 0x0000000204cbd73e in ldexp () from /lib/libc.so.5 > #27 0x0000000204cbd778 in ldexp () from /lib/libc.so.5 > #28 0x0000000204cbe119 in ldexp () from /lib/libc.so.5 > #29 0x0000000204cbe2ac in malloc () from /lib/libc.so.5 > #30 0x0000000204699c3d in _XEnq () from /usr/X11R6/lib/libX11.so.6 > #31 0x0000000204699447 in _XReply () from /usr/X11R6/lib/libX11.so.6 > #32 0x0000000204694c8f in XSync () from /usr/X11R6/lib/libX11.so.6 > #33 0x0000000202476e3d in gdk_flush () > from /usr/X11R6/lib/libgdk-x11-2.0.so.400 > #34 0x000000020143c079 in libgnomeui_module_info_get () > from /usr/X11R6/lib/libgnomeui-2.so.600 > #35 0x0000000204954f2e in sigaction () from /usr/lib/libpthread.so.1 > #36 0x0000000204954de9 in sigaction () from /usr/lib/libpthread.so.1 > #37 0x00000002049557be in sigaction () from /usr/lib/libpthread.so.1 > #38 0x0000000204955a00 in sigaction () from /usr/lib/libpthread.so.1 > #39 0x000000020495bc75 in pthread_mutexattr_init () > from /usr/lib/libpthread.so.1 > ---Type to continue, or q to quit--- > #40 0x0000000204963a3f in pthread_testcancel () from > /usr/lib/libpthread.so.1 > #41 0x0000000204950a9e in pthread_kill () from /usr/lib/libpthread.so.1 > #42 0x0000000204950473 in raise () from /usr/lib/libpthread.so.1 > #43 0x0000000204d113ee in abort () from /lib/libc.so.5 > #44 0x0000000204cbd73e in ldexp () from /lib/libc.so.5 > #45 0x0000000204cbd778 in ldexp () from /lib/libc.so.5 > #46 0x0000000204cbe095 in ldexp () from /lib/libc.so.5 > #47 0x0000000204cbe1de in ldexp () from /lib/libc.so.5 > #48 0x0000000204cbe2c9 in free () from /lib/libc.so.5 > #49 0x00000002040b5e0f in g_free () from > /usr/local/lib/libglib-2.0.so.400 > #50 0x0000000203ae5c95 in ORBit_free_T () from > /usr/local/lib/libORBit-2.so.0 > #51 0x0000000203ae5b0e in ORBit_freekids_via_TypeCode_T () > from /usr/local/lib/libORBit-2.so.0 > #52 0x0000000203ae5a41 in ORBit_freekids_via_TypeCode_T () > from /usr/local/lib/libORBit-2.so.0 > #53 0x0000000203ae5caa in ORBit_free_T () from > /usr/local/lib/libORBit-2.so.0 > #54 0x0000000203ae5b2d in ORBit_freekids_via_TypeCode_T () > from /usr/local/lib/libORBit-2.so.0 > #55 0x0000000203ae5caa in ORBit_free_T () from > /usr/local/lib/libORBit-2.so.0 > #56 0x0000000203ae5d0c in ORBit_free () from > /usr/local/lib/libORBit-2.so.0 > #57 0x0000000203ae5c29 in CORBA_free () from > /usr/local/lib/libORBit-2.so.0 > #58 0x000000020386cd79 in gnome_vfs_volume_monitor_client_get_type () > from /usr/X11R6/lib/libgnomevfs-2.so.600 > ---Type to continue, or q to quit--- > #59 0x000000020386ce91 in gnome_vfs_volume_monitor_client_get_type () > from /usr/X11R6/lib/libgnomevfs-2.so.600 > #60 0x0000000203c41987 in g_type_create_instance () > from /usr/local/lib/libgobject-2.0.so.400 > #61 0x0000000203c2e731 in g_object_constructor () > from /usr/local/lib/libgobject-2.0.so.400 > #62 0x0000000203c2e0a6 in g_object_newv () > from /usr/local/lib/libgobject-2.0.so.400 > #63 0x0000000203c2e40d in g_object_new_valist () > from /usr/local/lib/libgobject-2.0.so.400 > #64 0x0000000203c2dcb4 in g_object_new () > from /usr/local/lib/libgobject-2.0.so.400 > #65 0x000000020386ed5c in gnome_vfs_volume_monitor_unref () > from /usr/X11R6/lib/libgnomevfs-2.so.600 > #66 0x000000020386edd2 in gnome_vfs_get_volume_monitor () > from /usr/X11R6/lib/libgnomevfs-2.so.600 > #67 0x0000000000429cc2 in nautilus_application_get_spatial_window_list > () > #68 0x0000000203c41987 in g_type_create_instance () > from /usr/local/lib/libgobject-2.0.so.400 > #69 0x0000000203c2e731 in g_object_constructor () > from /usr/local/lib/libgobject-2.0.so.400 > #70 0x000000020359bdb9 in bonobo_object_constructor () > from /usr/local/lib/libbonobo-2.so.0 > ---Type to continue, or q to quit--- > #71 0x0000000203c2e0a6 in g_object_newv () > from /usr/local/lib/libgobject-2.0.so.400 > #72 0x0000000203c2e40d in g_object_new_valist () > from /usr/local/lib/libgobject-2.0.so.400 > #73 0x0000000203c2dcb4 in g_object_new () > from /usr/local/lib/libgobject-2.0.so.400 > #74 0x0000000000429d91 in nautilus_application_new () > #75 0x0000000000434c3d in main () > (gdb) -- mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 2 12:31:45 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 27D0816A4CE; Wed, 2 Jun 2004 12:31:45 -0700 (PDT) Received: from mail.mcneil.com (rrcs-west-24-199-45-54.biz.rr.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F22043D2F; Wed, 2 Jun 2004 12:31:45 -0700 (PDT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 69428FD03A; Wed, 2 Jun 2004 12:31:47 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 64856-07; Wed, 2 Jun 2004 12:31:47 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id F21B8FD020; Wed, 2 Jun 2004 12:31:46 -0700 (PDT) From: Sean McNeil To: Joe Marcus Clarke In-Reply-To: <1086204118.514.11.camel@gyros> References: <1086203721.60191.2.camel@server.mcneil.com> <1086204118.514.11.camel@gyros> Content-Type: text/plain Message-Id: <1086204706.60191.8.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 02 Jun 2004 12:31:46 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com cc: freebsd-gnome@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: backtrace of nautilus core dump on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 19:31:45 -0000 On Wed, 2004-06-02 at 12:21, Joe Marcus Clarke wrote: > On Wed, 2004-06-02 at 15:15, Sean McNeil wrote: > > Here is a core dump of nautilus. The only interesting difference in my > > environment is that I use ldap/nss_ldap. Other than that, everything > > should be just like everyone else: > > There are no symbols in this backtrace. Please recompile everything > with debugging flags. Also, try disabling nss_ldap, and see if it makes > a difference. > > Joe Tried with nss_ldap disabled. Same core. Mezz just sent me a comment to do: CFLAGS= -O -pipe -g STRIP= I usually do DEBUG_FLAGS=-g WITH_DEBUG=yes Are they both as good, should I do as Mezz suggests? I just started a portupgrade -fR on nautilus. Please let me know if I should stop it and do the build with the CFLAGS/STRIP assignment. Cheers, Sean From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 2 12:56:17 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4FC8916A4CE; Wed, 2 Jun 2004 12:56:17 -0700 (PDT) Received: from creme-brulee.marcuscom.com (rrcs-midsouth-24-172-16-118.biz.rr.com [24.172.16.118]) by mx1.FreeBSD.org (Postfix) with ESMTP id D136C43D31; Wed, 2 Jun 2004 12:56:16 -0700 (PDT) (envelope-from marcus@marcuscom.com) Received: from [10.2.1.70] (vpn-client-70.marcuscom.com [10.2.1.70]) i52JttQp035023; Wed, 2 Jun 2004 15:55:55 -0400 (EDT) (envelope-from marcus@marcuscom.com) From: Joe Marcus Clarke To: Sean McNeil In-Reply-To: <1086204706.60191.8.camel@server.mcneil.com> References: <1086203721.60191.2.camel@server.mcneil.com> <1086204118.514.11.camel@gyros> <1086204706.60191.8.camel@server.mcneil.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-RlKlI9/Hw3KiGPLtsmWF" Organization: MarcusCom, Inc. Message-Id: <1086206214.514.15.camel@gyros> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 02 Jun 2004 15:56:54 -0400 X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on creme-brulee.marcuscom.com cc: freebsd-gnome@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: backtrace of nautilus core dump on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 19:56:17 -0000 --=-RlKlI9/Hw3KiGPLtsmWF Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Wed, 2004-06-02 at 15:31, Sean McNeil wrote: > On Wed, 2004-06-02 at 12:21, Joe Marcus Clarke wrote: > > On Wed, 2004-06-02 at 15:15, Sean McNeil wrote: > > > Here is a core dump of nautilus. The only interesting difference in = my > > > environment is that I use ldap/nss_ldap. Other than that, everything > > > should be just like everyone else: > >=20 > > There are no symbols in this backtrace. Please recompile everything > > with debugging flags. Also, try disabling nss_ldap, and see if it make= s > > a difference. > >=20 > > Joe >=20 > Tried with nss_ldap disabled. Same core. Mezz just sent me a comment > to do: >=20 > CFLAGS=3D -O -pipe -g > STRIP=3D >=20 > I usually do >=20 > DEBUG_FLAGS=3D-g > WITH_DEBUG=3Dyes >=20 > Are they both as good, should I do as Mezz suggests? I just started a > portupgrade -fR on nautilus. Please let me know if I should stop it and > do the build with the CFLAGS/STRIP assignment. You should do what Mezz suggested. Joe >=20 > Cheers, > Sean >=20 >=20 --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-RlKlI9/Hw3KiGPLtsmWF Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBAvjEGb2iPiv4Uz4cRAlHJAKChR5ak5kFFJyZNrxu0zpsmGDToCQCgk6s7 SW4TU710LfWGpvF54tFTJwU= =F8f5 -----END PGP SIGNATURE----- --=-RlKlI9/Hw3KiGPLtsmWF-- From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 2 14:38:36 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E94F16A4CE; Wed, 2 Jun 2004 14:38:36 -0700 (PDT) Received: from mail.mcneil.com (rrcs-west-24-199-45-54.biz.rr.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2EBDB43D46; Wed, 2 Jun 2004 14:38:34 -0700 (PDT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 53292FD020; Wed, 2 Jun 2004 14:38:36 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 75282-02; Wed, 2 Jun 2004 14:38:35 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 9169EFD03A; Wed, 2 Jun 2004 14:38:35 -0700 (PDT) From: Sean McNeil To: Joe Marcus Clarke In-Reply-To: <1086204118.514.11.camel@gyros> References: <1086203721.60191.2.camel@server.mcneil.com> <1086204118.514.11.camel@gyros> Content-Type: text/plain Message-Id: <1086212315.66953.1.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 02 Jun 2004 14:38:35 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com cc: freebsd-gnome@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: backtrace of nautilus core dump on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 21:38:36 -0000 On Wed, 2004-06-02 at 12:21, Joe Marcus Clarke wrote: > On Wed, 2004-06-02 at 15:15, Sean McNeil wrote: > > Here is a core dump of nautilus. The only interesting difference in my > > environment is that I use ldap/nss_ldap. Other than that, everything > > should be just like everyone else: > > There are no symbols in this backtrace. Please recompile everything > with debugging flags. Also, try disabling nss_ldap, and see if it makes > a difference. > > Joe Here is a backtrace with the application built including symbols (portupgrade -fR nautilus2-2.6.1): (gdb) bt #0 0x00000002049662ec in pthread_testcancel () from /usr/lib/libpthread.so.1 #1 0x0000000204958d33 in sigaction () from /usr/lib/libpthread.so.1 #2 0x0000000204959151 in sigaction () from /usr/lib/libpthread.so.1 #3 0x0000000204953a93 in pthread_kill () from /usr/lib/libpthread.so.1 #4 0x0000000204953473 in raise () from /usr/lib/libpthread.so.1 #5 0x0000000204d14441 in abort () from /lib/libc.so.5 #6 0x0000000204cc073e in ldexp () from /lib/libc.so.5 #7 0x0000000204cc0778 in ldexp () from /lib/libc.so.5 #8 0x0000000204cc1119 in ldexp () from /lib/libc.so.5 #9 0x0000000204cc12ac in malloc () from /lib/libc.so.5 #10 0x000000020495afd2 in pthread_mutex_init () from /usr/lib/libpthread.so.1 #11 0x000000020495b58a in pthread_mutex_destroy () from /usr/lib/libpthread.so.1 #12 0x000000020495cbb1 in _pthread_mutex_lock () from /usr/lib/libpthread.so.1 #13 0x0000000204d15f7d in flockfile () from /lib/libc.so.5 #14 0x0000000204d0b80e in vfprintf () from /lib/libc.so.5 #15 0x0000000204cfac4c in fprintf () from /lib/libc.so.5 #16 0x000000020143c143 in libgnomeui_segv_handle (signum=6) at gnome-ui-init.c:708 #17 0x0000000204957f2e in sigaction () from /usr/lib/libpthread.so.1 #18 0x0000000204957de9 in sigaction () from /usr/lib/libpthread.so.1 #19 0x00000002049587be in sigaction () from /usr/lib/libpthread.so.1 #20 0x0000000204958a00 in sigaction () from /usr/lib/libpthread.so.1 ---Type to continue, or q to quit--- #21 0x000000020495ec75 in pthread_mutexattr_init () from /usr/lib/libpthread.so.1 #22 0x0000000204966a3f in pthread_testcancel () from /usr/lib/libpthread.so.1 #23 0x0000000204953a9e in pthread_kill () from /usr/lib/libpthread.so.1 #24 0x0000000204953473 in raise () from /usr/lib/libpthread.so.1 #25 0x0000000204d143ee in abort () from /lib/libc.so.5 #26 0x0000000204cc073e in ldexp () from /lib/libc.so.5 #27 0x0000000204cc0778 in ldexp () from /lib/libc.so.5 #28 0x0000000204cc1119 in ldexp () from /lib/libc.so.5 #29 0x0000000204cc12ac in malloc () from /lib/libc.so.5 #30 0x000000020469cd1d in _XEnq (dpy=0x5e7000, event=0x7fffffffd6f0) at XlibInt.c:2249 #31 0x000000020469c527 in _XReply (dpy=0x5e7000, rep=0x7fffffffd6f0, extra=0, discard=1) at XlibInt.c:1798 #32 0x0000000204697d6f in XSync (dpy=0x5e7000, discard=0) at Sync.c:45 #33 0x0000000202476f1d in gdk_flush () at gdkevents-x11.c:2333 #34 0x000000020143c169 in libgnomeui_segv_handle (signum=6) at gnome-ui-init.c:716 #35 0x0000000204957f2e in sigaction () from /usr/lib/libpthread.so.1 #36 0x0000000204957de9 in sigaction () from /usr/lib/libpthread.so.1 #37 0x00000002049587be in sigaction () from /usr/lib/libpthread.so.1 #38 0x0000000204958a00 in sigaction () from /usr/lib/libpthread.so.1 #39 0x000000020495ec75 in pthread_mutexattr_init () ---Type to continue, or q to quit--- from /usr/lib/libpthread.so.1 #40 0x0000000204966a3f in pthread_testcancel () from /usr/lib/libpthread.so.1 #41 0x0000000204953a9e in pthread_kill () from /usr/lib/libpthread.so.1 #42 0x0000000204953473 in raise () from /usr/lib/libpthread.so.1 #43 0x0000000204d143ee in abort () from /lib/libc.so.5 #44 0x0000000204cc073e in ldexp () from /lib/libc.so.5 #45 0x0000000204cc0778 in ldexp () from /lib/libc.so.5 #46 0x0000000204cc1095 in ldexp () from /lib/libc.so.5 #47 0x0000000204cc11de in ldexp () from /lib/libc.so.5 #48 0x0000000204cc12c9 in free () from /lib/libc.so.5 #49 0x00000002040b8eef in g_free (mem=0x0) at gmem.c:186 #50 0x0000000203ae8d85 in ORBit_free_T (mem=0x0) at allocators.c:187 #51 0x0000000203ae8bfe in ORBit_freekids_via_TypeCode_T (mem=0x8dd080, tc=0x5b6550) at allocators.c:88 #52 0x0000000203ae8b31 in ORBit_freekids_via_TypeCode_T (mem=0x8dd080, tc=0x203983c60) at allocators.c:65 #53 0x0000000203ae8d9a in ORBit_free_T (mem=0x0) at allocators.c:197 #54 0x0000000203ae8c1d in ORBit_freekids_via_TypeCode_T (mem=0x87f250, tc=0x87f250) at allocators.c:96 #55 0x0000000203ae8d9a in ORBit_free_T (mem=0x0) at allocators.c:197 #56 0x0000000203ae8dfc in ORBit_free (mem=0x87f250) at allocators.c:213 #57 0x0000000203ae8d19 in CORBA_free (mem=0x0) at allocators.c:138 #58 0x000000020386fe69 in read_drives_from_daemon ( ---Type to continue, or q to quit--- volume_monitor_client=0x8dc4e0) at gnome-vfs-volume-monitor-client.c:135 #59 0x000000020386ff81 in gnome_vfs_volume_monitor_client_init ( volume_monitor_client=0x885920) at gnome-vfs-volume-monitor-client.c:182 #60 0x0000000203c44a67 in g_type_create_instance (type=0) at gtype.c:1595 #61 0x0000000203c31811 in g_object_constructor (type=0, n_construct_properties=0, construct_params=0x0) at gobject.c:1044 #62 0x0000000203c31186 in g_object_newv (object_type=8932608, n_parameters=0, parameters=0x0) at gobject.c:941 #63 0x0000000203c314ed in g_object_new_valist (object_type=8932608, first_property_name=0x0, var_args=0x7fffffffe2b0) at gobject.c:984 #64 0x0000000203c30d94 in g_object_new (object_type=8932608, first_property_name=0x0) at gobject.c:822 #65 0x0000000203871e4c in _gnome_vfs_get_volume_monitor_internal (create=1) at gnome-vfs-volume-monitor.c:226 #66 0x0000000203871ec2 in gnome_vfs_get_volume_monitor () at gnome-vfs-volume-monitor.c:238 #67 0x0000000000429cc2 in nautilus_application_instance_init ( application=0x884800) at nautilus-application.c:183 #68 0x0000000203c44a67 in g_type_create_instance (type=0) at gtype.c:1595 #69 0x0000000203c31811 in g_object_constructor (type=0, n_construct_properties=1, construct_params=0x8dabc0) at gobject.c:1044 #70 0x000000020359ee99 in bonobo_object_constructor (type=8930688, n_construct_properties=4, construct_properties=0x6) at bonobo-object.c:813 ---Type to continue, or q to quit--- #71 0x0000000203c31186 in g_object_newv (object_type=8930688, n_parameters=0, parameters=0x0) at gobject.c:941 #72 0x0000000203c314ed in g_object_new_valist (object_type=8930688, first_property_name=0x0, var_args=0x7fffffffe660) at gobject.c:984 #73 0x0000000203c30d94 in g_object_new (object_type=8930688, first_property_name=0x0) at gobject.c:822 #74 0x0000000000429d91 in nautilus_application_new () at nautilus-application.c:202 #75 0x0000000000434c3d in main (argc=6153216, argv=0x7fffffffe990) at nautilus-main.c:319 From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 2 15:37:09 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D03DD16A4CE; Wed, 2 Jun 2004 15:37:09 -0700 (PDT) Received: from creme-brulee.marcuscom.com (rrcs-midsouth-24-172-16-118.biz.rr.com [24.172.16.118]) by mx1.FreeBSD.org (Postfix) with ESMTP id 779FD43D1F; Wed, 2 Jun 2004 15:37:09 -0700 (PDT) (envelope-from marcus@marcuscom.com) Received: from [10.2.1.70] (vpn-client-70.marcuscom.com [10.2.1.70]) i52Malmw036399; Wed, 2 Jun 2004 18:36:47 -0400 (EDT) (envelope-from marcus@marcuscom.com) From: Joe Marcus Clarke To: Sean McNeil In-Reply-To: <1086212315.66953.1.camel@server.mcneil.com> References: <1086203721.60191.2.camel@server.mcneil.com> <1086204118.514.11.camel@gyros> <1086212315.66953.1.camel@server.mcneil.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-fJL9iIt/kpKEdPnREvLs" Organization: MarcusCom, Inc. Message-Id: <1086215867.514.20.camel@gyros> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 02 Jun 2004 18:37:47 -0400 X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on creme-brulee.marcuscom.com cc: freebsd-gnome@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: backtrace of nautilus core dump on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 22:37:10 -0000 --=-fJL9iIt/kpKEdPnREvLs Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Wed, 2004-06-02 at 17:38, Sean McNeil wrote: > On Wed, 2004-06-02 at 12:21, Joe Marcus Clarke wrote: > > On Wed, 2004-06-02 at 15:15, Sean McNeil wrote: > > > Here is a core dump of nautilus. The only interesting difference in = my > > > environment is that I use ldap/nss_ldap. Other than that, everything > > > should be just like everyone else: > >=20 > > There are no symbols in this backtrace. Please recompile everything > > with debugging flags. Also, try disabling nss_ldap, and see if it make= s > > a difference. > >=20 > > Joe >=20 > Here is a backtrace with the application built including symbols > (portupgrade -fR nautilus2-2.6.1): I don't really see a bug here, but the stack is in pretty bad shape.=20 You might try filing this with GNOME's Bugzilla. Since I don't have an amd64 machine, I won't be able to do any recreation of this. However, no other 64-bit users have complained, so maybe there is a local problem on your system. Joe >=20 --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-fJL9iIt/kpKEdPnREvLs Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBAvla7b2iPiv4Uz4cRAo3/AJ9em6PXiUfEJO78W0EU1dWJ0OUNAACfQe5M UQHGSHOEbvCWVYbRV/WpZYc= =WB+0 -----END PGP SIGNATURE----- --=-fJL9iIt/kpKEdPnREvLs-- From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 2 16:03:17 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D756916A4CE; Wed, 2 Jun 2004 16:03:17 -0700 (PDT) Received: from smtp01.syd.iprimus.net.au (smtp01.syd.iprimus.net.au [210.50.30.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 11F1643D48; Wed, 2 Jun 2004 16:03:17 -0700 (PDT) (envelope-from tim@robbins.dropbear.id.au) Received: from robbins.dropbear.id.au (210.50.200.168) by smtp01.syd.iprimus.net.au (7.0.024) id 40B7A0DA00181AC8; Thu, 3 Jun 2004 09:03:15 +1000 Received: by robbins.dropbear.id.au (Postfix, from userid 1000) id EB30441D0; Thu, 3 Jun 2004 09:04:15 +1000 (EST) Date: Thu, 3 Jun 2004 09:04:15 +1000 From: Tim Robbins To: Joe Marcus Clarke Message-ID: <20040602230415.GA14177@cat.robbins.dropbear.id.au> References: <1086203721.60191.2.camel@server.mcneil.com> <1086204118.514.11.camel@gyros> <1086212315.66953.1.camel@server.mcneil.com> <1086215867.514.20.camel@gyros> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1086215867.514.20.camel@gyros> User-Agent: Mutt/1.4.1i cc: freebsd-amd64@freebsd.org cc: Sean McNeil cc: freebsd-gnome@freebsd.org Subject: Re: backtrace of nautilus core dump on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 23:03:18 -0000 On Wed, Jun 02, 2004 at 06:37:47PM -0400, Joe Marcus Clarke wrote: > On Wed, 2004-06-02 at 17:38, Sean McNeil wrote: > > On Wed, 2004-06-02 at 12:21, Joe Marcus Clarke wrote: > > > On Wed, 2004-06-02 at 15:15, Sean McNeil wrote: > > > > Here is a core dump of nautilus. The only interesting difference in my > > > > environment is that I use ldap/nss_ldap. Other than that, everything > > > > should be just like everyone else: > > > > > > There are no symbols in this backtrace. Please recompile everything > > > with debugging flags. Also, try disabling nss_ldap, and see if it makes > > > a difference. > > > > > > Joe > > > > Here is a backtrace with the application built including symbols > > (portupgrade -fR nautilus2-2.6.1): > > I don't really see a bug here, but the stack is in pretty bad shape. > You might try filing this with GNOME's Bugzilla. Since I don't have an > amd64 machine, I won't be able to do any recreation of this. However, > no other 64-bit users have complained, so maybe there is a local problem > on your system. GNOME is generally unusable on amd64. Nautilus and the panel both work fine, but most other apps crash so often as to be useless: gnome-terminal, rhythmbox, gst-player, gpdf, ggv. Tim From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 2 17:19:17 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 02C7C16A4CE; Wed, 2 Jun 2004 17:19:17 -0700 (PDT) Received: from smtp01.syd.iprimus.net.au (smtp01.syd.iprimus.net.au [210.50.30.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 478A643D48; Wed, 2 Jun 2004 17:19:16 -0700 (PDT) (envelope-from tim@robbins.dropbear.id.au) Received: from robbins.dropbear.id.au (210.50.200.168) by smtp01.syd.iprimus.net.au (7.0.024) id 40B7A0DA00186C44; Thu, 3 Jun 2004 10:19:14 +1000 Received: by robbins.dropbear.id.au (Postfix, from userid 1000) id 13F0741CB; Thu, 3 Jun 2004 10:20:15 +1000 (EST) Date: Thu, 3 Jun 2004 10:20:15 +1000 From: Tim Robbins To: David Schultz Message-ID: <20040603002015.GA14544@cat.robbins.dropbear.id.au> References: <20040602064846.GA6124@VARK.homeunix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040602064846.GA6124@VARK.homeunix.com> User-Agent: Mutt/1.4.1i cc: amd64@freebsd.org Subject: Re: Initial FP exception flags incorrect on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jun 2004 00:19:17 -0000 On Tue, Jun 01, 2004 at 11:48:46PM -0700, David Schultz wrote: > I discovered that new processes on amd64 have the inexact flag > raised by default, at least on sledge. However, all the sticky > flags should be clear initially. [...] > I don't have any amd64 hardware of my own to test kernel patches > on, but if I were to make a wild guess as to how to solve the > problem, it would be the following patch. I would appreciate it > if someone could address the problem, or at least let me know > whether my proposed fix works. > > Index: sys/amd64/amd64/fpu.c > =================================================================== > RCS file: /cvs/src/sys/amd64/amd64/fpu.c,v > retrieving revision 1.149 > diff -u -r1.149 fpu.c > --- fpu.c 5 Apr 2004 21:25:51 -0000 1.149 > +++ fpu.c 2 Jun 2004 06:08:34 -0000 > @@ -73,6 +73,7 @@ > #define fnstsw(addr) __asm __volatile("fnstsw %0" : "=m" (*(addr))) > #define fxrstor(addr) __asm("fxrstor %0" : : "m" (*(addr))) > #define fxsave(addr) __asm __volatile("fxsave %0" : "=m" (*(addr))) > +#define stmxcsr(addr) __asm("stmxcsr %0" : "=m" (*(addr))) > #define start_emulating() __asm("smsw %%ax; orb %0,%%al; lmsw %%ax" \ > : : "n" (CR0_TS) : "ax") > #define stop_emulating() __asm("clts") > @@ -119,6 +120,8 @@ > fninit(); > control = __INITIAL_FPUCW__; > fldcw(&control); > + control = __INITIAL_MXCSR__; > + stmxcsr(&control); > fxsave(&fpu_cleanstate); > start_emulating(); > fpu_cleanstate_ready = 1; This seems to cause a panic (trap 12) on startup. Shouldn't it be ldmxcsr instead? Changing that causes a different kind of panic (trap 9.) Tim From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 2 18:53:15 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D68A16A4CE for ; Wed, 2 Jun 2004 18:53:15 -0700 (PDT) Received: from VARK.homeunix.com (ar59.lsanca2-4.27.98.47.lsanca2.dsl-verizon.net [4.27.98.47]) by mx1.FreeBSD.org (Postfix) with ESMTP id E84CD43D1F for ; Wed, 2 Jun 2004 18:53:14 -0700 (PDT) (envelope-from das@FreeBSD.ORG) Received: from VARK.homeunix.com (localhost [127.0.0.1]) by VARK.homeunix.com (8.12.11/8.12.10) with ESMTP id i531rFXL003311; Wed, 2 Jun 2004 18:53:15 -0700 (PDT) (envelope-from das@FreeBSD.ORG) Received: (from das@localhost) by VARK.homeunix.com (8.12.11/8.12.10/Submit) id i531rFvL003310; Wed, 2 Jun 2004 18:53:15 -0700 (PDT) (envelope-from das@FreeBSD.ORG) Date: Wed, 2 Jun 2004 18:53:15 -0700 From: David Schultz To: Tim Robbins Message-ID: <20040603015315.GA739@VARK.homeunix.com> References: <20040602064846.GA6124@VARK.homeunix.com> <20040603002015.GA14544@cat.robbins.dropbear.id.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040603002015.GA14544@cat.robbins.dropbear.id.au> cc: amd64@FreeBSD.ORG Subject: Re: Initial FP exception flags incorrect on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jun 2004 01:53:15 -0000 On Thu, Jun 03, 2004, Tim Robbins wrote: > On Tue, Jun 01, 2004 at 11:48:46PM -0700, David Schultz wrote: > > I discovered that new processes on amd64 have the inexact flag > > raised by default, at least on sledge. However, all the sticky > > flags should be clear initially. > [...] > > I don't have any amd64 hardware of my own to test kernel patches > > on, but if I were to make a wild guess as to how to solve the > > problem, it would be the following patch. I would appreciate it > > if someone could address the problem, or at least let me know > > whether my proposed fix works. > > > > Index: sys/amd64/amd64/fpu.c > > =================================================================== > > RCS file: /cvs/src/sys/amd64/amd64/fpu.c,v > > retrieving revision 1.149 > > diff -u -r1.149 fpu.c > > --- fpu.c 5 Apr 2004 21:25:51 -0000 1.149 > > +++ fpu.c 2 Jun 2004 06:08:34 -0000 > > @@ -73,6 +73,7 @@ > > #define fnstsw(addr) __asm __volatile("fnstsw %0" : "=m" (*(addr))) > > #define fxrstor(addr) __asm("fxrstor %0" : : "m" (*(addr))) > > #define fxsave(addr) __asm __volatile("fxsave %0" : "=m" (*(addr))) > > +#define stmxcsr(addr) __asm("stmxcsr %0" : "=m" (*(addr))) > > #define start_emulating() __asm("smsw %%ax; orb %0,%%al; lmsw %%ax" \ > > : : "n" (CR0_TS) : "ax") > > #define stop_emulating() __asm("clts") > > @@ -119,6 +120,8 @@ > > fninit(); > > control = __INITIAL_FPUCW__; > > fldcw(&control); > > + control = __INITIAL_MXCSR__; > > + stmxcsr(&control); > > fxsave(&fpu_cleanstate); > > start_emulating(); > > fpu_cleanstate_ready = 1; > > This seems to cause a panic (trap 12) on startup. Shouldn't it be ldmxcsr > instead? Changing that causes a different kind of panic (trap 9.) Oops, you're right. The other problem is probably that control is a u_short, so garbage gets loaded into the upper 16 bits of the CSR. Making 'control' a u_int should fix the problem, but the following patch introduces a new variable to avoid relying on endianness for the fldcw. Thanks, Tim! Index: sys/amd64/amd64/fpu.c =================================================================== RCS file: /cvs/src/sys/amd64/amd64/fpu.c,v retrieving revision 1.149 diff -u -r1.149 fpu.c --- sys/amd64/amd64/fpu.c 5 Apr 2004 21:25:51 -0000 1.149 +++ sys/amd64/amd64/fpu.c 3 Jun 2004 01:48:23 -0000 @@ -73,6 +73,7 @@ #define fnstsw(addr) __asm __volatile("fnstsw %0" : "=m" (*(addr))) #define fxrstor(addr) __asm("fxrstor %0" : : "m" (*(addr))) #define fxsave(addr) __asm __volatile("fxsave %0" : "=m" (*(addr))) +#define ldmxcsr(r) __asm __volatile("ldmxcsr %0" : : "m" (r)) #define start_emulating() __asm("smsw %%ax; orb %0,%%al; lmsw %%ax" \ : : "n" (CR0_TS) : "ax") #define stop_emulating() __asm("clts") @@ -111,6 +112,7 @@ fpuinit(void) { register_t savecrit; + u_int mxcsr; u_short control; savecrit = intr_disable(); @@ -119,6 +121,8 @@ fninit(); control = __INITIAL_FPUCW__; fldcw(&control); + mxcsr = __INITIAL_MXCSR__; + ldmxcsr(mxcsr); fxsave(&fpu_cleanstate); start_emulating(); fpu_cleanstate_ready = 1; From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 2 21:15:32 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B0FBD16A4CE; Wed, 2 Jun 2004 21:15:32 -0700 (PDT) Received: from mail.mcneil.com (rrcs-west-24-199-45-54.biz.rr.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 83B7E43D4C; Wed, 2 Jun 2004 21:15:32 -0700 (PDT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 73583FD03A; Wed, 2 Jun 2004 21:15:34 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 14256-04; Wed, 2 Jun 2004 21:15:33 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 9E28FFD020; Wed, 2 Jun 2004 21:15:33 -0700 (PDT) From: Sean McNeil To: Tim Robbins In-Reply-To: <20040602230415.GA14177@cat.robbins.dropbear.id.au> References: <1086203721.60191.2.camel@server.mcneil.com> <1086204118.514.11.camel@gyros> <1086212315.66953.1.camel@server.mcneil.com> <1086215867.514.20.camel@gyros> <20040602230415.GA14177@cat.robbins.dropbear.id.au> Content-Type: text/plain Message-Id: <1086236133.81122.2.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 02 Jun 2004 21:15:33 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com cc: Joe Marcus Clarke cc: freebsd-amd64@freebsd.org cc: freebsd-gnome@freebsd.org Subject: Re: backtrace of nautilus core dump on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jun 2004 04:15:32 -0000 On Wed, 2004-06-02 at 16:04, Tim Robbins wrote: > On Wed, Jun 02, 2004 at 06:37:47PM -0400, Joe Marcus Clarke wrote: > > > On Wed, 2004-06-02 at 17:38, Sean McNeil wrote: > > > On Wed, 2004-06-02 at 12:21, Joe Marcus Clarke wrote: > > > > On Wed, 2004-06-02 at 15:15, Sean McNeil wrote: > > > > > Here is a core dump of nautilus. The only interesting difference in my > > > > > environment is that I use ldap/nss_ldap. Other than that, everything > > > > > should be just like everyone else: > > > > > > > > There are no symbols in this backtrace. Please recompile everything > > > > with debugging flags. Also, try disabling nss_ldap, and see if it makes > > > > a difference. > > > > > > > > Joe > > > > > > Here is a backtrace with the application built including symbols > > > (portupgrade -fR nautilus2-2.6.1): > > > > I don't really see a bug here, but the stack is in pretty bad shape. > > You might try filing this with GNOME's Bugzilla. Since I don't have an > > amd64 machine, I won't be able to do any recreation of this. However, > > no other 64-bit users have complained, so maybe there is a local problem > > on your system. > > GNOME is generally unusable on amd64. Nautilus and the panel both work fine, > but most other apps crash so often as to be useless: gnome-terminal, > rhythmbox, gst-player, gpdf, ggv. > > > Tim This turns out to be a problem with my /etc/fstab file. When I delete the comment lines and the user mounted devices then nautilus came up just fine. Here is what my /etc/fstab looked like when it was failing: # Device Mountpoint FStype Options Dump Pass# /dev/ad6s1b none swap sw 0 0 /dev/ad6s1a / ufs rw 1 1 /dev/ar0s1e /home ufs rw 1 1 proc /proc procfs rw 0 0 #linproc /compat/linux/proc linprocfs rw 0 0 # user mounted devices /dev/cd0 /home/sean/mnt/dvd0 udf rw,noauto 0 0 /dev/cd1 /home/sean/mnt/dvd1 udf rw,noauto 0 0 /dev/cd0 /home/sean/mnt/cdrom0 cd9660 ro,noauto 0 0 /dev/cd1 /home/sean/mnt/cdrom1 cd9660 ro,noauto 0 0 /dev/da0s1 /home/sean/mnt/pen msdos rw,noauto 0 0 From owner-freebsd-amd64@FreeBSD.ORG Thu Jun 3 02:27:11 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 048A816A4F9; Thu, 3 Jun 2004 02:27:11 -0700 (PDT) Received: from mail.mcneil.com (rrcs-west-24-199-45-54.biz.rr.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id D304E43D54; Thu, 3 Jun 2004 02:27:08 -0700 (PDT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 75434FD02B; Thu, 3 Jun 2004 02:26:58 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00671-09; Thu, 3 Jun 2004 02:26:53 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id AD6E3FD02A; Thu, 3 Jun 2004 02:26:51 -0700 (PDT) From: Sean McNeil To: freebsd-amd64@freebsd.org, freebsd-current@freebsd.org, freebsd-ports@freebsd.org Content-Type: text/plain Message-Id: <1086254809.81807.10.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Thu, 03 Jun 2004 02:26:51 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com Subject: bash core dumping when resize gnome-terminal on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jun 2004 09:27:11 -0000 I did some investigation into a core dump of bash that I have been having. First, I do not know if this problem exists with the i386 arch, but it is possible. I never noticed it. I use nss_ldap. There were some efforts to purge shared libraries from explicitly linking to libthread.so whenever they do not directly use pthread functions as this can cause issues with the nss layer in libc. Some of those issues have been addressed. Some, unfortunately, are still around. I just found a new one: My openldap, used by nss_ldap, uses sasl. sasl in turn uses db41. db41 is building /usr/local/lib/libdb41.so.1 with an explicit link to libpthread.so. This is because of line 3263 in dist/configure setting LDFLAGS to use -lpthread. This is wrong. It explicitly links programs correctly with -lpthread and LDFLAGS is used with creating shared libraries (don't know why, it really shouldn't as it isn't linking). The following patch fixed my core dumps of bash on window resizes: *** work/db-4.1.25/dist/configure~ Thu Jun 3 02:03:44 2004 --- work/db-4.1.25/dist/configure Thu Jun 3 02:04:08 2004 *************** bsdi3*) optimize_def="-O2" *** 3259,3265 **** bsdi*) optimize_def="-O2";; freebsd*) optimize_def="-O2" ! CPPFLAGS="$CPPFLAGS -D_THREAD_SAFE" hpux*) CPPFLAGS="$CPPFLAGS -D_REENTRANT";; irix*) optimize_def="-O2" CPPFLAGS="$CPPFLAGS -D_SGI_MP_SOURCE";; --- 3259,3265 ---- bsdi*) optimize_def="-O2";; freebsd*) optimize_def="-O2" ! CPPFLAGS="$CPPFLAGS -D_THREAD_SAFE";; hpux*) CPPFLAGS="$CPPFLAGS -D_REENTRANT";; irix*) optimize_def="-O2" CPPFLAGS="$CPPFLAGS -D_SGI_MP_SOURCE";; From owner-freebsd-amd64@FreeBSD.ORG Thu Jun 3 12:12:14 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 62B0916A4CE; Thu, 3 Jun 2004 12:12:14 -0700 (PDT) Received: from mail.mcneil.com (rrcs-west-24-199-45-54.biz.rr.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 00A1E43D54; Thu, 3 Jun 2004 12:12:14 -0700 (PDT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 8C82CFD029; Thu, 3 Jun 2004 12:12:13 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 25239-09; Thu, 3 Jun 2004 12:12:13 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id D38D1FD020; Thu, 3 Jun 2004 12:12:12 -0700 (PDT) From: Sean McNeil To: freebsd-amd64@freebsd.org In-Reply-To: <1086254809.81807.10.camel@server.mcneil.com> References: <1086254809.81807.10.camel@server.mcneil.com> Content-Type: text/plain Message-Id: <1086289932.53327.1.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Thu, 03 Jun 2004 12:12:12 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com cc: freebsd-current@freebsd.org cc: freebsd-ports@freebsd.org Subject: Re: bash core dumping when resize gnome-terminal on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jun 2004 19:12:14 -0000 On Thu, 2004-06-03 at 02:26, Sean McNeil wrote: > I did some investigation into a core dump of bash that I have been > having. First, I do not know if this problem exists with the i386 arch, > but it is possible. I never noticed it. > > I use nss_ldap. There were some efforts to purge shared libraries from > explicitly linking to libthread.so whenever they do not directly use > pthread functions as this can cause issues with the nss layer in libc. > Some of those issues have been addressed. Some, unfortunately, are > still around. I just found a new one: > > My openldap, used by nss_ldap, uses sasl. sasl in turn uses db41. db41 > is building /usr/local/lib/libdb41.so.1 with an explicit link to > libpthread.so. This is because of line 3263 in dist/configure setting > LDFLAGS to use -lpthread. This is wrong. It explicitly links programs > correctly with -lpthread and LDFLAGS is used with creating shared > libraries (don't know why, it really shouldn't as it isn't linking). > The following patch fixed my core dumps of bash on window resizes: > > *** work/db-4.1.25/dist/configure~ Thu Jun 3 02:03:44 2004 > --- work/db-4.1.25/dist/configure Thu Jun 3 02:04:08 2004 > *************** bsdi3*) optimize_def="-O2" > *** 3259,3265 **** > bsdi*) optimize_def="-O2";; > freebsd*) > optimize_def="-O2" > ! CPPFLAGS="$CPPFLAGS -D_THREAD_SAFE" > hpux*) CPPFLAGS="$CPPFLAGS -D_REENTRANT";; > irix*) optimize_def="-O2" > CPPFLAGS="$CPPFLAGS -D_SGI_MP_SOURCE";; > --- 3259,3265 ---- > bsdi*) optimize_def="-O2";; > freebsd*) > optimize_def="-O2" > ! CPPFLAGS="$CPPFLAGS -D_THREAD_SAFE";; > hpux*) CPPFLAGS="$CPPFLAGS -D_REENTRANT";; > irix*) optimize_def="-O2" > CPPFLAGS="$CPPFLAGS -D_SGI_MP_SOURCE";; Oops. I had an error that I fixed and didn't realize the above patch is bogus. It should have been taking out the LDFLAGS setting and adding the ;; to the line above. Sean From owner-freebsd-amd64@FreeBSD.ORG Thu Jun 3 12:59:20 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 35D3116A4FC; Thu, 3 Jun 2004 12:59:20 -0700 (PDT) Received: from out003.verizon.net (out003pub.verizon.net [206.46.170.103]) by mx1.FreeBSD.org (Postfix) with ESMTP id 84EF943D2F; Thu, 3 Jun 2004 12:59:19 -0700 (PDT) (envelope-from dfeustel@mindspring.com) Received: from atlnga1-ar3-4-33-228-225.atlnga1.dsl-verizon.net ([4.33.228.225]) by out003.verizon.netESMTP <20040603195918.TXZJ6671.out003.verizon.net@atlnga1-ar3-4-33-228-225.atlnga1.dsl-verizon.net>; Thu, 3 Jun 2004 14:59:18 -0500 From: Dave Feustel To: Sean McNeil , freebsd-amd64@freebsd.org Date: Thu, 3 Jun 2004 14:57:57 -0500 User-Agent: KMail/1.5.3 References: <1086254809.81807.10.camel@server.mcneil.com> <1086289932.53327.1.camel@server.mcneil.com> In-Reply-To: <1086289932.53327.1.camel@server.mcneil.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200406031457.57841.dfeustel@mindspring.com> X-Authentication-Info: Submitted using SMTP AUTH at out003.verizon.net from [4.33.228.225] at Thu, 3 Jun 2004 14:59:18 -0500 cc: freebsd-current@freebsd.org Subject: Re: bash core dumping when resize gnome-terminal on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: dfeustel@mindspring.com List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jun 2004 19:59:20 -0000 On Thursday 03 June 2004 02:12 pm, Sean McNeil wrote: > > I did some investigation into a core dump of bash that I have been > > having. First, I do not know if this problem exists with the i386 arch, > > but it is possible. I never noticed it. Resizing vi inside of a kde shell window will very often crash vi. This has been going on for some time. It is not a serious problem. From owner-freebsd-amd64@FreeBSD.ORG Thu Jun 3 13:05:45 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C572916A4CE; Thu, 3 Jun 2004 13:05:45 -0700 (PDT) Received: from mail.mcneil.com (rrcs-west-24-199-45-54.biz.rr.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 903F343D31; Thu, 3 Jun 2004 13:05:45 -0700 (PDT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id BE4DBFD029; Thu, 3 Jun 2004 13:05:44 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 31719-02; Thu, 3 Jun 2004 13:05:44 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 3D8C8FD01A; Thu, 3 Jun 2004 13:05:44 -0700 (PDT) From: Sean McNeil To: dfeustel@mindspring.com In-Reply-To: <200406031457.57841.dfeustel@mindspring.com> References: <1086254809.81807.10.camel@server.mcneil.com> <1086289932.53327.1.camel@server.mcneil.com> <200406031457.57841.dfeustel@mindspring.com> Content-Type: text/plain Message-Id: <1086293143.73536.4.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Thu, 03 Jun 2004 13:05:44 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com cc: freebsd-current@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: bash core dumping when resize gnome-terminal on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jun 2004 20:05:45 -0000 On Thu, 2004-06-03 at 12:57, Dave Feustel wrote: > On Thursday 03 June 2004 02:12 pm, Sean McNeil wrote: > > > I did some investigation into a core dump of bash that I have been > > > having. First, I do not know if this problem exists with the i386 arch, > > > but it is possible. I never noticed it. > > Resizing vi inside of a kde shell window will very often crash vi. > This has been going on for some time. It is not a serious problem. I have fixed the issue for bash (see thread). Are you using nss_ldap? If so, my fix may help your vi issue as well. I actually think there is a latent bug somewhere in sigaction. I get all kinds of crashes that have the feeling of improperly handled signals. The bash resize issue was related to restarting the sigaction in libpthread. I'm just hiding the real issue by making sure that the pthread library isn't pulled in just because of nss_ldap. Sean From owner-freebsd-amd64@FreeBSD.ORG Thu Jun 3 15:53:29 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5535C16A4CE; Thu, 3 Jun 2004 15:53:29 -0700 (PDT) Received: from mail.mcneil.com (rrcs-west-24-199-45-54.biz.rr.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2877243D2F; Thu, 3 Jun 2004 15:53:27 -0700 (PDT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id A3D48FD029; Thu, 3 Jun 2004 15:53:26 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 12576-09; Thu, 3 Jun 2004 15:53:26 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id E543DFD020; Thu, 3 Jun 2004 15:53:25 -0700 (PDT) From: Sean McNeil To: freebsd-amd64@freebsd.org, freebsd-gnome@freebsd.org Content-Type: text/plain Message-Id: <1086303205.87004.3.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Thu, 03 Jun 2004 15:53:25 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com Subject: evolution compilation on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jun 2004 22:53:29 -0000 I get an error when compiling evolution on amd64: cc -shared address-conduit.lo -Wl,--whole-archive ../../e-util/ename/.libs/libename-static.al ../../addressbook/backend/ebook/.libs/libebook-static.a -Wl,--no-whole-archive -Wl,--rpath -Wl,/usr/ports/mail/evolution/work/evolution-1.4.6/e-util/.libs -Wl,--rpath -Wl,/usr/ports/mail/evolution/work/evolution-1.4.6/libversit/.libs -Wl,--rpath -Wl,/usr/ports/mail/evolution/work/evolution-1.4.6/camel/.libs -Wl,--rpath -Wl,/usr/local/lib -Wl,--rpath -Wl,/usr/X11R6/lib/evolution/1.4 -Wl,--rpath -Wl,/usr/local/lib -L/usr/lib -L/usr/ports/mail/evolution/work/evolution-1.4.6/e-util/.libs -L/usr/X11R6/lib -L/usr/local/lib ../../e-util/.libs/libeutil.so ../../libversit/.libs/libversit.so ../../e-util/.libs/libeconduit.so ../../camel/.libs/libcamel.so -lgpilotd -lgpilotdcm -lgpilotdconduit /usr/local/lib/libpisock.so /usr/local/lib/libpisync.so -lgal-2.0 -lgal-a11y-2.0 -lglade-2.0 -lgnomeui-2 -lSM -lICE -lbonoboui-2 -lgnome-2 -lpopt -lbonobo-2 -lgconf-2 -lgnomevfs-2 -lbonobo-activation -lORBit-2 -lgthread-2.0 -lgnomeprintui-2-2 -lgnomeprint-2-2 -lgnomecanvas-2 -lxml2 -lart_lgpl_2 -lpangoft2-1.0 -lgtk-x11-2.0 -lgdk-x11-2.0 -lXrandr -lXi -lXinerama -lXcursor -latk-1.0 -lgdk_pixbuf-2.0 -lm -lpangoxft-1.0 -lXft -lfreetype -lz -lXrender -lXext -lfontconfig -lpangox-1.0 -lX11 -lpango-1.0 -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -liconv -lpthread -Wl,--export-dynamic -Wl,-soname -Wl,libeaddress_conduit.so -o .libs/libeaddress_conduit.so /usr/bin/ld: ../../addressbook/backend/ebook/.libs/libebook-static.a(addressbook-stubs.o): relocation R_X86_64_32S can not be used when making a shared object; recompile with -fPIC ../../addressbook/backend/ebook/.libs/libebook-static.a(addressbook-stubs.o): could not read symbols: Bad value gmake[3]: *** [libeaddress_conduit.la] Error 1 The following patch will get me past this issue. I would think this to be a problem on any arch other than i386. For some reason, i386 allows for normally build archives to be included into shared libraries... *** Makefile.orig Thu Jun 3 15:34:38 2004 --- Makefile Thu Jun 3 15:12:25 2004 *************** CONFIGURE_ARGS+=--with-openldap=${LOCALB *** 64,69 **** --- 64,73 ---- CONFIGURE_ARGS+=--with-openldap=no .endif + .if ${ARCH} == "amd64" + CONFIGURE_ARGS+=--with-pic + .endif + post-patch: @${FIND} ${WRKSRC} -type f -name "*.[ch]" | ${XARGS} ${GREP} -l '' | \ ${XARGS} ${REINPLACE_CMD} -e 's|||g' From owner-freebsd-amd64@FreeBSD.ORG Thu Jun 3 17:45:20 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 88D2D16A4CE for ; Thu, 3 Jun 2004 17:45:20 -0700 (PDT) Received: from mail.mcneil.com (rrcs-west-24-199-45-54.biz.rr.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 51D8E43D1F for ; Thu, 3 Jun 2004 17:45:16 -0700 (PDT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id B3AB1FD11B for ; Thu, 3 Jun 2004 17:45:15 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00676-01 for ; Thu, 3 Jun 2004 17:45:15 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 373D2FD0C8 for ; Thu, 3 Jun 2004 17:45:15 -0700 (PDT) From: Sean McNeil To: freebsd-amd64@freebsd.org Content-Type: text/plain Message-Id: <1086309914.1383.5.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Thu, 03 Jun 2004 17:45:15 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com Subject: readline issues X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jun 2004 00:45:20 -0000 If I run bash from the console and try to edit a previous line, the line isn't being properly updated. It works fine in a gnome-terminal. For instance, if I do: ls -l *.core up-arrow, ctrl-a, del del rm I see that the characters are deleted correctly, but inserts act as overwrite. Is there something I have set for console that is causing this, or is this some sort of bug? Sean From owner-freebsd-amd64@FreeBSD.ORG Thu Jun 3 18:12:59 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 06D6916A4CE for ; Thu, 3 Jun 2004 18:12:59 -0700 (PDT) Received: from bsdhosting.net (bsdhosting.net [65.39.221.113]) by mx1.FreeBSD.org (Postfix) with SMTP id C1C9843D31 for ; Thu, 3 Jun 2004 18:12:58 -0700 (PDT) (envelope-from jhopper@bsdhosting.net) Received: (qmail 86349 invoked from network); 4 Jun 2004 01:12:17 -0000 Received: from unknown (HELO ?192.168.1.6?) (jhopper@bsdhosting.net@65.39.221.113) by bsdhosting.net with SMTP; 4 Jun 2004 01:12:17 -0000 From: Justin Hopper To: freebsd-amd64@freebsd.org In-Reply-To: References: Content-Type: text/plain Message-Id: <1086311576.31042.470.camel@work.gusalmighty.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Thu, 03 Jun 2004 18:12:56 -0700 Content-Transfer-Encoding: 7bit Subject: Re: Why is MySQL nearly twice as fast on Linux/AMD64Vs.FreeBSD/AMD64? (fwd) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jun 2004 01:12:59 -0000 On Fri, 2004-05-21 at 11:32, mike wrote: > out of the box debian blows the hell out of the freebsd setup in most > tests - all running through the local file socket (not over the network) > and compiled the same way. > > there is definately a problem here with threading/etc. Has this discussion moved to threads@? I too am preparing to roll out a production dual Opteron box running MySQL in the next month, and it needs to withstand a severe beating. I can't (or just don't want to take the time to port over my fbsd code to) Linux, so I'm really hoping this threading issue will be resolved soon. -- Justin Hopper UNIX Systems Engineer BSDHosting.net Hosting Division of Digital Oasys Inc. http://www.bsdhosting.net From owner-freebsd-amd64@FreeBSD.ORG Thu Jun 3 18:24:08 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1285516A4CE for ; Thu, 3 Jun 2004 18:24:08 -0700 (PDT) Received: from mail.mikehost.net (lvs-1.voxel.net [207.99.115.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id B1F6A43D1F for ; Thu, 3 Jun 2004 18:24:05 -0700 (PDT) (envelope-from mike@mike2k.com) Received: by mail.mikehost.net (Postfix, from userid 502) id 0E9781BC3F; Thu, 3 Jun 2004 18:24:05 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.mikehost.net (Postfix) with ESMTP id 0C6DB1BC3D; Thu, 3 Jun 2004 18:24:05 -0700 (PDT) Date: Thu, 3 Jun 2004 18:24:04 -0700 (PDT) From: mike X-X-Sender: mike@sql01.internal.mikehost.net To: Justin Hopper In-Reply-To: <1086311576.31042.470.camel@work.gusalmighty.com> Message-ID: References: <1086311576.31042.470.camel@work.gusalmighty.com> mike: yes MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-amd64@freebsd.org Subject: Re: Why is MySQL nearly twice as fast onLinux/AMD64Vs.FreeBSD/AMD64? (fwd) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jun 2004 01:24:08 -0000 sadly, we've put this on the mysql list, freebsd-amd64 and freebsd-threads, even offering $500 to whomever steps up and figures out how to get this performance bottleneck resolved (and access to our servers if needed) - and the discussion seems to have died out. On Thu, 3 Jun 2004, Justin Hopper wrote: > On Fri, 2004-05-21 at 11:32, mike wrote: > > out of the box debian blows the hell out of the freebsd setup in most > > tests - all running through the local file socket (not over the network) > > and compiled the same way. > > > > there is definately a problem here with threading/etc. > > Has this discussion moved to threads@? I too am preparing to roll out a > production dual Opteron box running MySQL in the next month, and it > needs to withstand a severe beating. I can't (or just don't want to > take the time to port over my fbsd code to) Linux, so I'm really hoping > this threading issue will be resolved soon. > > -- > Justin Hopper > UNIX Systems Engineer > BSDHosting.net > Hosting Division of Digital Oasys Inc. > http://www.bsdhosting.net > > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > From owner-freebsd-amd64@FreeBSD.ORG Thu Jun 3 21:24:11 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C6BDE16A4CE; Thu, 3 Jun 2004 21:24:11 -0700 (PDT) Received: from creme-brulee.marcuscom.com (rrcs-midsouth-24-172-16-118.biz.rr.com [24.172.16.118]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0B8AE43D41; Thu, 3 Jun 2004 21:24:11 -0700 (PDT) (envelope-from marcus@marcuscom.com) Received: from [192.168.1.4] (shumai.marcuscom.com [192.168.1.4]) i544NdnA051630; Fri, 4 Jun 2004 00:23:39 -0400 (EDT) (envelope-from marcus@marcuscom.com) From: Joe Marcus Clarke To: Sean McNeil In-Reply-To: <1086303205.87004.3.camel@server.mcneil.com> References: <1086303205.87004.3.camel@server.mcneil.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-At+sVBXgKcwikd3IUm1l" Organization: MarcusCom, Inc. Message-Id: <1086323045.41634.10.camel@shumai.marcuscom.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Fri, 04 Jun 2004 00:24:05 -0400 X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on creme-brulee.marcuscom.com cc: freebsd-gnome@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: evolution compilation on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jun 2004 04:24:12 -0000 --=-At+sVBXgKcwikd3IUm1l Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Thu, 2004-06-03 at 18:53, Sean McNeil wrote: > I get an error when compiling evolution on amd64: >=20 > cc -shared address-conduit.lo -Wl,--whole-archive > ../../e-util/ename/.libs/libename-static.al > ../../addressbook/backend/ebook/.libs/libebook-static.a > -Wl,--no-whole-archive -Wl,--rpath > -Wl,/usr/ports/mail/evolution/work/evolution-1.4.6/e-util/.libs > -Wl,--rpath > -Wl,/usr/ports/mail/evolution/work/evolution-1.4.6/libversit/.libs > -Wl,--rpath > -Wl,/usr/ports/mail/evolution/work/evolution-1.4.6/camel/.libs > -Wl,--rpath -Wl,/usr/local/lib -Wl,--rpath > -Wl,/usr/X11R6/lib/evolution/1.4 -Wl,--rpath -Wl,/usr/local/lib > -L/usr/lib -L/usr/ports/mail/evolution/work/evolution-1.4.6/e-util/.libs > -L/usr/X11R6/lib -L/usr/local/lib ../../e-util/.libs/libeutil.so > ../../libversit/.libs/libversit.so ../../e-util/.libs/libeconduit.so > ../../camel/.libs/libcamel.so -lgpilotd -lgpilotdcm -lgpilotdconduit > /usr/local/lib/libpisock.so /usr/local/lib/libpisync.so -lgal-2.0 > -lgal-a11y-2.0 -lglade-2.0 -lgnomeui-2 -lSM -lICE -lbonoboui-2 -lgnome-2 > -lpopt -lbonobo-2 -lgconf-2 -lgnomevfs-2 -lbonobo-activation -lORBit-2 > -lgthread-2.0 -lgnomeprintui-2-2 -lgnomeprint-2-2 -lgnomecanvas-2 -lxml2 > -lart_lgpl_2 -lpangoft2-1.0 -lgtk-x11-2.0 -lgdk-x11-2.0 -lXrandr -lXi > -lXinerama -lXcursor -latk-1.0 -lgdk_pixbuf-2.0 -lm -lpangoxft-1.0 -lXft > -lfreetype -lz -lXrender -lXext -lfontconfig -lpangox-1.0 -lX11 > -lpango-1.0 -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -liconv -lpthread=20 > -Wl,--export-dynamic -Wl,-soname -Wl,libeaddress_conduit.so -o > .libs/libeaddress_conduit.so > /usr/bin/ld: > ../../addressbook/backend/ebook/.libs/libebook-static.a(addressbook-stubs= .o): relocation R_X86_64_32S can not be used when making a shared object; r= ecompile with -fPIC > ../../addressbook/backend/ebook/.libs/libebook-static.a(addressbook-stubs= .o): could not read symbols: Bad value > gmake[3]: *** [libeaddress_conduit.la] Error 1 >=20 > The following patch will get me past this issue. I would think this to > be a problem on any arch other than i386. For some reason, i386 allows > for normally build archives to be included into shared libraries... >=20 > *** Makefile.orig Thu Jun 3 15:34:38 2004 > --- Makefile Thu Jun 3 15:12:25 2004 > *************** CONFIGURE_ARGS+=3D--with-openldap=3D${LOCALB > *** 64,69 **** > --- 64,73 ---- > CONFIGURE_ARGS+=3D--with-openldap=3Dno > .endif >=20 > + .if ${ARCH} =3D=3D "amd64" > + CONFIGURE_ARGS+=3D--with-pic > + .endif > + > post-patch: > @${FIND} ${WRKSRC} -type f -name "*.[ch]" | ${XARGS} ${GREP} -l '= ' | \ > ${XARGS} ${REINPLACE_CMD} -e 's|||g' Committed, thanks! Joe >=20 >=20 > _______________________________________________ > freebsd-gnome@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-gnome > To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@freebsd.org" --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-At+sVBXgKcwikd3IUm1l Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBAv/lkb2iPiv4Uz4cRAv2EAJ4hmwe8NLY9v3ua5aHHkPdGept0/gCfWYwi f8K94HBmO0nNkG8g16ysYPs= =v3cz -----END PGP SIGNATURE----- --=-At+sVBXgKcwikd3IUm1l-- From owner-freebsd-amd64@FreeBSD.ORG Thu Jun 3 21:31:36 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 54DB316A4CE; Thu, 3 Jun 2004 21:31:36 -0700 (PDT) Received: from mail.mcneil.com (rrcs-west-24-199-45-54.biz.rr.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D0DD43D3F; Thu, 3 Jun 2004 21:31:36 -0700 (PDT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 0A621FD0D7; Thu, 3 Jun 2004 21:31:36 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00676-06; Thu, 3 Jun 2004 21:31:35 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 9DBE0FD029; Thu, 3 Jun 2004 21:31:35 -0700 (PDT) From: Sean McNeil To: Joe Marcus Clarke In-Reply-To: <1086323045.41634.10.camel@shumai.marcuscom.com> References: <1086303205.87004.3.camel@server.mcneil.com> <1086323045.41634.10.camel@shumai.marcuscom.com> Content-Type: text/plain Message-Id: <1086323495.48282.20.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Thu, 03 Jun 2004 21:31:35 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com cc: freebsd-gnome@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: evolution compilation on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jun 2004 04:31:36 -0000 On Thu, 2004-06-03 at 21:24, Joe Marcus Clarke wrote: > > + .if ${ARCH} == "amd64" > > + CONFIGURE_ARGS+=--with-pic > > + .endif > > + > > post-patch: > > @${FIND} ${WRKSRC} -type f -name "*.[ch]" | ${XARGS} ${GREP} -l '' | \ > > ${XARGS} ${REINPLACE_CMD} -e 's|||g' > > Committed, thanks! > > Joe A pleasure. Your work on freebsd-gnome is greatly appreciated. Sean From owner-freebsd-amd64@FreeBSD.ORG Thu Jun 3 21:33:51 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 75C9B16A4CE for ; Thu, 3 Jun 2004 21:33:51 -0700 (PDT) Received: from mail.mcneil.com (rrcs-west-24-199-45-54.biz.rr.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 523DA43D46 for ; Thu, 3 Jun 2004 21:33:51 -0700 (PDT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 94352FD0D7 for ; Thu, 3 Jun 2004 21:33:49 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00677-07 for ; Thu, 3 Jun 2004 21:33:49 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 32465FD029 for ; Thu, 3 Jun 2004 21:33:49 -0700 (PDT) From: Sean McNeil To: freebsd-amd64@freebsd.org Content-Type: text/plain Message-Id: <1086323628.48282.23.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Thu, 03 Jun 2004 21:33:49 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com Subject: some broken ports? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jun 2004 04:33:51 -0000 Am I missing something? Is libtool suppose to handle this and isn't? I cannot get several ports to compile without adding the following snip of code to the Makefile for each: .if ${MACHINE_ARCH} == "amd64" CONFIGURE_ARGS+=--with-pic .endif So far these include: mail/evolution (has just been committed) multimedia/mpeg4ip There is an odd patch in gxine that I have to remove too: multimedia/gxine/files/patch-src::spidermonkey::jsprf.c Sean From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 4 08:34:54 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 73F3716A4CE for ; Fri, 4 Jun 2004 08:34:54 -0700 (PDT) Received: from mail.mcneil.com (rrcs-west-24-199-45-54.biz.rr.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C19F43D2D for ; Fri, 4 Jun 2004 08:34:52 -0700 (PDT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id E0212FD029 for ; Fri, 4 Jun 2004 08:34:37 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 23655-03 for ; Fri, 4 Jun 2004 08:34:37 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 810B0FD005 for ; Fri, 4 Jun 2004 08:34:37 -0700 (PDT) From: Sean McNeil To: freebsd-amd64@freebsd.org Content-Type: text/plain Message-Id: <1086363277.24158.3.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Fri, 04 Jun 2004 08:34:37 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com Subject: kerberos5/heimdal sig 11 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jun 2004 15:34:54 -0000 I am getting a sig 11 from within krb5_string_to_key_data_salt_opaque() when I do the following: kadmin -l init MCNEIL.COM Does anyone else have this issue or do I have some old cruft in my system that is causing this? I upgraded from i386. I've removed everything in /var/heimdal so I'm not sure what could be left over that would cause this. Sean From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 4 09:49:16 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF44F16A4CE for ; Fri, 4 Jun 2004 09:49:16 -0700 (PDT) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id A214F43D1D for ; Fri, 4 Jun 2004 09:49:16 -0700 (PDT) (envelope-from peter@evilpete.dyndns.org) Received: from fw.wemm.org (canning.wemm.org [192.203.228.65]) by canning.wemm.org (Postfix) with ESMTP id 2C1D42A7EA for ; Fri, 4 Jun 2004 09:49:02 -0700 (PDT) (envelope-from peter@overcee.wemm.org) Received: from overcee.wemm.org (overcee.wemm.org [10.0.0.3]) by fw.wemm.org (Postfix) with ESMTP id 838ECE27E for ; Fri, 4 Jun 2004 09:49:01 -0700 (PDT) (envelope-from peter@overcee.wemm.org) Received: from overcee.wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (8.12.11/8.12.11) with ESMTP id i54Gn1Ix099436; Fri, 4 Jun 2004 09:49:01 -0700 (PDT) (envelope-from peter@overcee.wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by overcee.wemm.org (8.12.11/8.12.11/Submit) id i54GmvMx099435; Fri, 4 Jun 2004 09:48:57 -0700 (PDT) (envelope-from peter) From: Peter Wemm To: freebsd-amd64@freebsd.org Date: Fri, 4 Jun 2004 09:48:56 -0700 User-Agent: KMail/1.6.1 References: <1086323628.48282.23.camel@server.mcneil.com> In-Reply-To: <1086323628.48282.23.camel@server.mcneil.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200406040948.57120.peter@wemm.org> cc: Sean McNeil Subject: Re: some broken ports? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jun 2004 16:49:16 -0000 On Thursday 03 June 2004 09:33 pm, Sean McNeil wrote: > Am I missing something? Is libtool suppose to handle this and isn't? > I cannot get several ports to compile without adding the following > snip of code to the Makefile for each: > > .if ${MACHINE_ARCH} == "amd64" > CONFIGURE_ARGS+=--with-pic > .endif I believe the problem is that libtool's test isn't adequate and it arrives at the conclusion that it is possible to use non-pic binaries in shared objects when in fact it just didn't test enough cases. I don't know my way around its internals well enough though. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 4 16:03:29 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DDDED16A4CF for ; Fri, 4 Jun 2004 16:03:29 -0700 (PDT) Received: from mail.mcneil.com (rrcs-west-24-199-45-54.biz.rr.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC1EC43D45 for ; Fri, 4 Jun 2004 16:03:29 -0700 (PDT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id D933EFD1CE for ; Fri, 4 Jun 2004 16:03:10 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00676-05 for ; Fri, 4 Jun 2004 16:03:10 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 580C2FD1C4 for ; Fri, 4 Jun 2004 16:03:10 -0700 (PDT) From: Sean McNeil To: freebsd-amd64@freebsd.org Content-Type: text/plain Message-Id: <1086390190.69872.2.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Fri, 04 Jun 2004 16:03:10 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com Subject: debugger that works? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jun 2004 23:03:30 -0000 Anyone have one? I've built a debugger from cvs as /usr/ports/devel/gdb6 doesn't point to a valid source. I get all kinds of junk in backtraces and attaching to a process doesn't work. Anyone have one that works better? I'm trying to do my best with assisting in tracking down issues with amd64, but without gdb I'm not sure how much I can help out. Cheers, Sean From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 4 17:23:03 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D6C4216A4CE for ; Fri, 4 Jun 2004 17:23:03 -0700 (PDT) Received: from ns1.xcllnt.net (209-128-86-226.BAYAREA.NET [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6837C43D1D for ; Fri, 4 Jun 2004 17:23:03 -0700 (PDT) (envelope-from marcel@xcllnt.net) Received: from dhcp50.pn.xcllnt.net (dhcp50.pn.xcllnt.net [192.168.4.250]) by ns1.xcllnt.net (8.12.11/8.12.11) with ESMTP id i550MW55037131; Fri, 4 Jun 2004 17:22:32 -0700 (PDT) (envelope-from marcel@piii.pn.xcllnt.net) Received: from dhcp50.pn.xcllnt.net (localhost [127.0.0.1]) i550MVrW000802; Fri, 4 Jun 2004 17:22:31 -0700 (PDT) (envelope-from marcel@dhcp50.pn.xcllnt.net) Received: (from marcel@localhost) by dhcp50.pn.xcllnt.net (8.12.11/8.12.11/Submit) id i550MTqQ000801; Fri, 4 Jun 2004 17:22:29 -0700 (PDT) (envelope-from marcel) Date: Fri, 4 Jun 2004 17:22:29 -0700 From: Marcel Moolenaar To: Sean McNeil Message-ID: <20040605002229.GA721@dhcp50.pn.xcllnt.net> References: <1086390190.69872.2.camel@server.mcneil.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1086390190.69872.2.camel@server.mcneil.com> User-Agent: Mutt/1.4.2.1i cc: freebsd-amd64@freebsd.org Subject: Re: debugger that works? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jun 2004 00:23:03 -0000 On Fri, Jun 04, 2004 at 04:03:10PM -0700, Sean McNeil wrote: > Anyone have one? Can you try http://people.freebsd.org/~marcel/gdb6.bin for me? -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 4 17:35:47 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2379716A4CE for ; Fri, 4 Jun 2004 17:35:47 -0700 (PDT) Received: from mail.mcneil.com (rrcs-west-24-199-45-54.biz.rr.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id EEDC543D39 for ; Fri, 4 Jun 2004 17:35:44 -0700 (PDT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 059CDFD1D5; Fri, 4 Jun 2004 17:35:14 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00676-07; Fri, 4 Jun 2004 17:35:12 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 932C7FD1D1; Fri, 4 Jun 2004 17:35:11 -0700 (PDT) From: Sean McNeil To: Marcel Moolenaar In-Reply-To: <20040605002229.GA721@dhcp50.pn.xcllnt.net> References: <1086390190.69872.2.camel@server.mcneil.com> <20040605002229.GA721@dhcp50.pn.xcllnt.net> Content-Type: text/plain Message-Id: <1086395709.34021.1.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Fri, 04 Jun 2004 17:35:09 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com cc: freebsd-amd64@freebsd.org Subject: Re: debugger that works? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jun 2004 00:35:47 -0000 On Fri, 2004-06-04 at 17:22, Marcel Moolenaar wrote: > On Fri, Jun 04, 2004 at 04:03:10PM -0700, Sean McNeil wrote: > > Anyone have one? > > Can you try http://people.freebsd.org/~marcel/gdb6.bin for me? Thanks, I downloaded it and placed it as /usr/bin/gdb. Then I played with epiphany until it died. Same thing - hangs when trying to attach to the crashed process. From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 4 18:03:15 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3904C16A4CE for ; Fri, 4 Jun 2004 18:03:15 -0700 (PDT) Received: from ns1.xcllnt.net (209-128-86-226.BAYAREA.NET [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0DAFA43D2F for ; Fri, 4 Jun 2004 18:03:15 -0700 (PDT) (envelope-from marcel@xcllnt.net) Received: from dhcp50.pn.xcllnt.net (dhcp50.pn.xcllnt.net [192.168.4.250]) by ns1.xcllnt.net (8.12.11/8.12.11) with ESMTP id i55135kN037233; Fri, 4 Jun 2004 18:03:05 -0700 (PDT) (envelope-from marcel@piii.pn.xcllnt.net) Received: from dhcp50.pn.xcllnt.net (localhost [127.0.0.1]) i55135RM000993; Fri, 4 Jun 2004 18:03:05 -0700 (PDT) (envelope-from marcel@dhcp50.pn.xcllnt.net) Received: (from marcel@localhost) by dhcp50.pn.xcllnt.net (8.12.11/8.12.11/Submit) id i55135Ys000992; Fri, 4 Jun 2004 18:03:05 -0700 (PDT) (envelope-from marcel) Date: Fri, 4 Jun 2004 18:03:05 -0700 From: Marcel Moolenaar To: Sean McNeil Message-ID: <20040605010305.GA835@dhcp50.pn.xcllnt.net> References: <1086390190.69872.2.camel@server.mcneil.com> <20040605002229.GA721@dhcp50.pn.xcllnt.net> <1086395709.34021.1.camel@server.mcneil.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1086395709.34021.1.camel@server.mcneil.com> User-Agent: Mutt/1.4.2.1i cc: freebsd-amd64@freebsd.org Subject: Re: debugger that works? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jun 2004 01:03:15 -0000 On Fri, Jun 04, 2004 at 05:35:09PM -0700, Sean McNeil wrote: > On Fri, 2004-06-04 at 17:22, Marcel Moolenaar wrote: > > On Fri, Jun 04, 2004 at 04:03:10PM -0700, Sean McNeil wrote: > > > Anyone have one? > > > > Can you try http://people.freebsd.org/~marcel/gdb6.bin for me? > > Thanks, > > I downloaded it and placed it as /usr/bin/gdb. Then I played with > epiphany until it died. Same thing - hangs when trying to attach to the > crashed process. The debugger also hangs on i386 and even without epiphany having died first. The problem here is that epiphany is threaded (KSE based) and we don't have debugger support for that yet. Are the backtraces any better? -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 4 18:48:05 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 369BE16A4CE; Fri, 4 Jun 2004 18:48:05 -0700 (PDT) Received: from mail.mcneil.com (rrcs-west-24-199-45-54.biz.rr.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 17D2243D46; Fri, 4 Jun 2004 18:48:03 -0700 (PDT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 68600FD1D6; Fri, 4 Jun 2004 18:47:32 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 18960-01; Fri, 4 Jun 2004 18:47:30 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 994C3FD1D5; Fri, 4 Jun 2004 18:47:29 -0700 (PDT) From: Sean McNeil To: freebsd-amd64@freebsd.org, freebsd-threads@freebsd.org Content-Type: text/plain Message-Id: <1086400049.19812.4.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Fri, 04 Jun 2004 18:47:29 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com Subject: All my amd64 problems appear to be KSE X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jun 2004 01:48:05 -0000 I just switched over to libc_r via. libmap.conf and I no longer get any mysterious crashes of applications in gnome. My gnome-terminals and everything else are just fine now. I'm wondering now if I can build db41 with the pthread library again. It shouldn't really be built with pthread as a dependency anyway, but it causes crashes in bash on amd64 with nss_ldap. I believe all the amd64 crashes to be related to signal handling. If there are any tests or additional things I can do to assist in fixing this please let me know. Sean From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 4 18:49:12 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7344C16A4CE for ; Fri, 4 Jun 2004 18:49:12 -0700 (PDT) Received: from mail.mcneil.com (rrcs-west-24-199-45-54.biz.rr.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6310D43D1F for ; Fri, 4 Jun 2004 18:49:12 -0700 (PDT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 7F53EFD1D6; Fri, 4 Jun 2004 18:48:54 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 19842-01; Fri, 4 Jun 2004 18:48:54 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 0358FFD1D5; Fri, 4 Jun 2004 18:48:54 -0700 (PDT) From: Sean McNeil To: Marcel Moolenaar In-Reply-To: <20040605010305.GA835@dhcp50.pn.xcllnt.net> References: <1086390190.69872.2.camel@server.mcneil.com> <20040605002229.GA721@dhcp50.pn.xcllnt.net> <1086395709.34021.1.camel@server.mcneil.com> <20040605010305.GA835@dhcp50.pn.xcllnt.net> Content-Type: text/plain Message-Id: <1086400133.19812.6.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Fri, 04 Jun 2004 18:48:54 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com cc: freebsd-amd64@freebsd.org Subject: Re: debugger that works? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jun 2004 01:49:12 -0000 On Fri, 2004-06-04 at 18:03, Marcel Moolenaar wrote: > On Fri, Jun 04, 2004 at 05:35:09PM -0700, Sean McNeil wrote: > > On Fri, 2004-06-04 at 17:22, Marcel Moolenaar wrote: > > > On Fri, Jun 04, 2004 at 04:03:10PM -0700, Sean McNeil wrote: > > > > Anyone have one? > > > > > > Can you try http://people.freebsd.org/~marcel/gdb6.bin for me? > > > > Thanks, > > > > I downloaded it and placed it as /usr/bin/gdb. Then I played with > > epiphany until it died. Same thing - hangs when trying to attach to the > > crashed process. > > The debugger also hangs on i386 and even without epiphany having > died first. The problem here is that epiphany is threaded (KSE based) > and we don't have debugger support for that yet. > > Are the backtraces any better? Backtraces are the same, but thanks to your comment I have tried running my system with libc_r instead of KSE. Everything seems to be working just fine now. Thanks, Sean From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 4 19:30:14 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EC9B716A4CE; Fri, 4 Jun 2004 19:30:13 -0700 (PDT) Received: from smtp01.syd.iprimus.net.au (smtp01.syd.iprimus.net.au [210.50.30.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 333F843D3F; Fri, 4 Jun 2004 19:30:13 -0700 (PDT) (envelope-from tim@robbins.dropbear.id.au) Received: from robbins.dropbear.id.au (210.50.249.37) by smtp01.syd.iprimus.net.au (7.0.024) id 40B7A0DA0021EC3F; Sat, 5 Jun 2004 12:30:07 +1000 Received: by robbins.dropbear.id.au (Postfix, from userid 1000) id 940B341D0; Sat, 5 Jun 2004 12:31:27 +1000 (EST) Date: Sat, 5 Jun 2004 12:31:27 +1000 From: Tim Robbins To: David Schultz Message-ID: <20040605023127.GA26469@cat.robbins.dropbear.id.au> References: <20040602064846.GA6124@VARK.homeunix.com> <20040603002015.GA14544@cat.robbins.dropbear.id.au> <20040603015315.GA739@VARK.homeunix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040603015315.GA739@VARK.homeunix.com> User-Agent: Mutt/1.4.1i cc: amd64@FreeBSD.ORG Subject: Re: Initial FP exception flags incorrect on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jun 2004 02:30:14 -0000 On Wed, Jun 02, 2004 at 06:53:15PM -0700, David Schultz wrote: > On Thu, Jun 03, 2004, Tim Robbins wrote: > > On Tue, Jun 01, 2004 at 11:48:46PM -0700, David Schultz wrote: > > > I discovered that new processes on amd64 have the inexact flag > > > raised by default, at least on sledge. However, all the sticky > > > flags should be clear initially. > > [...] > > > I don't have any amd64 hardware of my own to test kernel patches > > > on, but if I were to make a wild guess as to how to solve the > > > problem, it would be the following patch. I would appreciate it > > > if someone could address the problem, or at least let me know > > > whether my proposed fix works. > > > > > > Index: sys/amd64/amd64/fpu.c > > > =================================================================== > > > RCS file: /cvs/src/sys/amd64/amd64/fpu.c,v > > > retrieving revision 1.149 > > > diff -u -r1.149 fpu.c > > > --- fpu.c 5 Apr 2004 21:25:51 -0000 1.149 > > > +++ fpu.c 2 Jun 2004 06:08:34 -0000 > > > @@ -73,6 +73,7 @@ > > > #define fnstsw(addr) __asm __volatile("fnstsw %0" : "=m" (*(addr))) > > > #define fxrstor(addr) __asm("fxrstor %0" : : "m" (*(addr))) > > > #define fxsave(addr) __asm __volatile("fxsave %0" : "=m" (*(addr))) > > > +#define stmxcsr(addr) __asm("stmxcsr %0" : "=m" (*(addr))) > > > #define start_emulating() __asm("smsw %%ax; orb %0,%%al; lmsw %%ax" \ > > > : : "n" (CR0_TS) : "ax") > > > #define stop_emulating() __asm("clts") > > > @@ -119,6 +120,8 @@ > > > fninit(); > > > control = __INITIAL_FPUCW__; > > > fldcw(&control); > > > + control = __INITIAL_MXCSR__; > > > + stmxcsr(&control); > > > fxsave(&fpu_cleanstate); > > > start_emulating(); > > > fpu_cleanstate_ready = 1; > > > > This seems to cause a panic (trap 12) on startup. Shouldn't it be ldmxcsr > > instead? Changing that causes a different kind of panic (trap 9.) > > Oops, you're right. The other problem is probably that control is > a u_short, so garbage gets loaded into the upper 16 bits of the CSR. > Making 'control' a u_int should fix the problem, but the following > patch introduces a new variable to avoid relying on endianness > for the fldcw. Thanks, Tim! > > > Index: sys/amd64/amd64/fpu.c > =================================================================== > RCS file: /cvs/src/sys/amd64/amd64/fpu.c,v > retrieving revision 1.149 > diff -u -r1.149 fpu.c > --- sys/amd64/amd64/fpu.c 5 Apr 2004 21:25:51 -0000 1.149 > +++ sys/amd64/amd64/fpu.c 3 Jun 2004 01:48:23 -0000 > @@ -73,6 +73,7 @@ > #define fnstsw(addr) __asm __volatile("fnstsw %0" : "=m" (*(addr))) > #define fxrstor(addr) __asm("fxrstor %0" : : "m" (*(addr))) > #define fxsave(addr) __asm __volatile("fxsave %0" : "=m" (*(addr))) > +#define ldmxcsr(r) __asm __volatile("ldmxcsr %0" : : "m" (r)) > #define start_emulating() __asm("smsw %%ax; orb %0,%%al; lmsw %%ax" \ > : : "n" (CR0_TS) : "ax") > #define stop_emulating() __asm("clts") > @@ -111,6 +112,7 @@ > fpuinit(void) > { > register_t savecrit; > + u_int mxcsr; > u_short control; > > savecrit = intr_disable(); > @@ -119,6 +121,8 @@ > fninit(); > control = __INITIAL_FPUCW__; > fldcw(&control); > + mxcsr = __INITIAL_MXCSR__; > + ldmxcsr(mxcsr); > fxsave(&fpu_cleanstate); > start_emulating(); > fpu_cleanstate_ready = 1; Apologies for the late response -- the new patch no longer causes panics on startup, and gives the expected results with your test program (0x00.) It doesn't seem to break any applications, but I don't do anything numerically intensive (X, KDE, Mozilla, compiling.) Tim From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 4 20:13:27 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0B33016A4CE for ; Fri, 4 Jun 2004 20:13:27 -0700 (PDT) Received: from VARK.homeunix.com (ar59.lsanca2-4.27.98.47.lsanca2.dsl-verizon.net [4.27.98.47]) by mx1.FreeBSD.org (Postfix) with ESMTP id CBBCF43D1D for ; Fri, 4 Jun 2004 20:13:26 -0700 (PDT) (envelope-from das@FreeBSD.ORG) Received: from VARK.homeunix.com (localhost [127.0.0.1]) by VARK.homeunix.com (8.12.11/8.12.10) with ESMTP id i553D8Sl004189; Fri, 4 Jun 2004 20:13:08 -0700 (PDT) (envelope-from das@FreeBSD.ORG) Received: (from das@localhost) by VARK.homeunix.com (8.12.11/8.12.10/Submit) id i553D7CJ004188; Fri, 4 Jun 2004 20:13:07 -0700 (PDT) (envelope-from das@FreeBSD.ORG) Date: Fri, 4 Jun 2004 20:13:07 -0700 From: David Schultz To: Tim Robbins Message-ID: <20040605031307.GB4004@VARK.homeunix.com> References: <20040602064846.GA6124@VARK.homeunix.com> <20040603002015.GA14544@cat.robbins.dropbear.id.au> <20040603015315.GA739@VARK.homeunix.com> <20040605023127.GA26469@cat.robbins.dropbear.id.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040605023127.GA26469@cat.robbins.dropbear.id.au> cc: amd64@FreeBSD.ORG Subject: Re: Initial FP exception flags incorrect on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jun 2004 03:13:27 -0000 On Sat, Jun 05, 2004, Tim Robbins wrote: > Apologies for the late response -- the new patch no longer causes panics > on startup, and gives the expected results with your test program (0x00.) > It doesn't seem to break any applications, but I don't do anything > numerically intensive (X, KDE, Mozilla, compiling.) Great! Thanks, Tim. If nothing catastrophic happened under a normal workload, then resetting the CSR to its default value probably didn't break anything. I'll go ahead and commit the patch. From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 4 21:06:33 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EE78716A4CE; Fri, 4 Jun 2004 21:06:33 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D65643D48; Fri, 4 Jun 2004 21:06:33 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id i5546CtD016405; Sat, 5 Jun 2004 00:06:15 -0400 (EDT) Date: Sat, 5 Jun 2004 00:06:12 -0400 (EDT) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: Sean McNeil In-Reply-To: <1086400049.19812.4.camel@server.mcneil.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-amd64@freebsd.org cc: freebsd-threads@freebsd.org Subject: Re: All my amd64 problems appear to be KSE X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jun 2004 04:06:34 -0000 On Fri, 4 Jun 2004, Sean McNeil wrote: > I just switched over to libc_r via. libmap.conf and I no longer get any > mysterious crashes of applications in gnome. My gnome-terminals and > everything else are just fine now. How were you using libpthread? It's best to use libmap.conf to map everything to libpthread so that libc_r isn't pulled in by libraries still linked to it. -- Dan Eischen From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 4 21:21:38 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CA73E16A4CE; Fri, 4 Jun 2004 21:21:38 -0700 (PDT) Received: from mail.mcneil.com (rrcs-west-24-199-45-54.biz.rr.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9BF2343D55; Fri, 4 Jun 2004 21:21:36 -0700 (PDT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 9D584FD03A; Fri, 4 Jun 2004 21:20:54 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00677-03; Fri, 4 Jun 2004 21:20:54 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id EEC3BFD031; Fri, 4 Jun 2004 21:20:53 -0700 (PDT) From: Sean McNeil To: Daniel Eischen In-Reply-To: References: Content-Type: text/plain Message-Id: <1086409253.1525.11.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Fri, 04 Jun 2004 21:20:53 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com cc: freebsd-amd64@freebsd.org cc: freebsd-threads@freebsd.org Subject: Re: All my amd64 problems appear to be KSE X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jun 2004 04:21:38 -0000 On Fri, 2004-06-04 at 21:06, Daniel Eischen wrote: > On Fri, 4 Jun 2004, Sean McNeil wrote: > > > I just switched over to libc_r via. libmap.conf and I no longer get any > > mysterious crashes of applications in gnome. My gnome-terminals and > > everything else are just fine now. > > How were you using libpthread? It's best to use libmap.conf > to map everything to libpthread so that libc_r isn't pulled > in by libraries still linked to it. This is a completely rebuilt machine from a working i386 install that has tracked -current forever. There is absolutely nothing that is compiled and pointing to libc_r. I use to have libmap.conf point as follows: libpthread.so libpthread.so libpthread.so.1 libpthread.so.1 With this, gnome-terminal will crash constantly. I normally have 2 windows with 4 tabs each running. It crashes when I log in and they crash at odd times when I try to start a new one from either nautilus menu or panel button. With libmap.conf set to libpthread.so.1 libc_r.so.5 gnome-terminal works as it is suppose to. No crashes at all. Firefox is the only thing I have trouble with now - it crashes when I type in a character to the google search text widget. This was the behavior with kse before, so it is probably not thread related. libpthread is broken somewhere on amd64. Or it is possible that kse is uncovering an issue with something else. I frankly do not trust libreadline. It doesn't seem to work well with pthreads. I noticed several warnings when doing a buildworld in readline. But the bottom line is that gnome is practically unusable with all the crashes when using kse and appears quite stable with libc_r. This is with a system built entirely from -current as of today (Friday June 4). Updated ports as well. Cheers, Sean From owner-freebsd-amd64@FreeBSD.ORG Sat Jun 5 07:23:12 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 68D2916A4CE; Sat, 5 Jun 2004 07:23:12 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 22CF443D3F; Sat, 5 Jun 2004 07:23:12 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id i55EMwtD015302; Sat, 5 Jun 2004 10:23:01 -0400 (EDT) Date: Sat, 5 Jun 2004 10:22:58 -0400 (EDT) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: Sean McNeil In-Reply-To: <1086409253.1525.11.camel@server.mcneil.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-amd64@freebsd.org cc: freebsd-threads@freebsd.org Subject: Re: All my amd64 problems appear to be KSE X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jun 2004 14:23:12 -0000 On Fri, 4 Jun 2004, Sean McNeil wrote: > On Fri, 2004-06-04 at 21:06, Daniel Eischen wrote: > > On Fri, 4 Jun 2004, Sean McNeil wrote: > > > > > I just switched over to libc_r via. libmap.conf and I no longer get any > > > mysterious crashes of applications in gnome. My gnome-terminals and > > > everything else are just fine now. > > > > How were you using libpthread? It's best to use libmap.conf > > to map everything to libpthread so that libc_r isn't pulled > > in by libraries still linked to it. > > This is a completely rebuilt machine from a working i386 install that > has tracked -current forever. There is absolutely nothing that is > compiled and pointing to libc_r. Sorry, unless you have tried using libmap to map libc_r to libpthread, I don't trust that. -- Dan Eischen From owner-freebsd-amd64@FreeBSD.ORG Sat Jun 5 08:13:46 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2D0AD16A4CE; Sat, 5 Jun 2004 08:13:46 -0700 (PDT) Received: from smtp01.syd.iprimus.net.au (smtp01.syd.iprimus.net.au [210.50.30.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6296943D45; Sat, 5 Jun 2004 08:13:45 -0700 (PDT) (envelope-from tim@robbins.dropbear.id.au) Received: from robbins.dropbear.id.au (210.50.112.80) by smtp01.syd.iprimus.net.au (7.0.024) id 40B7A0DA0023E7C1; Sun, 6 Jun 2004 01:13:36 +1000 Received: by robbins.dropbear.id.au (Postfix, from userid 1000) id 18A3241D0; Sun, 6 Jun 2004 01:15:00 +1000 (EST) Date: Sun, 6 Jun 2004 01:15:00 +1000 From: Tim Robbins To: Daniel Eischen Message-ID: <20040605151500.GA29569@cat.robbins.dropbear.id.au> References: <1086409253.1525.11.camel@server.mcneil.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i cc: Sean McNeil cc: freebsd-amd64@freebsd.org cc: freebsd-threads@freebsd.org Subject: Re: All my amd64 problems appear to be KSE X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jun 2004 15:13:46 -0000 On Sat, Jun 05, 2004 at 10:22:58AM -0400, Daniel Eischen wrote: > On Fri, 4 Jun 2004, Sean McNeil wrote: > > > On Fri, 2004-06-04 at 21:06, Daniel Eischen wrote: > > > On Fri, 4 Jun 2004, Sean McNeil wrote: > > > > > > > I just switched over to libc_r via. libmap.conf and I no longer get any > > > > mysterious crashes of applications in gnome. My gnome-terminals and > > > > everything else are just fine now. > > > > > > How were you using libpthread? It's best to use libmap.conf > > > to map everything to libpthread so that libc_r isn't pulled > > > in by libraries still linked to it. > > > > This is a completely rebuilt machine from a working i386 install that > > has tracked -current forever. There is absolutely nothing that is > > compiled and pointing to libc_r. > > Sorry, unless you have tried using libmap to map libc_r to > libpthread, I don't trust that. I can corroborate what Sean is saying. There is definitely something wrong with KSE on amd64 (I haven't tried it on i386.) I've been chasing it down, on-and-off, for about a month, but have come up with nothing so far. gnome-terminal and xmms are two examples of applications that have gone from unusable to usable after changing from libpthread to libc_r. Mozilla may also be affected, but I'm less sure of that. The applications in question just mysteriously vanish, sometimes with signal 10 or 11, sometimes with no signal in the kernel log at all. Tim From owner-freebsd-amd64@FreeBSD.ORG Sat Jun 5 09:02:22 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 20A1616A4CE; Sat, 5 Jun 2004 09:02:22 -0700 (PDT) Received: from mail.mcneil.com (rrcs-west-24-199-45-54.biz.rr.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF2B143D3F; Sat, 5 Jun 2004 09:02:21 -0700 (PDT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 4E256FD1D8; Sat, 5 Jun 2004 09:02:21 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 06005-02; Sat, 5 Jun 2004 09:02:20 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 75BF6FD1D7; Sat, 5 Jun 2004 09:02:20 -0700 (PDT) From: Sean McNeil To: Daniel Eischen In-Reply-To: References: Content-Type: text/plain Message-Id: <1086451339.6274.18.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Sat, 05 Jun 2004 09:02:20 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com cc: freebsd-amd64@freebsd.org cc: freebsd-threads@freebsd.org Subject: Re: All my amd64 problems appear to be KSE X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jun 2004 16:02:22 -0000 On Sat, 2004-06-05 at 07:22, Daniel Eischen wrote: > On Fri, 4 Jun 2004, Sean McNeil wrote: > > > On Fri, 2004-06-04 at 21:06, Daniel Eischen wrote: > > > On Fri, 4 Jun 2004, Sean McNeil wrote: > > > > > > > I just switched over to libc_r via. libmap.conf and I no longer get any > > > > mysterious crashes of applications in gnome. My gnome-terminals and > > > > everything else are just fine now. > > > > > > How were you using libpthread? It's best to use libmap.conf > > > to map everything to libpthread so that libc_r isn't pulled > > > in by libraries still linked to it. > > > > This is a completely rebuilt machine from a working i386 install that > > has tracked -current forever. There is absolutely nothing that is > > compiled and pointing to libc_r. > > Sorry, unless you have tried using libmap to map libc_r to > libpthread, I don't trust that. I would have to say that is extremely myopic of you. Regardless of whether you trust me or not, it doesn't change what I have reported. kse is broken in some respect on amd64. For my own assurances, I have done the following: find / -name "*.so*" -exec ldd {} \; |& grep libc_r result was /usr/lib/libc_r.so.5: /usr/lib/libc_r.so: ldd: /usr/src/lib/compat/compat22/libc_r.so.3.0.bz2.uu: not a dynamic executableldd: /usr/src/lib/compat/compat3x.i386/libc_r.so.3.gz.uu: not a dynamic executable ldd: /usr/src/lib/compat/compat3x.i386/libc_r.so.4.gz.uu: not a dynamic executable ldd: /usr/src/lib/compat/compat4x.alpha/libc_r.so.4.bz2.uu: not a dynamic executable ldd: /usr/src/lib/compat/compat4x.i386/libc_r.so.4.bz2.uu: not a dynamic executable /usr/obj/usr/src/amd64/usr/lib/libc_r.so.5: /usr/obj/usr/src/amd64/usr/lib/libc_r.so: /usr/obj/usr/src/lib/libc_r/libc_r.so: /usr/obj/usr/src/lib/libc_r/libc_r.so.5: So as I stated earlier, there is absolutely nothing on my system that is compiled and pointing to libc_r. It is my opinion that it is always better to give a person the benefit of doubt regarding a claim. What I am looking for here is something constructive in a way of suggesting things I can do to assist in tracking down the problems I have seen. Can anyone give me ideas? I'm sort of stuck with this because 1) gdb doesn't work with attaching to a process that uses kse. This makes gnome's crash dialog and reporting mechanism non-functional. 2) I've tried --disable-crash-dialog when executing an application but that doesn't seem to have an effect. The crash dialog keeps getting in my way. I need some way to get these applications to dump core so I can take a look at a backtrace. Any help in accomplishing that would be highly appreciated. Hopefully it will help in resolving the issues with kse on amd64 as well. Cheers, Sean From owner-freebsd-amd64@FreeBSD.ORG Sat Jun 5 09:06:03 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5796216A4CE; Sat, 5 Jun 2004 09:06:03 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1306443D1F; Sat, 5 Jun 2004 09:06:03 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id i55G61tD009958; Sat, 5 Jun 2004 12:06:02 -0400 (EDT) Date: Sat, 5 Jun 2004 12:06:01 -0400 (EDT) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: Tim Robbins In-Reply-To: <20040605151500.GA29569@cat.robbins.dropbear.id.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Sean McNeil cc: freebsd-amd64@freebsd.org cc: freebsd-threads@freebsd.org Subject: Re: All my amd64 problems appear to be KSE X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jun 2004 16:06:03 -0000 On Sun, 6 Jun 2004, Tim Robbins wrote: > On Sat, Jun 05, 2004 at 10:22:58AM -0400, Daniel Eischen wrote: > > On Fri, 4 Jun 2004, Sean McNeil wrote: > > > > > On Fri, 2004-06-04 at 21:06, Daniel Eischen wrote: > > > > On Fri, 4 Jun 2004, Sean McNeil wrote: > > > > > > > > > I just switched over to libc_r via. libmap.conf and I no longer get any > > > > > mysterious crashes of applications in gnome. My gnome-terminals and > > > > > everything else are just fine now. > > > > > > > > How were you using libpthread? It's best to use libmap.conf > > > > to map everything to libpthread so that libc_r isn't pulled > > > > in by libraries still linked to it. > > > > > > This is a completely rebuilt machine from a working i386 install that > > > has tracked -current forever. There is absolutely nothing that is > > > compiled and pointing to libc_r. > > > > Sorry, unless you have tried using libmap to map libc_r to ^^^^^^^^^^^^^^^^^^^^^^^ > > libpthread, I don't trust that. ^^^^^^^^^^ ??? This is the first thing that I would ask anyone to try, and it's very simple to do. Noone (or do we now spell it as 'no_one' ;-)) has said, "yes, I've done that and it doesn't help". > I can corroborate what Sean is saying. There is definitely something wrong > with KSE on amd64 (I haven't tried it on i386.) I've been chasing it down, > on-and-off, for about a month, but have come up with nothing so far. > gnome-terminal and xmms are two examples of applications that have gone > from unusable to usable after changing from libpthread to libc_r. Mozilla > may also be affected, but I'm less sure of that. The applications in > question just mysteriously vanish, sometimes with signal 10 or 11, sometimes > with no signal in the kernel log at all. Is it something recent that broke? Last I knew, libpthread was working on amd64 with mozilla & kde. -- Dan Eischen From owner-freebsd-amd64@FreeBSD.ORG Sat Jun 5 09:13:18 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E90AB16A4CE; Sat, 5 Jun 2004 09:13:18 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96BDB43D1F; Sat, 5 Jun 2004 09:13:18 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id i55GD2tD011712; Sat, 5 Jun 2004 12:13:02 -0400 (EDT) Date: Sat, 5 Jun 2004 12:13:02 -0400 (EDT) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: Sean McNeil In-Reply-To: <1086451339.6274.18.camel@server.mcneil.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-amd64@freebsd.org cc: freebsd-threads@freebsd.org Subject: Re: All my amd64 problems appear to be KSE X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jun 2004 16:13:19 -0000 On Sat, 5 Jun 2004, Sean McNeil wrote: > On Sat, 2004-06-05 at 07:22, Daniel Eischen wrote: > > On Fri, 4 Jun 2004, Sean McNeil wrote: > > > > > On Fri, 2004-06-04 at 21:06, Daniel Eischen wrote: > > > > On Fri, 4 Jun 2004, Sean McNeil wrote: > > > > > > > > > I just switched over to libc_r via. libmap.conf and I no longer get any > > > > > mysterious crashes of applications in gnome. My gnome-terminals and > > > > > everything else are just fine now. > > > > > > > > How were you using libpthread? It's best to use libmap.conf > > > > to map everything to libpthread so that libc_r isn't pulled > > > > in by libraries still linked to it. > > > > > > This is a completely rebuilt machine from a working i386 install that > > > has tracked -current forever. There is absolutely nothing that is > > > compiled and pointing to libc_r. > > > > Sorry, unless you have tried using libmap to map libc_r to > > libpthread, I don't trust that. > > I would have to say that is extremely myopic of you. Regardless of > whether you trust me or not, it doesn't change what I have reported. > kse is broken in some respect on amd64. What I ask is very reasonable. You've already used libmap.conf to map libpthread.* to libc_r. Is it that hard for you to edit the file and try it the other way around? If you want help, you should be willing to answer very simple questions such as that. Is this Gnome-specific? Has anyone been using KDE successfully? -- Dan Eischen From owner-freebsd-amd64@FreeBSD.ORG Sat Jun 5 09:16:39 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0F43716A4CE; Sat, 5 Jun 2004 09:16:39 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id C1F5443D31; Sat, 5 Jun 2004 09:16:38 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id i55GGbtD012797; Sat, 5 Jun 2004 12:16:37 -0400 (EDT) Date: Sat, 5 Jun 2004 12:16:37 -0400 (EDT) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: Sean McNeil In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-amd64@freebsd.org cc: freebsd-threads@freebsd.org Subject: Re: All my amd64 problems appear to be KSE X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jun 2004 16:16:39 -0000 On Sat, 5 Jun 2004, Daniel Eischen wrote: > On Sat, 5 Jun 2004, Sean McNeil wrote: > > > > > I would have to say that is extremely myopic of you. Regardless of > > whether you trust me or not, it doesn't change what I have reported. > > kse is broken in some respect on amd64. > > What I ask is very reasonable. You've already used libmap.conf > to map libpthread.* to libc_r. Is it that hard for you to edit > the file and try it the other way around? If you want help, you > should be willing to answer very simple questions such as that. I would also make sure that libkse isn't being used (either remove it from your system or use libmap.conf). I would think that trying to use libc_r and libkse together would present the same sort of problem as using libpthread and libkse together, but just to be sure... -- Dan Eischen From owner-freebsd-amd64@FreeBSD.ORG Sat Jun 5 09:17:02 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 14EFE16A4CE; Sat, 5 Jun 2004 09:17:02 -0700 (PDT) Received: from mail.mcneil.com (rrcs-west-24-199-45-54.biz.rr.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id E857743D31; Sat, 5 Jun 2004 09:17:01 -0700 (PDT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id D2388FD1D8; Sat, 5 Jun 2004 09:16:59 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 06005-04; Sat, 5 Jun 2004 09:16:59 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id EA45CFD1D7; Sat, 5 Jun 2004 09:16:58 -0700 (PDT) From: Sean McNeil To: Daniel Eischen In-Reply-To: References: Content-Type: text/plain Message-Id: <1086452218.6274.28.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Sat, 05 Jun 2004 09:16:58 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com cc: Tim Robbins cc: freebsd-amd64@freebsd.org cc: freebsd-threads@freebsd.org Subject: Re: All my amd64 problems appear to be KSE X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jun 2004 16:17:02 -0000 On Sat, 2004-06-05 at 09:06, Daniel Eischen wrote: > On Sun, 6 Jun 2004, Tim Robbins wrote: > > > On Sat, Jun 05, 2004 at 10:22:58AM -0400, Daniel Eischen wrote: > > > On Fri, 4 Jun 2004, Sean McNeil wrote: > > > > > > > On Fri, 2004-06-04 at 21:06, Daniel Eischen wrote: > > > > > On Fri, 4 Jun 2004, Sean McNeil wrote: > > > > > > > > > > > I just switched over to libc_r via. libmap.conf and I no longer get any > > > > > > mysterious crashes of applications in gnome. My gnome-terminals and > > > > > > everything else are just fine now. > > > > > > > > > > How were you using libpthread? It's best to use libmap.conf > > > > > to map everything to libpthread so that libc_r isn't pulled > > > > > in by libraries still linked to it. > > > > > > > > This is a completely rebuilt machine from a working i386 install that > > > > has tracked -current forever. There is absolutely nothing that is > > > > compiled and pointing to libc_r. > > > > > > Sorry, unless you have tried using libmap to map libc_r to > ^^^^^^^^^^^^^^^^^^^^^^^ > > > libpthread, I don't trust that. > ^^^^^^^^^^ > > ??? > > This is the first thing that I would ask anyone to try, and it's > very simple to do. Noone (or do we now spell it as 'no_one' ;-)) > has said, "yes, I've done that and it doesn't help". I am 100% certain that I can. I must be no_one :) See my other email. I'm positive that since not a single shared object is using libc_r nor any application - I actually ran the find on all files after the email instead of just "*.so*" - adding a map of libc_r to libthread.so.1 would be a noop for me. > > I can corroborate what Sean is saying. There is definitely something wrong > > with KSE on amd64 (I haven't tried it on i386.) I've been chasing it down, > > on-and-off, for about a month, but have come up with nothing so far. > > gnome-terminal and xmms are two examples of applications that have gone > > from unusable to usable after changing from libpthread to libc_r. Mozilla > > may also be affected, but I'm less sure of that. The applications in > > question just mysteriously vanish, sometimes with signal 10 or 11, sometimes > > with no signal in the kernel log at all. > > Is it something recent that broke? Last I knew, libpthread was working > on amd64 with mozilla & kde. That I cannot tell you. I bought my amd64 about a week ago and it hasn't worked with kse. I've only managed to get everything converted about 3 days ago, so I don't have much history. I would prefer not reverting to a release to test, but that is an option if no other means of tracking down the problem presents itself. Sean From owner-freebsd-amd64@FreeBSD.ORG Sat Jun 5 09:30:16 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0B31916A4CE; Sat, 5 Jun 2004 09:30:16 -0700 (PDT) Received: from smtp01.syd.iprimus.net.au (smtp01.syd.iprimus.net.au [210.50.30.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 79C1243D2F; Sat, 5 Jun 2004 09:30:15 -0700 (PDT) (envelope-from tim@robbins.dropbear.id.au) Received: from robbins.dropbear.id.au (210.50.112.80) by smtp01.syd.iprimus.net.au (7.0.024) id 40B7A0DA0024323F; Sun, 6 Jun 2004 02:29:57 +1000 Received: by robbins.dropbear.id.au (Postfix, from userid 1000) id 1A09241D0; Sun, 6 Jun 2004 02:31:23 +1000 (EST) Date: Sun, 6 Jun 2004 02:31:23 +1000 From: Tim Robbins To: Daniel Eischen Message-ID: <20040605163123.GA29935@cat.robbins.dropbear.id.au> References: <20040605151500.GA29569@cat.robbins.dropbear.id.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i cc: Sean McNeil cc: freebsd-amd64@freebsd.org cc: freebsd-threads@freebsd.org Subject: Re: All my amd64 problems appear to be KSE X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jun 2004 16:30:16 -0000 On Sat, Jun 05, 2004 at 12:06:01PM -0400, Daniel Eischen wrote: > On Sun, 6 Jun 2004, Tim Robbins wrote: > > > On Sat, Jun 05, 2004 at 10:22:58AM -0400, Daniel Eischen wrote: > > > On Fri, 4 Jun 2004, Sean McNeil wrote: > > > > > > > On Fri, 2004-06-04 at 21:06, Daniel Eischen wrote: > > > > > On Fri, 4 Jun 2004, Sean McNeil wrote: > > > > > > > > > > > I just switched over to libc_r via. libmap.conf and I no longer get any > > > > > > mysterious crashes of applications in gnome. My gnome-terminals and > > > > > > everything else are just fine now. > > > > > > > > > > How were you using libpthread? It's best to use libmap.conf > > > > > to map everything to libpthread so that libc_r isn't pulled > > > > > in by libraries still linked to it. > > > > > > > > This is a completely rebuilt machine from a working i386 install that > > > > has tracked -current forever. There is absolutely nothing that is > > > > compiled and pointing to libc_r. > > > > > > Sorry, unless you have tried using libmap to map libc_r to > ^^^^^^^^^^^^^^^^^^^^^^^ > > > libpthread, I don't trust that. > ^^^^^^^^^^ > > ??? > > This is the first thing that I would ask anyone to try, and it's > very simple to do. Noone (or do we now spell it as 'no_one' ;-)) > has said, "yes, I've done that and it doesn't help". > > > I can corroborate what Sean is saying. There is definitely something wrong > > with KSE on amd64 (I haven't tried it on i386.) I've been chasing it down, > > on-and-off, for about a month, but have come up with nothing so far. > > gnome-terminal and xmms are two examples of applications that have gone > > from unusable to usable after changing from libpthread to libc_r. Mozilla > > may also be affected, but I'm less sure of that. The applications in > > question just mysteriously vanish, sometimes with signal 10 or 11, sometimes > > with no signal in the kernel log at all. > > Is it something recent that broke? Last I knew, libpthread was working > on amd64 with mozilla & kde. KDE works flawlessly. Mozilla almost works, but suffers from the "mysterious vanishing" I mentioned. If you want to reproduce the problems, either: (a) Fire up gnome-terminal, open a few new tabs, close them again, repeat until it crashes. It often takes only 2-3 invocations of "Open Tab" to make it happen. (b) Load a handful of MP3 files into XMMS, click the next/previous track buttons once every few seconds until it crashes. Everything seems to work fine if I build libpthread with SYSTEM_SCOPE_ONLY (at least it hasn't crashed so far.) My current guess is that there's a bug in context manipulation or signals. I initially thought we weren't saving enough FPU context in _amd64_save_context, but adding an fxsave in there didn't help. Tim From owner-freebsd-amd64@FreeBSD.ORG Sat Jun 5 09:33:38 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F317016A4CE; Sat, 5 Jun 2004 09:33:37 -0700 (PDT) Received: from mail.mcneil.com (rrcs-west-24-199-45-54.biz.rr.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id DBCE143D49; Sat, 5 Jun 2004 09:33:37 -0700 (PDT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 18D5FFD1D6; Sat, 5 Jun 2004 09:33:33 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 06189-05; Sat, 5 Jun 2004 09:33:32 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 97352FD1D5; Sat, 5 Jun 2004 09:33:32 -0700 (PDT) From: Sean McNeil To: Daniel Eischen In-Reply-To: References: Content-Type: text/plain Message-Id: <1086453212.96822.10.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Sat, 05 Jun 2004 09:33:32 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com cc: freebsd-amd64@freebsd.org cc: freebsd-threads@freebsd.org Subject: Re: All my amd64 problems appear to be KSE X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jun 2004 16:33:38 -0000 On Sat, 2004-06-05 at 09:16, Daniel Eischen wrote: > On Sat, 5 Jun 2004, Daniel Eischen wrote: > > > On Sat, 5 Jun 2004, Sean McNeil wrote: > > > > > > > > I would have to say that is extremely myopic of you. Regardless of > > > whether you trust me or not, it doesn't change what I have reported. > > > kse is broken in some respect on amd64. > > > > What I ask is very reasonable. You've already used libmap.conf > > to map libpthread.* to libc_r. Is it that hard for you to edit > > the file and try it the other way around? If you want help, you > > should be willing to answer very simple questions such as that. > > I would also make sure that libkse isn't being used (either > remove it from your system or use libmap.conf). I would think > that trying to use libc_r and libkse together would present > the same sort of problem as using libpthread and libkse > together, but just to be sure... There hasn't been a libkse on my system in a very long time. Just to make sure, I have searched the whole computer and it was not found. Also, I have done the libmap.conf of libc_r: libc_r.so.5 libpthread.so.1 libc_r.so libpthread.so.1 I can now claim that I am no_one without a doubt. I got the same failures as before. With regards to gnome-specific or if KDE has the same issue, I cannot answer. I do not use KDE. It would appear to be gnome-specific (gtk-specific?). Emacs has never given me any problems, but neither has nautilus, the panel, or a number of other gnome applications. For the moment, I highly suspect this is a pthread/readline interaction causing the crashes. Please let me know what I can do to help here. Sean From owner-freebsd-amd64@FreeBSD.ORG Sat Jun 5 09:34:09 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AD81F16A4CE; Sat, 5 Jun 2004 09:34:09 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4DECE43D2D; Sat, 5 Jun 2004 09:34:09 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id i55GY4tD017771; Sat, 5 Jun 2004 12:34:04 -0400 (EDT) Date: Sat, 5 Jun 2004 12:34:04 -0400 (EDT) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: Sean McNeil In-Reply-To: <1086452218.6274.28.camel@server.mcneil.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Tim Robbins cc: freebsd-amd64@freebsd.org cc: freebsd-threads@freebsd.org Subject: Re: All my amd64 problems appear to be KSE X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jun 2004 16:34:09 -0000 On Sat, 5 Jun 2004, Sean McNeil wrote: > On Sat, 2004-06-05 at 09:06, Daniel Eischen wrote: > > > > Is it something recent that broke? Last I knew, libpthread was working > > on amd64 with mozilla & kde. > > That I cannot tell you. I bought my amd64 about a week ago and it > hasn't worked with kse. I've only managed to get everything converted > about 3 days ago, so I don't have much history. I would prefer not > reverting to a release to test, but that is an option if no other means > of tracking down the problem presents itself. You don't need to revert to a release, just install KDE and see if you have similar problems. I thought that peter was running KDE and mozilla without any problems like this. -- Dan Eischen From owner-freebsd-amd64@FreeBSD.ORG Sat Jun 5 09:40:03 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C226916A4CE; Sat, 5 Jun 2004 09:40:03 -0700 (PDT) Received: from mail.mcneil.com (rrcs-west-24-199-45-54.biz.rr.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB63643D41; Sat, 5 Jun 2004 09:40:01 -0700 (PDT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 744C3FD1D6; Sat, 5 Jun 2004 09:40:01 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 06005-07; Sat, 5 Jun 2004 09:40:01 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id F301DFD084; Sat, 5 Jun 2004 09:40:00 -0700 (PDT) From: Sean McNeil To: Tim Robbins In-Reply-To: <20040605163123.GA29935@cat.robbins.dropbear.id.au> References: <20040605151500.GA29569@cat.robbins.dropbear.id.au> <20040605163123.GA29935@cat.robbins.dropbear.id.au> Content-Type: text/plain Message-Id: <1086453600.96822.16.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Sat, 05 Jun 2004 09:40:00 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com cc: freebsd-threads@freebsd.org cc: freebsd-amd64@freebsd.org cc: Daniel Eischen Subject: Re: All my amd64 problems appear to be KSE X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jun 2004 16:40:03 -0000 On Sat, 2004-06-05 at 09:31, Tim Robbins wrote: > Everything seems to work fine if I build libpthread with SYSTEM_SCOPE_ONLY > (at least it hasn't crashed so far.) My current guess is that there's a > bug in context manipulation or signals. I initially thought we weren't > saving enough FPU context in _amd64_save_context, but adding an fxsave > in there didn't help. I see a problem with bash and signals too when libpthread is involved. It would core dump when I resize a window. I use nss_ldap and it was pulling in pthread through db41. I solved my issue by rebuilding db41 to eliminate pthread from the libdb41.so.1. Perhaps tracing this down would be useful? Sean From owner-freebsd-amd64@FreeBSD.ORG Sat Jun 5 09:46:21 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 67B9516A4CE; Sat, 5 Jun 2004 09:46:21 -0700 (PDT) Received: from mail.mcneil.com (rrcs-west-24-199-45-54.biz.rr.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 47F4143D5C; Sat, 5 Jun 2004 09:46:21 -0700 (PDT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 77034FD1D6; Sat, 5 Jun 2004 09:46:20 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 06189-07; Sat, 5 Jun 2004 09:46:20 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id D9B41FD020; Sat, 5 Jun 2004 09:46:19 -0700 (PDT) From: Sean McNeil To: Tim Robbins In-Reply-To: <1086453600.96822.16.camel@server.mcneil.com> References: <20040605151500.GA29569@cat.robbins.dropbear.id.au> <20040605163123.GA29935@cat.robbins.dropbear.id.au> <1086453600.96822.16.camel@server.mcneil.com> Content-Type: text/plain Message-Id: <1086453979.18813.0.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Sat, 05 Jun 2004 09:46:19 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com cc: freebsd-threads@freebsd.org cc: freebsd-amd64@freebsd.org cc: Daniel Eischen Subject: Re: All my amd64 problems appear to be KSE X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jun 2004 16:46:21 -0000 On Sat, 2004-06-05 at 09:40, Sean McNeil wrote: > On Sat, 2004-06-05 at 09:31, Tim Robbins wrote: > > > Everything seems to work fine if I build libpthread with SYSTEM_SCOPE_ONLY > > (at least it hasn't crashed so far.) My current guess is that there's a > > bug in context manipulation or signals. I initially thought we weren't > > saving enough FPU context in _amd64_save_context, but adding an fxsave > > in there didn't help. > > I see a problem with bash and signals too when libpthread is involved. > It would core dump when I resize a window. I use nss_ldap and it was > pulling in pthread through db41. I solved my issue by rebuilding db41 > to eliminate pthread from the libdb41.so.1. Perhaps tracing this down > would be useful? resize of bash causes error like this: #0 _thr_sig_handler (sig=28, info=0x100, ucp=0x201701904) at /usr/src/lib/libpthread/thread/thr_sig.c:373 #1 0x00000002006ae9b0 in _rl_savestring () from /lib/libreadline.so.4 #2 #3 0x0000000200a822ec in read () from /lib/libc.so.5 #4 0x00000002006ab113 in rl_getc () from /lib/libreadline.so.4 #5 0x00000002006ab0c9 in rl_read_key () from /lib/libreadline.so.4 #6 0x00000002006bdeb7 in readline_internal_char () from /lib/libreadline.so.4 #7 0x00000002006be045 in readline_internal_char () from /lib/libreadline.so.4 #8 0x00000002006be060 in readline_internal_char () from /lib/libreadline.so.4 #9 0x00000002006bdc1e in readline () from /lib/libreadline.so.4 #10 0x0000000000415072 in yy_readline_get () at /usr/homes/chet/src/bash/src/parse.y:1108 #11 0x0000000000414fde in yy_getc () at /usr/homes/chet/src/bash/src/parse.y:1042 #12 0x0000000000415885 in shell_getc (remove_quoted_newline=1) at /usr/homes/chet/src/bash/src/parse.y:1803 #13 0x000000000041633e in read_token (command=0) at /usr/homes/chet/src/bash/src/parse.y:2414 #14 0x0000000000415e22 in yylex () at /usr/homes/chet/src/bash/src/parse.y:2084 #15 0x0000000000413b1a in yyparse () at /usr/local/share/bison/bison.simple:573 #16 0x00000000004138ab in parse_command () at eval.c:217 #17 0x000000000041395b in read_command () at eval.c:261 From owner-freebsd-amd64@FreeBSD.ORG Sat Jun 5 09:51:33 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B196716A4CE; Sat, 5 Jun 2004 09:51:33 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7025043D5D; Sat, 5 Jun 2004 09:51:33 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id i55GpMtD022725; Sat, 5 Jun 2004 12:51:22 -0400 (EDT) Date: Sat, 5 Jun 2004 12:51:22 -0400 (EDT) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: Tim Robbins In-Reply-To: <20040605163123.GA29935@cat.robbins.dropbear.id.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Sean McNeil cc: freebsd-amd64@freebsd.org cc: freebsd-threads@freebsd.org Subject: Re: All my amd64 problems appear to be KSE X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jun 2004 16:51:33 -0000 On Sun, 6 Jun 2004, Tim Robbins wrote: > On Sat, Jun 05, 2004 at 12:06:01PM -0400, Daniel Eischen wrote: > > > > Is it something recent that broke? Last I knew, libpthread was working > > on amd64 with mozilla & kde. > > KDE works flawlessly. Mozilla almost works, but suffers from the "mysterious > vanishing" I mentioned. > > If you want to reproduce the problems, either: > (a) Fire up gnome-terminal, open a few new tabs, close them again, repeat > until it crashes. It often takes only 2-3 invocations of "Open Tab" > to make it happen. > (b) Load a handful of MP3 files into XMMS, click the next/previous > track buttons once every few seconds until it crashes. > > Everything seems to work fine if I build libpthread with SYSTEM_SCOPE_ONLY > (at least it hasn't crashed so far.) My current guess is that there's a > bug in context manipulation or signals. I initially thought we weren't > saving enough FPU context in _amd64_save_context, but adding an fxsave > in there didn't help. If KDE & mozilla work, then context switching would work (unless they are specifically creating system-scope threads, but I don't think that is the case). I just ran a simple test case on sledge that created a few cpu bound threads doing FPU operations and it didn't crash. -- Dan Eischen From owner-freebsd-amd64@FreeBSD.ORG Sat Jun 5 09:57:58 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 110D316A4CE; Sat, 5 Jun 2004 09:57:58 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2FCD43D41; Sat, 5 Jun 2004 09:57:57 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id i55GvetD024322; Sat, 5 Jun 2004 12:57:40 -0400 (EDT) Date: Sat, 5 Jun 2004 12:57:40 -0400 (EDT) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: Sean McNeil In-Reply-To: <1086453212.96822.10.camel@server.mcneil.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-amd64@freebsd.org cc: freebsd-threads@freebsd.org Subject: Re: All my amd64 problems appear to be KSE X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jun 2004 16:57:58 -0000 On Sat, 5 Jun 2004, Sean McNeil wrote: > On Sat, 2004-06-05 at 09:16, Daniel Eischen wrote: > > > > I would also make sure that libkse isn't being used (either > > remove it from your system or use libmap.conf). I would think > > that trying to use libc_r and libkse together would present > > the same sort of problem as using libpthread and libkse > > together, but just to be sure... > > There hasn't been a libkse on my system in a very long time. Just to > make sure, I have searched the whole computer and it was not found. > Also, I have done the libmap.conf of libc_r: > > libc_r.so.5 libpthread.so.1 > libc_r.so libpthread.so.1 > > I can now claim that I am no_one without a doubt. I got the same > failures as before. > > With regards to gnome-specific or if KDE has the same issue, I cannot > answer. I do not use KDE. It would appear to be gnome-specific > (gtk-specific?). Emacs has never given me any problems, but neither has That includes glib also, right? > nautilus, the panel, or a number of other gnome applications. > > For the moment, I highly suspect this is a pthread/readline interaction > causing the crashes. Why do you suspect that? -- Dan Eischen From owner-freebsd-amd64@FreeBSD.ORG Sat Jun 5 10:04:39 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3890B16A4CE; Sat, 5 Jun 2004 10:04:39 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id EAD4B43D3F; Sat, 5 Jun 2004 10:04:38 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id i55H4btD026427; Sat, 5 Jun 2004 13:04:37 -0400 (EDT) Date: Sat, 5 Jun 2004 13:04:37 -0400 (EDT) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: Sean McNeil In-Reply-To: <1086453600.96822.16.camel@server.mcneil.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Tim Robbins cc: freebsd-amd64@freebsd.org cc: freebsd-threads@freebsd.org Subject: Re: All my amd64 problems appear to be KSE X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jun 2004 17:04:39 -0000 On Sat, 5 Jun 2004, Sean McNeil wrote: > On Sat, 2004-06-05 at 09:31, Tim Robbins wrote: > > > Everything seems to work fine if I build libpthread with SYSTEM_SCOPE_ONLY > > (at least it hasn't crashed so far.) My current guess is that there's a > > bug in context manipulation or signals. I initially thought we weren't > > saving enough FPU context in _amd64_save_context, but adding an fxsave > > in there didn't help. > > I see a problem with bash and signals too when libpthread is involved. > It would core dump when I resize a window. I use nss_ldap and it was > pulling in pthread through db41. I solved my issue by rebuilding db41 > to eliminate pthread from the libdb41.so.1. Perhaps tracing this down > would be useful? Isn't that a known problem? You can't dynamically load libpthread then unload it, which is what nss_ldap was doing. I thought that was fixed so that libpthread wasn't pulled in. It could be possible that something is trying to dlopen() a library that requires libpthread, and libpthread is loaded then unloaded. You can't do that because it'll screw up libc. One way around it is to build all your shared libraries with -pthread which will avoid linking to libpthread (-pthread is a noop when building shared libraries). You should be able to safely set PTHREAD_LIBS to -pthread instead of -lpthread, just keep an eye out for anything that manually brings in -lpthread. -- Dan Eischen From owner-freebsd-amd64@FreeBSD.ORG Sat Jun 5 10:11:57 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4459E16A4CE; Sat, 5 Jun 2004 10:11:57 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 02AC943D48; Sat, 5 Jun 2004 10:11:57 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id i55HButD028509; Sat, 5 Jun 2004 13:11:56 -0400 (EDT) Date: Sat, 5 Jun 2004 13:11:56 -0400 (EDT) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: Sean McNeil In-Reply-To: <1086453979.18813.0.camel@server.mcneil.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Tim Robbins cc: freebsd-amd64@freebsd.org cc: freebsd-threads@freebsd.org Subject: Re: All my amd64 problems appear to be KSE X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jun 2004 17:11:57 -0000 On Sat, 5 Jun 2004, Sean McNeil wrote: > On Sat, 2004-06-05 at 09:40, Sean McNeil wrote: > > On Sat, 2004-06-05 at 09:31, Tim Robbins wrote: > > > > > Everything seems to work fine if I build libpthread with SYSTEM_SCOPE_ONLY > > > (at least it hasn't crashed so far.) My current guess is that there's a > > > bug in context manipulation or signals. I initially thought we weren't > > > saving enough FPU context in _amd64_save_context, but adding an fxsave > > > in there didn't help. > > > > I see a problem with bash and signals too when libpthread is involved. > > It would core dump when I resize a window. I use nss_ldap and it was > > pulling in pthread through db41. I solved my issue by rebuilding db41 > > to eliminate pthread from the libdb41.so.1. Perhaps tracing this down > > would be useful? > > resize of bash causes error like this: > > #0 _thr_sig_handler (sig=28, info=0x100, ucp=0x201701904) > at /usr/src/lib/libpthread/thread/thr_sig.c:373 > #1 0x00000002006ae9b0 in _rl_savestring () from /lib/libreadline.so.4 > #2 > #3 0x0000000200a822ec in read () from /lib/libc.so.5 > #4 0x00000002006ab113 in rl_getc () from /lib/libreadline.so.4 > #5 0x00000002006ab0c9 in rl_read_key () from /lib/libreadline.so.4 > #6 0x00000002006bdeb7 in readline_internal_char () from > /lib/libreadline.so.4 That all looks fine, but bash isn't threaded is it? -- Dan Eischen From owner-freebsd-amd64@FreeBSD.ORG Sat Jun 5 10:16:14 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 64F4916A4CE; Sat, 5 Jun 2004 10:16:14 -0700 (PDT) Received: from mail.mcneil.com (rrcs-west-24-199-45-54.biz.rr.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C00743D3F; Sat, 5 Jun 2004 10:16:12 -0700 (PDT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 9A50FFD1D5; Sat, 5 Jun 2004 10:16:09 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 06005-10; Sat, 5 Jun 2004 10:16:09 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 1E23BFD084; Sat, 5 Jun 2004 10:16:09 -0700 (PDT) From: Sean McNeil To: Daniel Eischen In-Reply-To: References: Content-Type: text/plain Message-Id: <1086455768.18813.12.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Sat, 05 Jun 2004 10:16:08 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com cc: Tim Robbins cc: freebsd-amd64@freebsd.org cc: freebsd-threads@freebsd.org Subject: Re: All my amd64 problems appear to be KSE X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jun 2004 17:16:14 -0000 On Sat, 2004-06-05 at 10:04, Daniel Eischen wrote: > On Sat, 5 Jun 2004, Sean McNeil wrote: > > > On Sat, 2004-06-05 at 09:31, Tim Robbins wrote: > > > > > Everything seems to work fine if I build libpthread with SYSTEM_SCOPE_ONLY > > > (at least it hasn't crashed so far.) My current guess is that there's a > > > bug in context manipulation or signals. I initially thought we weren't > > > saving enough FPU context in _amd64_save_context, but adding an fxsave > > > in there didn't help. > > > > I see a problem with bash and signals too when libpthread is involved. > > It would core dump when I resize a window. I use nss_ldap and it was > > pulling in pthread through db41. I solved my issue by rebuilding db41 > > to eliminate pthread from the libdb41.so.1. Perhaps tracing this down > > would be useful? > > Isn't that a known problem? You can't dynamically load libpthread > then unload it, which is what nss_ldap was doing. I thought that > was fixed so that libpthread wasn't pulled in. > > It could be possible that something is trying to dlopen() a library > that requires libpthread, and libpthread is loaded then unloaded. > You can't do that because it'll screw up libc. > > One way around it is to build all your shared libraries with -pthread > which will avoid linking to libpthread (-pthread is a noop when building > shared libraries). You should be able to safely set PTHREAD_LIBS to > -pthread instead of -lpthread, just keep an eye out for anything that > manually brings in -lpthread. Yes, this is a known problem. I worked on fixing at least one of the issues with that. The end result is that there is no easy way do handle these cases. That is why I ended up removing pthread from db41. It isn't correct. I felt, though, that the issues with gnome may be related to the bash one as this exact same setup works with i386 and doesn't with amd64. Looking at libreadline now I see there is an error: (gdb) bt #0 _thr_sig_handler (sig=28, info=0x100, ucp=0x201701904) at /usr/src/lib/libpthread/thread/thr_sig.c:373 #1 0x00000002006aea90 in rl_sigwinch_handler (sig=28) at /usr/src/contrib/libreadline/signals.c:202 #2 You will see that libreadline invokes the handler as: 202 (*oh) (sig); From owner-freebsd-amd64@FreeBSD.ORG Sat Jun 5 10:18:43 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A882E16A4CE; Sat, 5 Jun 2004 10:18:43 -0700 (PDT) Received: from mail.mcneil.com (rrcs-west-24-199-45-54.biz.rr.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 911E943D41; Sat, 5 Jun 2004 10:18:43 -0700 (PDT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 4D738FD1D5; Sat, 5 Jun 2004 10:18:43 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 06189-10; Sat, 5 Jun 2004 10:18:43 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id C58EFFD084; Sat, 5 Jun 2004 10:18:42 -0700 (PDT) From: Sean McNeil To: Daniel Eischen In-Reply-To: References: Content-Type: text/plain Message-Id: <1086455922.18813.15.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Sat, 05 Jun 2004 10:18:42 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com cc: Tim Robbins cc: freebsd-amd64@freebsd.org cc: freebsd-threads@freebsd.org Subject: Re: All my amd64 problems appear to be KSE X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jun 2004 17:18:43 -0000 On Sat, 2004-06-05 at 10:11, Daniel Eischen wrote: > On Sat, 5 Jun 2004, Sean McNeil wrote: > > > On Sat, 2004-06-05 at 09:40, Sean McNeil wrote: > > > On Sat, 2004-06-05 at 09:31, Tim Robbins wrote: > > > > > > > Everything seems to work fine if I build libpthread with SYSTEM_SCOPE_ONLY > > > > (at least it hasn't crashed so far.) My current guess is that there's a > > > > bug in context manipulation or signals. I initially thought we weren't > > > > saving enough FPU context in _amd64_save_context, but adding an fxsave > > > > in there didn't help. > > > > > > I see a problem with bash and signals too when libpthread is involved. > > > It would core dump when I resize a window. I use nss_ldap and it was > > > pulling in pthread through db41. I solved my issue by rebuilding db41 > > > to eliminate pthread from the libdb41.so.1. Perhaps tracing this down > > > would be useful? > > > > resize of bash causes error like this: > > > > #0 _thr_sig_handler (sig=28, info=0x100, ucp=0x201701904) > > at /usr/src/lib/libpthread/thread/thr_sig.c:373 > > #1 0x00000002006ae9b0 in _rl_savestring () from /lib/libreadline.so.4 > > #2 > > #3 0x0000000200a822ec in read () from /lib/libc.so.5 > > #4 0x00000002006ab113 in rl_getc () from /lib/libreadline.so.4 > > #5 0x00000002006ab0c9 in rl_read_key () from /lib/libreadline.so.4 > > #6 0x00000002006bdeb7 in readline_internal_char () from > > /lib/libreadline.so.4 > > That all looks fine, but bash isn't threaded is it? bash isn't naturally threaded. I rebuilt db41 to its default of linking with pthread. This caused threading to be pulled in. Look again, info and ucp are garbage. It core dumps when it tries to dereference info. From owner-freebsd-amd64@FreeBSD.ORG Sat Jun 5 11:03:41 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1034B16A4CE; Sat, 5 Jun 2004 11:03:41 -0700 (PDT) Received: from mail.mcneil.com (rrcs-west-24-199-45-54.biz.rr.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id EAE0443D31; Sat, 5 Jun 2004 11:03:40 -0700 (PDT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 6B0A4FD1D6; Sat, 5 Jun 2004 11:03:28 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 19651-01; Sat, 5 Jun 2004 11:03:28 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id CC21CFD084; Sat, 5 Jun 2004 11:03:27 -0700 (PDT) From: Sean McNeil To: Daniel Eischen In-Reply-To: References: Content-Type: text/plain Message-Id: <1086458607.18813.37.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Sat, 05 Jun 2004 11:03:27 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com cc: freebsd-amd64@freebsd.org cc: freebsd-threads@freebsd.org Subject: Re: All my amd64 problems appear to be KSE X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jun 2004 18:03:41 -0000 On Sat, 2004-06-05 at 09:57, Daniel Eischen wrote: > On Sat, 5 Jun 2004, Sean McNeil wrote: > > > On Sat, 2004-06-05 at 09:16, Daniel Eischen wrote: > > > > > > I would also make sure that libkse isn't being used (either > > > remove it from your system or use libmap.conf). I would think > > > that trying to use libc_r and libkse together would present > > > the same sort of problem as using libpthread and libkse > > > together, but just to be sure... > > > > There hasn't been a libkse on my system in a very long time. Just to > > make sure, I have searched the whole computer and it was not found. > > Also, I have done the libmap.conf of libc_r: > > > > libc_r.so.5 libpthread.so.1 > > libc_r.so libpthread.so.1 > > > > I can now claim that I am no_one without a doubt. I got the same > > failures as before. > > > > With regards to gnome-specific or if KDE has the same issue, I cannot > > answer. I do not use KDE. It would appear to be gnome-specific > > (gtk-specific?). Emacs has never given me any problems, but neither has > > That includes glib also, right? right. > > nautilus, the panel, or a number of other gnome applications. > > > > For the moment, I highly suspect this is a pthread/readline interaction > > causing the crashes. > > Why do you suspect that? I suspect libreadline because the only time I get a crash is when I type in a character to an application or when it is starting up (resize?). Sorry, it just occurred to me that this might be useful information. Looking at my bash problem, I can see there is an issue with any program that might get a signal and then want to call an older installed handler as sa_handler(sig) What happens is that sigaction is called and returns a context with the _thr_sig_handler function. So the new signal handler is called and then it in turn wants to call the old one. But the old handler isn't called as a sigaction. I suppose it is really libreadline at fault here and it should check SA_SIGINFO. Do you think there might be others that don't check either? Why doesn't this show an issue in i386? Is it just luck that info has been null and not caused a bad dereference? Sean From owner-freebsd-amd64@FreeBSD.ORG Sat Jun 5 12:17:34 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 783C316A4CE; Sat, 5 Jun 2004 12:17:34 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 28B4743D2D; Sat, 5 Jun 2004 12:17:34 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id i55JHQtD001743; Sat, 5 Jun 2004 15:17:28 -0400 (EDT) Date: Sat, 5 Jun 2004 15:17:26 -0400 (EDT) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: Sean McNeil In-Reply-To: <1086455922.18813.15.camel@server.mcneil.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Tim Robbins cc: freebsd-amd64@freebsd.org cc: freebsd-threads@freebsd.org Subject: Re: All my amd64 problems appear to be KSE X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jun 2004 19:17:34 -0000 On Sat, 5 Jun 2004, Sean McNeil wrote: > On Sat, 2004-06-05 at 10:11, Daniel Eischen wrote: > > On Sat, 5 Jun 2004, Sean McNeil wrote: > > > > > resize of bash causes error like this: > > > > > > #0 _thr_sig_handler (sig=28, info=0x100, ucp=0x201701904) > > > at /usr/src/lib/libpthread/thread/thr_sig.c:373 > > > #1 0x00000002006ae9b0 in _rl_savestring () from /lib/libreadline.so.4 > > > #2 > > > #3 0x0000000200a822ec in read () from /lib/libc.so.5 > > > #4 0x00000002006ab113 in rl_getc () from /lib/libreadline.so.4 > > > #5 0x00000002006ab0c9 in rl_read_key () from /lib/libreadline.so.4 > > > #6 0x00000002006bdeb7 in readline_internal_char () from > > > /lib/libreadline.so.4 > > > > That all looks fine, but bash isn't threaded is it? > > bash isn't naturally threaded. I rebuilt db41 to its default of linking > with pthread. This caused threading to be pulled in. Look again, info > and ucp are garbage. It core dumps when it tries to dereference info. I can't tell whether info or ucp are garbage or not. If libpthread is being unloaded, then you would expect it not to work correctly. -- Dan Eischen From owner-freebsd-amd64@FreeBSD.ORG Sat Jun 5 12:21:48 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E3E7216A4CE; Sat, 5 Jun 2004 12:21:48 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9CDD943D1D; Sat, 5 Jun 2004 12:21:48 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id i55JLTtD002551; Sat, 5 Jun 2004 15:21:29 -0400 (EDT) Date: Sat, 5 Jun 2004 15:21:29 -0400 (EDT) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: Sean McNeil In-Reply-To: <1086458607.18813.37.camel@server.mcneil.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-amd64@freebsd.org cc: freebsd-threads@freebsd.org Subject: Re: All my amd64 problems appear to be KSE X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jun 2004 19:21:49 -0000 On Sat, 5 Jun 2004, Sean McNeil wrote: > On Sat, 2004-06-05 at 09:57, Daniel Eischen wrote: > > On Sat, 5 Jun 2004, Sean McNeil wrote: > > > > > With regards to gnome-specific or if KDE has the same issue, I cannot > > > answer. I do not use KDE. It would appear to be gnome-specific > > > (gtk-specific?). Emacs has never given me any problems, but neither has > > > > That includes glib also, right? > > right. > > > > nautilus, the panel, or a number of other gnome applications. > > > > > > For the moment, I highly suspect this is a pthread/readline interaction > > > causing the crashes. > > > > Why do you suspect that? > > I suspect libreadline because the only time I get a crash is when I type > in a character to an application or when it is starting up (resize?). > Sorry, it just occurred to me that this might be useful information. > > Looking at my bash problem, I can see there is an issue with any program > that might get a signal and then want to call an older installed handler > as > > sa_handler(sig) > > What happens is that sigaction is called and returns a context with the > _thr_sig_handler function. So the new signal handler is called and then > it in turn wants to call the old one. But the old handler isn't called > as a sigaction. > > I suppose it is really libreadline at fault here and it should check > SA_SIGINFO. Do you think there might be others that don't check either? I don't know; perhaps. > Why doesn't this show an issue in i386? Is it just luck that info has > been null and not caused a bad dereference? When I write signal handlers, I usually check info and ucp to make sure they are not null before using them. Actually, I rarely use them anyways so it doesn't matter if they are null or not. -- Dan Eischen From owner-freebsd-amd64@FreeBSD.ORG Sat Jun 5 12:41:18 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7670216A4CE; Sat, 5 Jun 2004 12:41:18 -0700 (PDT) Received: from ns1.xcllnt.net (209-128-86-226.BAYAREA.NET [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 16EF943D31; Sat, 5 Jun 2004 12:41:18 -0700 (PDT) (envelope-from marcel@xcllnt.net) Received: from dhcp50.pn.xcllnt.net (dhcp50.pn.xcllnt.net [192.168.4.250]) by ns1.xcllnt.net (8.12.11/8.12.11) with ESMTP id i55JfIpv001279; Sat, 5 Jun 2004 12:41:18 -0700 (PDT) (envelope-from marcel@piii.pn.xcllnt.net) Received: from dhcp50.pn.xcllnt.net (localhost [127.0.0.1]) i55JfEst026872; Sat, 5 Jun 2004 12:41:14 -0700 (PDT) (envelope-from marcel@dhcp50.pn.xcllnt.net) Received: (from marcel@localhost) by dhcp50.pn.xcllnt.net (8.12.11/8.12.11/Submit) id i55JfDal026871; Sat, 5 Jun 2004 12:41:13 -0700 (PDT) (envelope-from marcel) Date: Sat, 5 Jun 2004 12:41:13 -0700 From: Marcel Moolenaar To: Daniel Eischen Message-ID: <20040605194113.GA26707@dhcp50.pn.xcllnt.net> References: <1086458607.18813.37.camel@server.mcneil.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i cc: Sean McNeil cc: freebsd-amd64@freebsd.org cc: freebsd-threads@freebsd.org Subject: Re: All my amd64 problems appear to be KSE X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jun 2004 19:41:18 -0000 On Sat, Jun 05, 2004 at 03:21:29PM -0400, Daniel Eischen wrote: > > > > I suppose it is really libreadline at fault here and it should check > > SA_SIGINFO. Do you think there might be others that don't check either? > > I don't know; perhaps. > > > Why doesn't this show an issue in i386? Is it just luck that info has > > been null and not caused a bad dereference? > > When I write signal handlers, I usually check info and ucp to > make sure they are not null before using them. Actually, I > rarely use them anyways so it doesn't matter if they are null > or not. Nevertheless, libpthread has a signal handler that takes 3 arguments and it apparently gets called from other signal handlers (chaining) that do not always pass along the full context; just the signal number in this case. Consequently, info and ucp can be garbage as is the case here. This is a general problem and potentionally causes failures on all platforms, not just amd64. I tend to give blame to libreadline here, but I don't have a clear or even complete picture of it all, so I might actually miss a vital precondition that's being violated and that would clear libreadline... -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net