Re: Bug#195846: python2.2: Core-dumps when files get large
On Mon, Jun 02, 2003 at 10:56:05PM +0200, Matthias Klose wrote:
> That are 18MB, not 1,8GB.
Oops.
> Without a stack trace, there is not much to do ...
Here you go:
#0 0x0fd90454 in exit () from /lib/libc.so.6
#1 0x0fd9044c in exit () from /lib/libc.so.6
#2 0x0ff79884 in __pthread_sighandler () from /lib/libpthread.so.0
#3 <signal handler called>
#4 0x0fd8dfd0 in kill () from /lib/libc.so.6
#5 0x0f7d8108 in wtouchln () from /lib/libncurses.so.5
#6 0x0ff79884 in __pthread_sighandler () from /lib/libpthread.so.0
#7 <signal handler called>
#8 0x0fd8e044 in sigsuspend () from /lib/libc.so.6
#9 0x0ff74adc in __pthread_wait_for_restart_signal ()
from /lib/libpthread.so.0
#10 0x0ff71170 in pthread_cond_wait () from /lib/libpthread.so.0
#11 0x10074a98 in PyThread_acquire_lock ()
#12 0x1003ecf0 in PyEval_RestoreThread ()
#13 0x0fd10ea4 in inittime () from /usr/lib/python2.2/lib-dynload/time.so
#14 0x100bd268 in PyCFunction_Call ()
#15 0x1003afec in Py_MakePendingCalls ()
#16 0x1003bd4c in PyEval_EvalCodeEx ()
#17 0x1003d278 in PyEval_CallObjectWithKeywords ()
#18 0x1003af08 in Py_MakePendingCalls ()
#19 0x1003bd4c in PyEval_EvalCodeEx ()
#20 0x1003d278 in PyEval_CallObjectWithKeywords ()
#21 0x1003af08 in Py_MakePendingCalls ()
#22 0x1003bd4c in PyEval_EvalCodeEx ()
#23 0x1003d278 in PyEval_CallObjectWithKeywords ()
#24 0x1003af08 in Py_MakePendingCalls ()
#25 0x1003bd4c in PyEval_EvalCodeEx ()
#26 0x1003eddc in PyEval_EvalCode ()
#27 0x1006fd20 in PyRun_FileExFlags ()
#28 0x1006f458 in PyRun_SimpleFileExFlags ()
#29 0x1000c42c in Py_Main ()
#30 0x1000bea0 in main ()
#31 0x0fd77d04 in __libc_start_main () from /lib/libc.so.6
Reply to: