seg fault after "quit"

[Paul Johnson]

Dear Everybody:

I've been beating the hell out of some swarm code today and I did
something that causes a seg fault after I push the quit button.  Until
the most recent incident, I was able to make it go away by changing the
ordering of things in the modelActions part of ModelSwarm.  Now I
can't get rid of it at all.  

I don't understand the backtrace.  If you do, please let me know.
Here's a clip from the xterm, beginning
with the seg fault message, then showing gdb bt on the core.

Segmentation fault (core dumped)
address@hidden recruit081]$ gdb recruiter core
GNU gdb 4.17
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux"...
Core was generated by `./recruiter'.
Program terminated with signal 11, Segmentation fault.
find_solib: Can't read pathname for load map: Input/output error

#0  0x37f in ?? ()
(gdb) bt
#0  0x37f in ?? ()
#1  0x4010a1f5 in ?? () from /usr/local/lib/libdefobj.so.0
#2  0x40005ce6 in ?? ()
#3  0x4037d665 in ?? () from /lib/libc.so.6
(gdb) 


Paul E. Johnson                      address@hidden
Dept. of Political Science           http://lark.cc.ukans.edu/~pauljohn
University of Kansas                 Office: (913) 864-9086
Lawrence, Kansas 66045               FAX: (913) 864-5700
 


                  ==================================
   Swarm-Support is for discussion of the technical details of the day
   to day usage of Swarm.  For list administration needs (esp.
   [un]subscribing), please send a message to <address@hidden>
   with "help" in the body of the message.
                  ==================================