Bugs item #1544106, was opened at 2006-08-21 11:02 Message generated for change (Comment added) made by greg You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1544106&group_id=5470
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Extension Modules Group: Python 2.5 Status: Open Resolution: None Priority: 5 Submitted By: Clay Spence (cspence) Assigned to: Gregory P. Smith (greg) Summary: test_anydbm segmentation fault Initial Comment: After building 2.5rc1 and bfore installing, make test failed for me at test_anydbm: cholla 88% uname -a Linux cholla.sarnoff.com 2.6.9-34.ELsmp #1 SMP Fri Feb 24 16:54:53 EST 2006 i686 i686 i386 GNU/Linux cholla 89% ./python Python 2.5c1 (r25c1:51305, Aug 21 2006, 11:30:37) [GCC 3.4.5 20051201 (Red Hat 3.4.5-2)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> cholla 90% ./python ./Lib/test/test_anydbm.py Segmentation fault cholla 91% I tracked this to Lib/bsddb/__init__.py, line 355, in _openDBEnv(): e.set_lk_detect(db.DB_LOCK_DEFAULT) See the attached pdb text output, if it's useful. ---------------------------------------------------------------------- >Comment By: Gregory P. Smith (greg) Date: 2006-09-03 16:14 Message: Logged In: YES user_id=413 weird i would not expect this to happen regardless of berkeleydb version. can you also do a 'ldd' on the _bsddb.so binary that your python build produced? presumably libdb42.so or something similar should be in the output. also, when to compile python does it print out a message saying what version of the include files and libs it thinks its compiling and linking with? it looks like you're using rhel4 or centos4; i'll try compiling 2.5rc1 on that myself when i get a chance. ---------------------------------------------------------------------- Comment By: Neal Norwitz (nnorwitz) Date: 2006-08-22 06:45 Message: Logged In: YES user_id=33168 Yes, correct. 4.2.52 is the version of the C BSD DB library. That's a fairly old version. I believe the bug is in there. If you update to 4.3.x or 4.4.x, I suspect the problem will go away. I know very little about bsddb. The code looks quite simple. Assigning Greg as he's probably the only one that has a chance of knowing. ---------------------------------------------------------------------- Comment By: Clay Spence (cspence) Date: 2006-08-22 06:26 Message: Logged In: YES user_id=685289 Excuse my ignorance, but I'm not sure how to determine the version. Poking around gives me: cholla 92% ./python Python 2.5c1 (r25c1:51305, Aug 21 2006, 11:30:37) [GCC 3.4.5 20051201 (Red Hat 3.4.5-2)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import bsddb >>> bsddb.__version__ '4.4.5' >>> bsddb._bsddb.version() (4, 2, 52) >>> Is it the second? ---------------------------------------------------------------------- Comment By: Neal Norwitz (nnorwitz) Date: 2006-08-21 16:28 Message: Logged In: YES user_id=33168 I'm guessing this is an old version of berkeley db. What version of bdb are you using? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1544106&group_id=5470 _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
