On Sun, 2008-09-07 at 07:40 +0100, Peter TB Brett wrote: > On Sunday 07 September 2008 01:44:37 Ales Hvezda wrote: > > gschem git head (commit b4ed5e92d203c7449b7d33e924a41b093e1de930) seg > > faults on exit: > > > > 1) Run gschem with at least two schematics on the command line > > (any schematics; they can even be just empty files) > > 2) Exit gschem > > 3) observe core dump at:
Found and fixed this one. It was introduced in the innocuously titled: > commit 95923f7de815ec58819eaf94ab9332d51a28fbb9 > Author: Patrick Bernaud <[EMAIL PROTECTED]> > Date: Fri Jul 25 17:52:39 2008 +0200 > > Simplify prototype of s_tile_remove_object(). Unfortunately this commit removed the temporary shuffling done to set the current page before deleting things from it. Patrick removed the unused parameters to s_tile_remove_object() (one being passed toplevel->page_current), but the assumption that objects being deleted are on the current page still persists elsewhere, e.g. in s_delete_object() I reverted the commit, re-added the bits which weren't causing the crash, then committed a more direct warning as to why we make the page being deleted current in s_page_delete(). [snip] > > "Interrupt system call"? A non-existant schematic causes an interrupted > > system call. Okay... Sounds like a bug in the (new-ish) error reporting code. That one might be more up Peter B's street. -- Peter Clifton Electrical Engineering Division, Engineering Department, University of Cambridge, 9, JJ Thomson Avenue, Cambridge CB3 0FA Tel: +44 (0)7729 980173 - (No signal in the lab!) _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
