X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Date: Sun, 21 Jan 2018 18:53:38 +0100 (CET)
From: Roland Lutz <rlutz AT hedmen DOT org>
To: "John Griessen (john AT ecosensory DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Subject: Re: [geda-user] gschem frequent segmentation faults
In-Reply-To: <fb3d2b3a-bb9a-1959-3dad-4333d81628ae@ecosensory.com>
Message-ID: <alpine.DEB.2.20.1801211837550.4204@nimbus>
References: <fb3d2b3a-bb9a-1959-3dad-4333d81628ae AT ecosensory DOT com>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-user AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

On Sun, 21 Jan 2018, John Griessen (john AT ecosensory DOT com) [via 
geda-user AT delorie DOT com] wrote:
> I'm seeing frequent segfaults.

I'm seeing them, too, so it's probably not the fault of your setup.  It's 
on the very top of my to-do list, but I don't have the time to examine 
this further right now.

> What is a good way to clean up old guile/scheme traces left in place?

I don't install a gEDA package from my distibution and don't install the 
built files to /usr/local/, so I don't have any gEDA files in /usr/. 
Instead, I use a separate installation directory for each repository and 
invoke the executables individually by full path.  This way, I can remove 
the installation directory and be sure I don't have any files left, and I 
can be sure I invoked the correct version of the executable.

There's also the ~/.cache/ directory Richard pointed out.  I guess 
removing ~/.cache/guile/ should do the trick, though it may be a bit of an 
overkill.