I've got it narrowed down to this: vineet@cotterpin:~$ python2.2 Python 2.2.1 (#1, Sep 7 2002, 14:34:30) [GCC 2.95.4 20011002 (Debian prerelease)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import socket >>> socket.getfqdn() Segmentation fault So I tried it in gdb: vineet@cotterpin:~$ gdb python2.2 GNU gdb 2002-04-01-cvs Copyright 2002 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-linux"...(no debugging symbols found)... (gdb) run Starting program: /usr/bin/python2.2 (no debugging symbols found)...(no debugging symbols found)...[New Thread 1024 ( LWP 7097)] (no debugging symbols found)...(no debugging symbols found)... Python 2.2.1 (#1, Sep 7 2002, 14:34:30) [GCC 2.95.4 20011002 (Debian prerelease)] on linux2 Type "help", "copyright", "credits" or "license" for more information. (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... >>> import socket (no debugging symbols found)...(no debugging symbols found)... >>> socket.getfqdn() (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)... Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1024 (LWP 7097)] 0x3de23745 in ?? () (gdb) bt #0 0x3de23745 in ?? () Cannot access memory at address 0xffff0000 (gdb) Which is not very useful to me. Any ideas on how to make this more useful? Is there an easy way to rebuild it with debugging symbols? good times, Vineet -- http://www.doorstop.net/ -- http://www.eff.org/ Defending freedom in the digital world
Attachment:
signature.asc
Description: Digital signature