Bugs item #991754, was opened at 2004-07-15 17:27
Message generated for change (Comment added) made by dcjim
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=991754&group_id=5470

Category: Extension Modules
Group: Python 2.4
>Status: Closed
>Resolution: Fixed
Priority: 7
Submitted By: Jim Fulton (dcjim)
Assigned to: Gregory P. Smith (greg)
Summary: _bsddb segfault

Initial Comment:
I have to remove the _bsddb extension to run the Python
tests. Otherwise I get a segfault when test_anydbm is
run. I also get a segfault running test_bsddb

uname -r
2.4.22-1.2188.nptlsmp

rpm -q db4
db4-4.1.25-14


gdb ./python
GNU gdb Red Hat Linux (5.3.90-0.20030710.41rh)
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public
License, and you are
welcome to change it and/or distribute copies of it
under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show
warranty" for details.
This GDB was configured as
"i386-redhat-linux-gnu"...Using host libthread_db
library "/lib/tls/libthread_db.so.1".

(gdb) r -E -tt ./Lib/test/regrtest.py -vv test_bsddb
Starting program:
/home/jim/src/python/cvs2/dist/src/python -E -tt
./Lib/test/regrtest.py -vv test_bsddb
[Thread debugging using libthread_db enabled]
[New Thread -1084317568 (LWP 19122)]
test_bsddb
test__no_deadlock_first (test.test_bsddb.TestBTree) ...
ERROR

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1084317568 (LWP 19122)]
0x00000000 in ?? ()
(gdb) where
#0  0x00000000 in ?? ()
(gdb) r -E -tt ./Lib/test/regrtest.py -vv test_anydbm
The program being debugged has been started already.
Start it from the beginning? (y or n) y

Starting program:
/home/jim/src/python/cvs2/dist/src/python -E -tt
./Lib/test/regrtest.py -vv test_anydbm
[Thread debugging using libthread_db enabled]
[New Thread -1084645248 (LWP 19132)]
test_anydbm
test_anydbm_creation (test.test_anydbm.AnyDBMTestCase)
... ERROR

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1084645248 (LWP 19132)]
0x00000000 in ?? ()
(gdb) where
#0  0x00000000 in ?? ()


----------------------------------------------------------------------

>Comment By: Jim Fulton (dcjim)
Date: 2004-12-23 22:08

Message:
Logged In: YES 
user_id=73023

That seems to have fixed it, at least for me.

The tests run without seg-faulting and I can even import
bsddb. :)

Thanks.

P.S. I only tested the head.  Lemme know if you want be to
test the 2.4 branch.


----------------------------------------------------------------------

Comment By: Gregory P. Smith (greg)
Date: 2004-12-13 12:07

Message:
Logged In: YES 
user_id=413

I just rewrote the setup.py section that finds the header and library file for 
use when building the bsddb module.  Previously it could pick different 
versions of the header + lib which would compile and link fine but fail at 
runtime.  Its checked in to HEAD.  Could you try that out and let me know if 
that fixes anything for you?


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=991754&group_id=5470
_______________________________________________
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to