avoid double close() and EBADF

It can be dangerous to hit (and ignore) EBADF errors in
multi-threaded applications.  Users of POSIX_MQ#to_io have two
Ruby objects pointing to the same file descriptor, making
things tricky when it comes time to reap resources.

We'll always prefer to close the Ruby IO object if it exists
(because we have less control over its GC behavior) and
ignore the raw descriptor.

1 files changed, 1 insertions, 0 deletions

diff --git a/test/test_posix_mq.rb b/test/test_posix_mq.rb
index 37ca664..78a005b 100644
--- a/test/test_posix_mq.rb
+++ b/test/test_posix_mq.rb
@@ -30,6 +30,7 @@ class Test_POSIX_MQ < Test::Unit::TestCase
   def test_gc
     assert_nothing_raised do
       2025.times { POSIX_MQ.new(@path, :rw) }
+      2025.times { a = POSIX_MQ.new(@path, :rw); a.to_io }
     end
   end