X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:content-type;
	bh=5qDnJZ7L4EjDm3Lrdkywz2AgePYbTvff9/axSZlquLw=;
	b=xTSrHtgGTkJqTXi/TszIp83cVAktdjozy/mG5mCanbsOOYxyzBmf5yhfwSRw78EVY8
	h7MwPgleZgFXoqD3wv4WMrWjzzhnDeDk5N1ou/hoDUgjcyqGSpJi5A3CpjigKMjMGZ4/
	gcEvjI1gGU7jiDzSsP5M1PMs0ASiWblFd+DeLQHyOp1MbS9T1Vy4JYOpDDj9A0CnECI3
	40kEuJFRtoc1x5kq8eZVLxPYgQKmvuOSgf5FE1beZ2L03qOm2+nF+elDfcwDd84I8Ny8
	7/kJlMwC4K2MURzN/KZ6uhFoNONE2so3Fxi2GJwhLoktXCm/pEgT96lp4KqlI2N8DJ/0
	6Xzw==
MIME-Version:	1.0
In-Reply-To:	<CAMvDHVD01WBCOMgZebkJS9uWgjHZQa5VRrQ7VFHR-eCsyCvCYQ@mail.gmail.com>
References:	<CACPio-7BaZJ5ZirPVEjHEfWbXjC5gENX6rhJcmfdw0KcCL7WBw AT mail DOT gmail DOT com>
	<CACPio-5JEEoaqFcHHmRy2+yPqjLOR98G7gyxrzrTNpWLHzR-ew AT mail DOT gmail DOT com>
	<CAMvDHVD01WBCOMgZebkJS9uWgjHZQa5VRrQ7VFHR-eCsyCvCYQ AT mail DOT gmail DOT com>
Date:	Thu, 3 May 2012 08:28:12 -0400
Message-ID:	<CACPio-6fSgp8MyXVPzaT7E2rcCf6rDCNp9+xiQ-FhD392jByWA@mail.gmail.com>
Subject:	Re: [geda-user] Re: crash connecting to nets
From:	Nathan Stewart <therealnathanstewart AT gmail DOT com>
To:	geda-user AT delorie DOT com
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

Ok, not sure if this is a bug so much as an ungraceful failure. I was
trying to use it incorrectly.

I couldn't recreate the problem initially either, when I set out to
create the simplest possible test case. It turns out that I had used
subcomponents in my symbol, made them graphical, but had hooked them
up with nets (which I also attempted to mark as graphical at the same
time - not sure if nets can be graphical)

The problem occurs when connecting to a NET in a symbol. In my test
case, I created a sub component, added a net to one of the pins. In
this case, connecting to either end of the NET blows up. Then I
disconnected the NET from the PIN, but left it in. Now I can connect
to the PIN. I could also connect to one end of the NET, but not the
other.

Also interesting when the debugger stops here is that j,k are
optimized out, even though the code path is going to attempt to index
using them into the null pointer, but I try not to read too much into
what the debugger thinks the optimizer has done. (Arguing with the
compiler is like arguing with your wife. You're rarely right, but even
when you are, it doesn't matter - you're not getting anywhere until
you make it happy.)


On Thu, May 3, 2012 at 6:39 AM, Vladimir Zhbanov <vzhbanov AT gmail DOT com> wrote:
> 2012/5/1 Nathan Stewart wrote:
>> Sorry - this is current git source (7e8f6fdb2af40cab8e4fe969b25c6aa39f20240d)
>
> I can't reproduce such a behaviour using hierarchical
> schematic from gaf sources.
>
> Please file a bug report, preferably provided with a simple
> test case. (https://bugs.launchpad.net/geda)

- Raw text -