From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2287 invoked from network); 21 Dec 2003 15:33:52 -0000 Received: from sunsite.dk (130.225.247.90) by ns1.primenet.com.au with SMTP; 21 Dec 2003 15:33:52 -0000 Received: (qmail 19364 invoked by alias); 21 Dec 2003 15:33:37 -0000 Mailing-List: contact zsh-users-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 6943 Received: (qmail 19304 invoked from network); 21 Dec 2003 15:33:36 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 21 Dec 2003 15:33:36 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [200.17.209.129] by sunsite.dk (MessageWall 1.0.8) with SMTP; 21 Dec 2003 15:33:36 -0000 Received: by fisica.ufpr.br (Postfix) id A220E23AC93; Sun, 21 Dec 2003 13:33:34 -0200 (BRDT) From: Carlos Carvalho Message-Id: <16357.48454.273094.145563@fisica.ufpr.br> Date: Sun, 21 Dec 2003 13:33:26 -0200 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Zsh users list Subject: Re: 4.0.9 In-Reply-To: <20031221130800.GA20618@DervishD> References: <14540.1071847413@csr.com> <16356.46659.422887.208336@fisica.ufpr.br> <20031221130800.GA20618@DervishD> X-Mailer: VM 7.07 under Emacs 19.34.1 DervishD (raul@pleyades.net) wrote on 21 December 2003 14:08: > * Carlos Carvalho dixit: >> Module loading doesn't work for me in either 4.0.8 or 4.0.9. I'm using >> gcc 3.3.2 and the latest libc from debian unstable. > > I've tested with 4.0.9, GCC 3.3, libc 2.2.4, and have the same >problem. > >> and it ends up segfaulting. > > Mine didn't segfaulted, but it was unable to load modules. >Anyway, I've done a quick and dirty test, so I'm not sure if the >problem is my fault (which is, probably). I found that the module loading didn't work because the installation process didn't complete and the modules were not put in the system area. The segfaulting is happening with several other programs in an apparently random fashion; rebooting "cures" it for a while. Therefore it's not zsh-related. Looks like some cache mis-behavior... Sorry for the false alarm.