segfault in _dirstate_helpers_pyx.ProcessEntry.__loop_one_block
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
Medium
|
Unassigned |
Bug Description
branch: 2.0 revno: 4721
Sat 2010-01-09 12:47:12 -0800
0.063 bzr arguments: [u'status']
0.079 looking for plugins in /home/jjulian/
0.079 looking for plugins in /usr/lib64/
0.196 looking for plugins in /usr/lib/
0.198 encoding stdout as sys.stdout encoding 'ANSI_X3.4-1968'
0.330 opening working tree '/home/
0.342 check paths: None
Bazaar (bzr) 2.0.4dev
Python interpreter: /usr/bin/python 2.4.3
Python standard library: /usr/lib64/
Platform: Linux-2.
bzrlib: /usr/lib64/
Bazaar configuration: /home/jjulian/
Bazaar log file: /home/jjulian/
$ gdb python
(gdb) run /usr/bin/bzr status
Starting program: /usr/bin/python /usr/bin/bzr status
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[New Thread 0x2b7e62257190 (LWP 9331)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
Program received signal SIGSEGV, Segmentation fault.
__pyx_f_
8450 Py_DECREF(__pyx_7); __pyx_7 = 0;
(gdb) bt
#0 __pyx_f_
#1 0x00002b7bc30c1844 in __pyx_f_
#2 0x00002b7bc30a4f5b in __pyx_f_
#3 0x00002b7bbccfe423 in PyEval_EvalFrame () from /usr/lib64/
#4 0x00002b7bbcd02fe5 in PyEval_EvalCodeEx () from /usr/lib64/
#5 0x00002b7bbcd0173f in PyEval_EvalFrame () from /usr/lib64/
#6 0x00002b7bbcd02fe5 in PyEval_EvalCodeEx () from /usr/lib64/
#7 0x00002b7bbccb945a in ?? () from /usr/lib64/
#8 0x00002b7bbcca30f0 in PyObject_Call () from /usr/lib64/
#9 0x00002b7bbcd0052c in PyEval_EvalFrame () from /usr/lib64/
#10 0x00002b7bbcd02fe5 in PyEval_EvalCodeEx () from /usr/lib64/
#11 0x00002b7bbcd0173f in PyEval_EvalFrame () from /usr/lib64/
#12 0x00002b7bbcd02fe5 in PyEval_EvalCodeEx () from /usr/lib64/
#13 0x00002b7bbcd0173f in PyEval_EvalFrame () from /usr/lib64/
#14 0x00002b7bbcd02fe5 in PyEval_EvalCodeEx () from /usr/lib64/
#15 0x00002b7bbcd0173f in PyEval_EvalFrame () from /usr/lib64/
#16 0x00002b7bbcd02fe5 in PyEval_EvalCodeEx () from /usr/lib64/
#17 0x00002b7bbccb945a in ?? () from /usr/lib64/
#18 0x00002b7bbcca30f0 in PyObject_Call () from /usr/lib64/
#19 0x00002b7bbcd0052c in PyEval_EvalFrame () from /usr/lib64/
#20 0x00002b7bbcd02fe5 in PyEval_EvalCodeEx () from /usr/lib64/
#21 0x00002b7bbccb945a in ?? () from /usr/lib64/
#22 0x00002b7bbcca30f0 in PyObject_Call () from /usr/lib64/
#23 0x00002b7bbcd0052c in PyEval_EvalFrame () from /usr/lib64/
#24 0x00002b7bbcd02fe5 in PyEval_EvalCodeEx () from /usr/lib64/
#25 0x00002b7bbccb9367 in ?? () from /usr/lib64/
#26 0x00002b7bbcca30f0 in PyObject_Call () from /usr/lib64/
#27 0x00002b7bbcd0052c in PyEval_EvalFrame () from /usr/lib64/
#28 0x00002b7bbcd02fe5 in PyEval_EvalCodeEx () from /usr/lib64/
#29 0x00002b7bbccb945a in ?? () from /usr/lib64/
#30 0x00002b7bbcca30f0 in PyObject_Call () from /usr/lib64/
#31 0x00002b7bbcd0052c in PyEval_EvalFrame () from /usr/lib64/
#32 0x00002b7bbcd02fe5 in PyEval_EvalCodeEx () from /usr/lib64/
#33 0x00002b7bbcd0173f in PyEval_EvalFrame () from /usr/lib64/
#34 0x00002b7bbcd01b66 in PyEval_EvalFrame () from /usr/lib64/
#35 0x00002b7bbcd02fe5 in PyEval_EvalCodeEx () from /usr/lib64/
#36 0x00002b7bbcd0173f in PyEval_EvalFrame () from /usr/lib64/
#37 0x00002b7bbcd02fe5 in PyEval_EvalCodeEx () from /usr/lib64/
#38 0x00002b7bbcd03032 in PyEval_EvalCode () from /usr/lib64/
#39 0x00002b7bbcd1f729 in ?? () from /usr/lib64/
#40 0x00002b7bbcd20bd8 in PyRun_SimpleFil
#41 0x00002b7bbcd2700d in Py_Main () from /usr/lib64/
#42 0x00002b7bbd862994 in __libc_start_main () from /lib64/libc.so.6
#43 0x0000000000400629 in _start ()
Thanks for the traceback. Does this happen on all trees, or just this one?
It looks ilke you're getting this in a checkout of bzr itself. Could you attach the .bzr/checkout/ dirstate file to this bug?