From owner-freebsd-stable Sun Feb 11 21:43:56 2001 Delivered-To: freebsd-stable@freebsd.org Received: from pendragon.tacni.net (unknown [216.178.136.165]) by hub.freebsd.org (Postfix) with SMTP id CB19B37B401 for ; Sun, 11 Feb 2001 21:43:51 -0800 (PST) Received: (qmail 60134 invoked by alias); 12 Feb 2001 05:43:49 -0000 Received: from unknown (HELO mail.tacni.net) (204.155.159.101) by ns2.sohos.net with SMTP; 12 Feb 2001 05:43:49 -0000 Received: (qmail 5943 invoked by uid 1000); 12 Feb 2001 05:43:48 -0000 Date: Sun, 11 Feb 2001 23:43:48 -0600 From: Erich Zigler To: stable@freebsd.org Subject: getenv() problems on 4.2-STABLE Message-ID: <20010211234348.A5894@superhero.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Eric-Conspiracy: There is no conspiracy. X-Shane: Hi Shane! Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've currently been working on the Gabber port. I'm running in to a constant problem though. Whenever gettext or GNOME makes a getenv() call it segfaults. This is Gabber 0.8.1. Here is an example of one of the backtraces... #0 0x28c0e7a3 in getenv () from /usr/lib/libc_r.so.4 #1 0x2881aa5d in guess_category_value () from /usr/local/lib/libintl.so.1 #2 0x2881a36a in dcgettext__ () from /usr/local/lib/libintl.so.1 #3 0x2881ab0c in dgettext__ () from /usr/local/lib/libintl.so.1 #4 0x2881ab38 in gettext__ () from /usr/local/lib/libintl.so.1 #5 0x28819ffe in gettext () from /usr/local/lib/libintl.so.1 #6 0x80c0efb in GabberWin::OnSessionConnected (this=0x8390a00, t=@0x838b200) at GabberWin.cc:302 I wrote a small getenv() test program, and it works fine. So why is this coring? Here is the test program.. #include main() { printf("HOME=%s\n", getenv("HOME")); } Any help would be greatly appreciated, the developers of Gabber and I are completely stumped. -- Erich Zigler Mind like a steel trap - Rusty and Illegal in 37 States! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message