No problems (apart from the usual test failures) with the CVS from 10 July, but with CVS from 11 July I get core dumps at random points in "make test" which seem to point to a problem with the GC code. Sample dbx output: (Platform is DEC (Compaq) Alpha, Compaq C T6.3-125 (dtk) on Digital UNIX V4.0F (Rev. 1229)) dbx version 3.11.10 Type 'help' for help. Core file created by program "python" thread 0xb signal Segmentation fault at >*[__nxm_thread_kill, 0x3ff805c7ca8] ret r31, (r26), 1 (dbx) where > 0 __nxm_thread_kill(0x3ffc01b3c10, 0x1200f47dc, 0x0, 0x11fffeed0, 0x3ff8059c724) [0x3ff805c7ca8] 1 pthread_kill(0x1200ea970, 0x1, 0x0, 0x11fffeee0, 0x3ffc01b36c0) [0x3ff805ad6f4] 2 (unknown)() [0x3ff8059712c] 3 (unknown)() [0x3ff807e370c] 4 exc_unwind(0x11fffaf28, 0xabadabad00beed00, 0x3ff80592b90, 0x11fffb1c8, 0x3ff807e3acc) [0x3ff807e380c] 5 exc_raise_signal_exception(0x86, 0x0, 0x120159490, 0x1, 0x1) [0x3ff807e3ac8] 6 (unknown)() [0x3ff805af254] 7 (unknown)() [0x12015948c] 8 (unknown)() [0x12014f36c] 9 (unknown)() [0x120159844] 10 _PyGC_Insert(0x7f, 0x6f, 0x120111690, 0x2, 0x140155e20) [0x120159d04] This _PyGC_Insert always appears here in the trace - sometimes called from PyTuple_New, sometimes from PyMethod_New... -- Email - m.favas@per.dem.csiro.au Mark C Favas Phone - +61 8 9333 6268, 0418 926 074 CSIRO Exploration & Mining Fax - +61 8 9383 9891 Private Bag No 5, Wembley WGS84 - 31.95 S, 115.80 E Western Australia 6913
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