[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: gEDA-user: gschem segmentation fault

Hi,

> * What version of guile is being used?
> * Was this version of guile installed by the distribution or a custom build?
	I'm using guile-1.6.7-6, rpm supplied by Fedora
	
> * Which operating system (brand/distribution)?
	My PC at school is running a 32-bit version of Fedora Core 5 (upgrade
history of FC4->Rawhide->FC5)
	My PC at home is running a fresh 64-bit installation of Fedora Core 5
	
> * How was the software installed (distribution package/install CD)?
	Both of them experienced the same problem using the 20060123
installation CD, and the CVS version of (DMY) 6-4-2006)

> I haven't seen a failure like this in quite a while.  Could you please post
> a schematic and the exact keystrokes necessary to reproduce this seg fault?
	When I select the entire schematic (attached), and try to delete it,
it fails every single time.
	When I delete each component individualy, it will eventually fail,
but I've not noticed any consistency in to when it exactly fails.

> A few more questions:
>
> * What is the installed version of glib?
	glib-1.2.10-18.2.2 (rpm from fedora)
> * What is the installed version of gtk+?
	gtk+-1.2.10-50 (rpm from fedora)

> * Could you please post a backtrace?
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1208989504 (LWP 31049)]
magazine_cache_push_magazine (ix=1, magazine_chunks=0x9d1e500, count=51)
    at gslice.c:423
423       ChunkLink *chunk = (*magazine_chunks)->data;
(gdb) bt
#0  magazine_cache_push_magazine (ix=1, magazine_chunks=0x9d1e500, count=51)
    at gslice.c:423
#1  0x001578e5 in thread_memory_magazine2_unload (tmem=Variable "tmem"
is not av ailable.
) at gslice.c:697
#2  0x00158197 in IA__g_slice_free1 (mem_size=12, mem_block=0x9c75a50)
    at gslice.c:806
#3  0x0013f4a0 in IA__g_list_remove (list=0x9c75a70, data=0x9c76648)
    at glist.c:230
#4  0x004439f3 in s_conn_remove_other (w_current=0x980e170,
    other_object=0x9c76510, to_remove=0x9ab5890) at ../noweb/s_conn.nw:167
#5  0x00443a76 in s_conn_remove (w_current=0x980e170, to_remove=0x9ab5890)
    at ../noweb/s_conn.nw:225
#6  0x004400f1 in s_delete (w_current=0x980e170, o_current=0x9ab5890)
    at ../noweb/s_basic.nw:488
#7  0x004403b0 in s_delete_list_fromstart (w_current=0x980e170,
    start=0x99f7548) at ../noweb/s_basic.nw:637
#8  0x0043595b in o_complex_delete (w_current=0x980e170, delete=0x99f7460)
    at ../noweb/o_complex_basic.nw:1311
#9  0x0805e9e0 in o_delete_complex (w_current=0x980e170, obj=0x99f7460)
    at ../noweb/o_delete.nw:188
#10 0x0805ec3a in o_delete (w_current=0x980e170) at ../noweb/o_delete.nw:384
#11 0x08058cc4 in i_callback_edit_delete (data=0x980e170, callback_action=0,
    widget=0x0) at ../noweb/i_callbacks.nw:1113
#12 0x0805607d in g_keys_edit_delete () at ../noweb/g_keys.nw:196
---Type <return> to continue, or q <return> to quit---q

> * Are you running on an 64-bit machine?
My PC at home is, but with the workaround enabled, there's no problem

regards, Dimitri