From owner-freebsd-stable@FreeBSD.ORG Wed Apr 21 02:27:01 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8BCDE16A4CE for ; Wed, 21 Apr 2004 02:27:01 -0700 (PDT) Received: from atlas.informatik.rwth-aachen.de (atlas.informatik.RWTH-Aachen.DE [137.226.194.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7211143D5C for ; Wed, 21 Apr 2004 02:27:00 -0700 (PDT) (envelope-from stolz@i2.informatik.rwth-aachen.de) Received: from menelaos.informatik.rwth-aachen.de (menelaos.informatik.RWTH-Aachen.DE [137.226.194.73]) 8.11.1-0.5-michaelw-20030918) with ESMTP id i3L9Qx432766; Wed, 21 Apr 2004 11:26:59 +0200 Received: (from stolz@localhost)i3L9QxJx019710; Wed, 21 Apr 2004 11:26:59 +0200 (CEST) (envelope-from stolz) Date: Wed, 21 Apr 2004 11:26:59 +0200 From: Volker Stolz To: Kris Kennaway Message-ID: <20040421092659.GA19703@i2.informatik.rwth-aachen.de> References: <20040421004132.GA2292@dogma.freebsd-uk.eu.org> <1082508499.41182.4.camel@shumai.marcuscom.com> <20040421005507.GA70542@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20040421005507.GA70542@xor.obsecurity.org> X-PGP-Key: finger vs@foldr.org X-PGP-Id: 0x3FD1B6B5 User-Agent: Mutt/1.5.4i cc: stable@freebsd.org Subject: iiimf-csconv [was: Re: Can't build gtk20, no ideas....] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Apr 2004 09:27:01 -0000 In local.freebsd-stable, you wrote: > I see similar errors repeatably on non-gnome ports on bento, e.g. > http://bento.freebsd.org/errorlogs/i386-4-full/iiimf-csconv-r11.4_1.log > I've not been able to track down what is calling rcmdsh [1], let alone why > it's failing. Just to add a data point in case somebody wants to look at this: Looks like a smashed stack: gdb'ing drops you dead in libc's _start() when you get back from the "call main", if you use "exit" instead of "return" in main, something else goes wrong...Interestingly, the problem goes away when linking with ElectricFence. Volker -- http://www-i2.informatik.rwth-aachen.de/stolz/ *** PGP *** S/MIME Neu! Ändern Sie den Anfangstag Ihrer Woche