X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-Mailer:	exmh version 2.8.0 04/21/2012 with nmh-1.6
X-Exmh-Isig-CompType:	repl
X-Exmh-Isig-Folder:	inbox
From:	karl AT aspodata DOT se
To:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] guile auto-compile failure
In-reply-to:	<alpine.DEB.2.20.1903061554220.1487@nimbus>
References:	<20190306122848 DOT 55A4185E7F4C AT turkos DOT aspodata DOT se> <alpine DOT DEB DOT 2 DOT 20 DOT 1903061554220 DOT 1487 AT nimbus>
Comments:	In-reply-to Roland Lutz <rlutz AT hedmen DOT org>
	message dated "Wed, 06 Mar 2019 16:11:29 +0100."
Mime-Version:	1.0
Message-Id:	<20190306172213.7229185E7F52@turkos.aspodata.se>
Date:	Wed, 6 Mar 2019 18:22:13 +0100 (CET)
X-Virus-Scanned:	ClamAV using ClamSMTP
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

Roland Lutz:
> On Wed, 6 Mar 2019, karl AT aspodata DOT se wrote:
...
> > $ gnetlist-legacy -g bom2 small.sch
> > [...]
> >
> > ** (process:10644): CRITICAL **: 13:24:24.729: s_object_weak_ref: assertion 'object != NULL' failed
> > Segmentation fault
> 
> This is a third error, and what's confusing about this one is that AFAICT, 
> the code hasn't been changed for years.  Have you done anything unusual 
> with your code base?  Has the same executable been working before?  Can 
> you in any way track down the error to a particular change in your setup 
> (including switching to a different version of gEDA/gaf)?

Just run that because it was there, hoping it might work better, 
perhaps best to just remove it.

Regards,
/Karl Hammar

- Raw text -