couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Noah Slater <nsla...@apache.org>
Subject Re: [VOTE] Apache CouchDB 1.1.0 release, round 2.
Date Sat, 28 May 2011 18:32:05 GMT
Make check ok.

Results from unit tests in Firefox:

* First base on "basics" caused segfault in CouchDB. Started over with GDB.

* Second time through with "cookie_auth" failed with "file exists" message.

* Second time through "design_docs" caused segfault:

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0x00000000107c3bc0
0x00000000107c3bc0 in ?? ()
(gdb) backtrace
#0  0x00000000107c3bc0 in ?? ()
Cannot access memory at address 0x107c3bc0
#1  0x00007fff8779b5b1 in EVP_DigestInit_ex ()
#2  0x00007fff8776989d in ssleay_rand_bytes ()
#3  0x00007fff87768f2e in ssleay_rand_pseudo_bytes ()
#4  0x000000001074307a in rand_bytes_1 ()
#5  0x00000000100fdc07 in process_main ()
#6  0x000000001006ff5e in sched_thread_func ()
#7  0x000000001018e8db in thr_wrapper ()
#8  0x00007fff833694f6 in _pthread_start ()
#9  0x00007fff833693a9 in thread_start ()

* Restarted test suite and got a segfault in "basics" again:

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0x00000000107c3bc0
[Switching to process 95309 thread 0x2803]
0x00000000107c3bc0 in ?? ()
(gdb) backtrace
#0  0x00000000107c3bc0 in ?? ()
Cannot access memory at address 0x107c3bc0
#1  0x00007fff8779b5b1 in EVP_DigestInit_ex ()
#2  0x00007fff8776989d in ssleay_rand_bytes ()
#3  0x00007fff87768f2e in ssleay_rand_pseudo_bytes ()
#4  0x000000001074307a in rand_bytes_1 ()
#5  0x00000000100fdc07 in process_main ()
#6  0x000000001006ff5e in sched_thread_func ()
#7  0x000000001018e8db in thr_wrapper ()
#8  0x00007fff833694f6 in _pthread_start ()
#9  0x00007fff833693a9 in thread_start ()

At least it seems to be the same bit of code that is segfaulting.

I am -1 on the release until we can figure out what's going on here.

Perhaps I have a dodgy SSL library?

I'm not sure how I could check for this, so looking for help!


Mime
View raw message