segfault in _dirstate_helpers_pyx.ProcessEntry.__loop_one_block

Bug #505274 reported by Joe Julian
12
This bug affects 2 people
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/.bazaar/plugins
0.079 looking for plugins in /usr/lib64/python2.4/site-packages/bzrlib/plugins
0.196 looking for plugins in /usr/lib/python2.4/site-packages/bzrlib/plugins
0.198 encoding stdout as sys.stdout encoding 'ANSI_X3.4-1968'
0.330 opening working tree '/home/jjulian/bzr-2.0bzr'
0.342 check paths: None

Bazaar (bzr) 2.0.4dev
  Python interpreter: /usr/bin/python 2.4.3
  Python standard library: /usr/lib64/python2.4
  Platform: Linux-2.6.18-92.1.22.el5xen-x86_64-with-redhat-5.4-Final
  bzrlib: /usr/lib64/python2.4/site-packages/bzrlib
  Bazaar configuration: /home/jjulian/.bazaar
  Bazaar log file: /home/jjulian/.bzr.log

$ 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_21_dirstate_helpers_pyx_13ProcessEntryC__loop_one_block (__pyx_v_self=0x1fff2c30) at bzrlib/_dirstate_helpers_pyx.c:8450
8450 Py_DECREF(__pyx_7); __pyx_7 = 0;
(gdb) bt
#0 __pyx_f_21_dirstate_helpers_pyx_13ProcessEntryC__loop_one_block (__pyx_v_self=0x1fff2c30) at bzrlib/_dirstate_helpers_pyx.c:8450
#1 0x00002b7bc30c1844 in __pyx_f_21_dirstate_helpers_pyx_13ProcessEntryC__iter_next (__pyx_v_self=0x1fff2c30) at bzrlib/_dirstate_helpers_pyx.c:7526
#2 0x00002b7bc30a4f5b in __pyx_f_21_dirstate_helpers_pyx_13ProcessEntryC___next__ (__pyx_v_self=0x2b7bbcf70740) at bzrlib/_dirstate_helpers_pyx.c:6063
#3 0x00002b7bbccfe423 in PyEval_EvalFrame () from /usr/lib64/libpython2.4.so.1.0
#4 0x00002b7bbcd02fe5 in PyEval_EvalCodeEx () from /usr/lib64/libpython2.4.so.1.0
#5 0x00002b7bbcd0173f in PyEval_EvalFrame () from /usr/lib64/libpython2.4.so.1.0
#6 0x00002b7bbcd02fe5 in PyEval_EvalCodeEx () from /usr/lib64/libpython2.4.so.1.0
#7 0x00002b7bbccb945a in ?? () from /usr/lib64/libpython2.4.so.1.0
#8 0x00002b7bbcca30f0 in PyObject_Call () from /usr/lib64/libpython2.4.so.1.0
#9 0x00002b7bbcd0052c in PyEval_EvalFrame () from /usr/lib64/libpython2.4.so.1.0
#10 0x00002b7bbcd02fe5 in PyEval_EvalCodeEx () from /usr/lib64/libpython2.4.so.1.0
#11 0x00002b7bbcd0173f in PyEval_EvalFrame () from /usr/lib64/libpython2.4.so.1.0
#12 0x00002b7bbcd02fe5 in PyEval_EvalCodeEx () from /usr/lib64/libpython2.4.so.1.0
#13 0x00002b7bbcd0173f in PyEval_EvalFrame () from /usr/lib64/libpython2.4.so.1.0
#14 0x00002b7bbcd02fe5 in PyEval_EvalCodeEx () from /usr/lib64/libpython2.4.so.1.0
#15 0x00002b7bbcd0173f in PyEval_EvalFrame () from /usr/lib64/libpython2.4.so.1.0
#16 0x00002b7bbcd02fe5 in PyEval_EvalCodeEx () from /usr/lib64/libpython2.4.so.1.0
#17 0x00002b7bbccb945a in ?? () from /usr/lib64/libpython2.4.so.1.0
#18 0x00002b7bbcca30f0 in PyObject_Call () from /usr/lib64/libpython2.4.so.1.0
#19 0x00002b7bbcd0052c in PyEval_EvalFrame () from /usr/lib64/libpython2.4.so.1.0
#20 0x00002b7bbcd02fe5 in PyEval_EvalCodeEx () from /usr/lib64/libpython2.4.so.1.0
#21 0x00002b7bbccb945a in ?? () from /usr/lib64/libpython2.4.so.1.0
#22 0x00002b7bbcca30f0 in PyObject_Call () from /usr/lib64/libpython2.4.so.1.0
#23 0x00002b7bbcd0052c in PyEval_EvalFrame () from /usr/lib64/libpython2.4.so.1.0
#24 0x00002b7bbcd02fe5 in PyEval_EvalCodeEx () from /usr/lib64/libpython2.4.so.1.0
#25 0x00002b7bbccb9367 in ?? () from /usr/lib64/libpython2.4.so.1.0
#26 0x00002b7bbcca30f0 in PyObject_Call () from /usr/lib64/libpython2.4.so.1.0
#27 0x00002b7bbcd0052c in PyEval_EvalFrame () from /usr/lib64/libpython2.4.so.1.0
#28 0x00002b7bbcd02fe5 in PyEval_EvalCodeEx () from /usr/lib64/libpython2.4.so.1.0
#29 0x00002b7bbccb945a in ?? () from /usr/lib64/libpython2.4.so.1.0
#30 0x00002b7bbcca30f0 in PyObject_Call () from /usr/lib64/libpython2.4.so.1.0
#31 0x00002b7bbcd0052c in PyEval_EvalFrame () from /usr/lib64/libpython2.4.so.1.0
#32 0x00002b7bbcd02fe5 in PyEval_EvalCodeEx () from /usr/lib64/libpython2.4.so.1.0
#33 0x00002b7bbcd0173f in PyEval_EvalFrame () from /usr/lib64/libpython2.4.so.1.0
#34 0x00002b7bbcd01b66 in PyEval_EvalFrame () from /usr/lib64/libpython2.4.so.1.0
#35 0x00002b7bbcd02fe5 in PyEval_EvalCodeEx () from /usr/lib64/libpython2.4.so.1.0
#36 0x00002b7bbcd0173f in PyEval_EvalFrame () from /usr/lib64/libpython2.4.so.1.0
#37 0x00002b7bbcd02fe5 in PyEval_EvalCodeEx () from /usr/lib64/libpython2.4.so.1.0
#38 0x00002b7bbcd03032 in PyEval_EvalCode () from /usr/lib64/libpython2.4.so.1.0
#39 0x00002b7bbcd1f729 in ?? () from /usr/lib64/libpython2.4.so.1.0
#40 0x00002b7bbcd20bd8 in PyRun_SimpleFileExFlags () from /usr/lib64/libpython2.4.so.1.0
#41 0x00002b7bbcd2700d in Py_Main () from /usr/lib64/libpython2.4.so.1.0
#42 0x00002b7bbd862994 in __libc_start_main () from /lib64/libc.so.6
#43 0x0000000000400629 in _start ()

Revision history for this message
Martin Pool (mbp) wrote :

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?

Changed in bzr:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Joe Julian (joe.julian) wrote :
Jelmer Vernooij (jelmer)
tags: added: dirstate
Jelmer Vernooij (jelmer)
tags: added: check-for-breezy
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.