> It doesn't get as far as the banner: > > Script started on Mon Dec 22 14:42:19 2003 > hydra /home/kbk/proj/sandbox/python_clean$ gdb ./python > GNU gdb 4.16.1 > Copyright 1996 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-unknown-openbsd3.3"... > (gdb) run > Starting program: /home/kbk/proj/sandbox/python_clean/./python > > Program received signal SIGSEGV, Segmentation fault. > 0x401900a0 in strchr () > (gdb) quit > The program is running. Quit anyway (and kill it)? (y or n) y > hydra /home/kbk/proj/sandbox/python_clean$ > Script done on Mon Dec 22 14:42:38 2003 > > Investigating. That suggests it's still in Py_Initialize(). What does the gdb command 'bt' say??? I'd also try another experiment: instead of "run" try "run -S". This passes the -S option to Python when it is started, so that it doesn't try to load site.py (which executes rather a lot of Python code). I'd be interested in seeing how much you can do interactively in that case, of if it still crashes in Py_Initialize(). --Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4