So..
I tried it on a newer version of gschem (20110115 running on someone
else's machine) and the behaviour was the same. Turned out it happens
whenever there is any wire inside a symbol.
I read somewhere on the mailing list archives that wires may not be
placed inside symbols.
Oh one update:
** (gschem:2337): CRITICAL **: o_shortest_distance: object 0x8fbf3f8
has bad type
This error showed up just now... I'm suspecting this has something to
do with the net rubber-banding but I'm not sure how to confirm...
Thanks!
~Abhijit
On Tue, Aug 23, 2011 at
Abhijit Kshirsagar abhijit...@gmail.com
writes:
I'm using gschem 1.6.1.20100214 on an Ubuntu 10.10 machine. I'm making a
simple schematic - just a couple of devices and just one page. I find that
it crashes with a Segmentation fault reported on my terminal.
Please upgrade to gEDA 1.6.2, which
Thanks. I will try with the newer version.
As of now I think the problem lies in one of the custom components I'm
using - but that should still not cause a segfault right?`
Also,� I'd have liked some inputs on how to debug the problem. Is
there some way of enabling debug logging or
On Tue, 2011-08-23 at 23:22 +0530, Abhijit Kshirsagar wrote:
Thanks. I will try with the newer version.
As of now I think the problem lies in one of the custom components I'm
using - but that should still not cause a segfault right?`
No - it should not.
If you can still reproduce it in
5 matches
Mail list logo