Issue #12388 has been reported by Wayne Conrad.

----------------------------------------
Bug #12388: Iterating second dbm enum causes first dbm enum to stop
https://bugs.ruby-lang.org/issues/12388

* Author: Wayne Conrad
* Status: Open
* Priority: Normal
* Assignee: 
* ruby -v: ruby 2.3.2p119 (2016-05-15 revision 55001) [x86_64-linux]
* Backport: 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN
----------------------------------------
When iterating over a dbm file, accessing the enumerator of a second dbm file causes iteration of the first dbm file to stop prematurely.  This happens in ruby 2.3.1p112 (2016-04-26 revision 54768) [x86_64-linux] and also in ruby 2.3.2p119 (2016-05-15 revision 55001) [x86_64-linux].

My Ruby's dbm is using gdbm.  This anomaly does not happen if I use gdbm directly instead of using it indirectly through dbm.  There is no maintainer listed for dbm.  Does that mean that dbm should not be used?

---Files--------------------------------
dbm_concurrent_iteration_anomaly (1.26 KB)


-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>