From: Eumir Gaspar <eumir@admoolabs.com>
To: ruby-core@ruby-lang.org
Subject: [ruby-core:35978] [Ruby 1.9 - Bug #3804] ruby crashed while running spork
Date: Tue, 3 May 2011 19:32:56 +0900 [thread overview]
Message-ID: <redmine.journal-16747.20110503193256@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-3804.20100908225830@ruby-lang.org
Issue #3804 has been updated by Eumir Gaspar.
also happened to me:
ruby -v ruby 1.9.2p180 (2011-02-18 revision 30909) [x86_64-darwin10.7.0]
/Users/eumir/.rvm/gems/ruby-1.9.2-p180@evolux/gems/spork-0.8.4/lib/spork/forker.rb:50: [BUG] pthread_mutex_lock: Invalid argument (EINVAL)
ruby 1.9.2p180 (2011-02-18 revision 30909) [x86_64-darwin10.7.0]
-- control frame ----------
c:0012 p:---- s:0045 b:0045 l:000044 d:000044 CFUNC :raise
c:0011 p:0083 s:0041 b:0041 l:002360 d:002360 METHOD /Users/eumir/.rvm/gems/ruby-1.9.2-p180@evolux/gems/spork-0.8.4/lib/spork/forker.rb:50
c:0010 p:0055 s:0037 b:0037 l:000a40 d:000a40 METHOD /Users/eumir/.rvm/gems/ruby-1.9.2-p180@evolux/gems/spork-0.8.4/lib/spork/run_strategy/forking.rb:17
c:0009 p:0023 s:0031 b:0031 l:000030 d:000030 METHOD /Users/eumir/.rvm/gems/ruby-1.9.2-p180@evolux/gems/spork-0.8.4/lib/spork/server.rb:47
c:0008 p:0098 s:0025 b:0025 l:000024 d:000024 METHOD /Users/eumir/.rvm/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/drb/drb.rb:1558
c:0007 p:0146 s:0021 b:0021 l:000020 d:000020 METHOD /Users/eumir/.rvm/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/drb/drb.rb:1518
c:0006 p:0042 s:0017 b:0017 l:000598 d:000016 BLOCK /Users/eumir/.rvm/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/drb/drb.rb:1592
c:0005 p:---- s:0012 b:0012 l:000011 d:000011 FINISH
c:0004 p:---- s:0010 b:0010 l:000009 d:000009 CFUNC :loop
c:0003 p:0068 s:0007 b:0007 l:000598 d:000006 BLOCK /Users/eumir/.rvm/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/drb/drb.rb:1588
c:0002 p:---- s:0004 b:0004 l:000003 d:000003 FINISH
c:0001 p:---- s:0002 b:0002 l:000001 d:000001 TOP
---------------------------
-- Ruby level backtrace information ----------------------------------------
/Users/eumir/.rvm/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/drb/drb.rb:1588:in `block in main_loop'
/Users/eumir/.rvm/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/drb/drb.rb:1588:in `loop'
/Users/eumir/.rvm/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/drb/drb.rb:1592:in `block (2 levels) in main_loop'
/Users/eumir/.rvm/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/drb/drb.rb:1518:in `perform'
/Users/eumir/.rvm/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/drb/drb.rb:1558:in `perform_without_block'
/Users/eumir/.rvm/gems/ruby-1.9.2-p180@evolux/gems/spork-0.8.4/lib/spork/server.rb:47:in `run'
/Users/eumir/.rvm/gems/ruby-1.9.2-p180@evolux/gems/spork-0.8.4/lib/spork/run_strategy/forking.rb:17:in `run'
/Users/eumir/.rvm/gems/ruby-1.9.2-p180@evolux/gems/spork-0.8.4/lib/spork/forker.rb:50:in `result'
/Users/eumir/.rvm/gems/ruby-1.9.2-p180@evolux/gems/spork-0.8.4/lib/spork/forker.rb:50:in `raise'
-- C level backtrace information -------------------------------------------
0 libruby.1.9.1.dylib 0x00000001001806f2 rb_vm_bugreport + 210
1 libruby.1.9.1.dylib 0x000000010003a104 report_bug + 372
2 libruby.1.9.1.dylib 0x000000010003a2c8 rb_bug + 200
3 libruby.1.9.1.dylib 0x000000010003a8ee rb_bug_errno + 1566
4 libruby.1.9.1.dylib 0x0000000100185d7c thread_raise_m + 188
5 libruby.1.9.1.dylib 0x000000010017bc03 vm_call_method + 931
6 libruby.1.9.1.dylib 0x0000000100167da4 vm_exec_core + 8260
7 libruby.1.9.1.dylib 0x000000010016fa53 vm_exec + 1507
8 libruby.1.9.1.dylib 0x000000010017df91 loop_i + 561
9 libruby.1.9.1.dylib 0x000000010003f297 rb_rescue2 + 519
10 libruby.1.9.1.dylib 0x0000000100162c96 rb_f_loop + 54
11 libruby.1.9.1.dylib 0x000000010017bc03 vm_call_method + 931
12 libruby.1.9.1.dylib 0x0000000100167da4 vm_exec_core + 8260
13 libruby.1.9.1.dylib 0x000000010016fa53 vm_exec + 1507
14 libruby.1.9.1.dylib 0x0000000100170dcd rb_vm_invoke_proc + 877
15 libruby.1.9.1.dylib 0x0000000100188279 thread_start_func_2 + 1705
16 libruby.1.9.1.dylib 0x000000010018841d thread_start_func_1 + 29
17 libSystem.B.dylib 0x00007fff88dc94f6 _pthread_start + 331
18 libSystem.B.dylib 0x00007fff88dc93a9 thread_start + 13
[NOTE]
You may have encountered a bug in the Ruby interpreter or extension libraries.
Bug reports are welcome.
For details: http://www.ruby-lang.org/bugreport.html
Abort trap
----------------------------------------
Bug #3804: ruby crashed while running spork
http://redmine.ruby-lang.org/issues/3804
Author: Mathieu Arnold
Status: Open
Priority: Normal
Assignee:
Category:
Target version:
ruby -v: ruby 1.9.2p0 (2010-08-18 revision 29036) [x86_64-darwin10.4.0]
=begin
/Users/mat/.rvm/gems/ruby-1.9.2-p0@dns/gems/spork-0.8.4/lib/spork/forker.rb:50: [BUG] pthread_mutex_lock: Invalid argument (EINVAL)
ruby 1.9.2p0 (2010-08-18 revision 29036) [x86_64-darwin10.4.0]
-- control frame ----------
c:0012 p:---- s:0045 b:0045 l:000044 d:000044 CFUNC :raise
c:0011 p:0083 s:0041 b:0041 l:0021b0 d:0021b0 METHOD /Users/mat/.rvm/gems/ruby-1.9.2-p0@dns/gems/spork-0.8.4/lib/spork/forker.rb:50
c:0010 p:0055 s:0037 b:0037 l:001ee0 d:001ee0 METHOD /Users/mat/.rvm/gems/ruby-1.9.2-p0@dns/gems/spork-0.8.4/lib/spork/run_strategy/forking.rb:17
c:0009 p:0023 s:0031 b:0031 l:000030 d:000030 METHOD /Users/mat/.rvm/gems/ruby-1.9.2-p0@dns/gems/spork-0.8.4/lib/spork/server.rb:47
c:0008 p:0098 s:0025 b:0025 l:000024 d:000024 METHOD /Users/mat/.rvm/rubies/ruby-1.9.2-p0/lib/ruby/1.9.1/drb/drb.rb:1558
c:0007 p:0146 s:0021 b:0021 l:000020 d:000020 METHOD /Users/mat/.rvm/rubies/ruby-1.9.2-p0/lib/ruby/1.9.1/drb/drb.rb:1518
c:0006 p:0042 s:0017 b:0017 l:0010e8 d:000016 BLOCK /Users/mat/.rvm/rubies/ruby-1.9.2-p0/lib/ruby/1.9.1/drb/drb.rb:1592
c:0005 p:---- s:0012 b:0012 l:000011 d:000011 FINISH
c:0004 p:---- s:0010 b:0010 l:000009 d:000009 CFUNC :loop
c:0003 p:0068 s:0007 b:0007 l:0010e8 d:000006 BLOCK /Users/mat/.rvm/rubies/ruby-1.9.2-p0/lib/ruby/1.9.1/drb/drb.rb:1588
c:0002 p:---- s:0004 b:0004 l:000003 d:000003 FINISH
c:0001 p:---- s:0002 b:0002 l:000001 d:000001 TOP
---------------------------
-- Ruby level backtrace information ----------------------------------------
/Users/mat/.rvm/rubies/ruby-1.9.2-p0/lib/ruby/1.9.1/drb/drb.rb:1588:in `block in main_loop'
/Users/mat/.rvm/rubies/ruby-1.9.2-p0/lib/ruby/1.9.1/drb/drb.rb:1588:in `loop'
/Users/mat/.rvm/rubies/ruby-1.9.2-p0/lib/ruby/1.9.1/drb/drb.rb:1592:in `block (2 levels) in main_loop'
/Users/mat/.rvm/rubies/ruby-1.9.2-p0/lib/ruby/1.9.1/drb/drb.rb:1518:in `perform'
/Users/mat/.rvm/rubies/ruby-1.9.2-p0/lib/ruby/1.9.1/drb/drb.rb:1558:in `perform_without_block'
/Users/mat/.rvm/gems/ruby-1.9.2-p0@dns/gems/spork-0.8.4/lib/spork/server.rb:47:in `run'
/Users/mat/.rvm/gems/ruby-1.9.2-p0@dns/gems/spork-0.8.4/lib/spork/run_strategy/forking.rb:17:in `run'
/Users/mat/.rvm/gems/ruby-1.9.2-p0@dns/gems/spork-0.8.4/lib/spork/forker.rb:50:in `result'
/Users/mat/.rvm/gems/ruby-1.9.2-p0@dns/gems/spork-0.8.4/lib/spork/forker.rb:50:in `raise'
-- C level backtrace information -------------------------------------------
0 libruby.1.9.1.dylib 0x000000010017f9f2 rb_vm_bugreport + 210
1 libruby.1.9.1.dylib 0x0000000100039d24 report_bug + 372
2 libruby.1.9.1.dylib 0x0000000100039ee8 rb_bug + 200
3 libruby.1.9.1.dylib 0x000000010003a50e rb_bug_errno + 1566
4 libruby.1.9.1.dylib 0x000000010018551a thread_raise_m + 186
5 libruby.1.9.1.dylib 0x00000001001654a7 vm_call_method + 983
6 libruby.1.9.1.dylib 0x0000000100168235 vm_exec_core + 8293
7 libruby.1.9.1.dylib 0x000000010016fe73 vm_exec + 1507
8 libruby.1.9.1.dylib 0x000000010017cee1 loop_i + 545
9 libruby.1.9.1.dylib 0x000000010003ee87 rb_rescue2 + 519
10 libruby.1.9.1.dylib 0x0000000100161c66 rb_f_loop + 54
11 libruby.1.9.1.dylib 0x00000001001654a7 vm_call_method + 983
12 libruby.1.9.1.dylib 0x0000000100168235 vm_exec_core + 8293
13 libruby.1.9.1.dylib 0x000000010016fe73 vm_exec + 1507
14 libruby.1.9.1.dylib 0x00000001001711aa rb_vm_invoke_proc + 842
15 libruby.1.9.1.dylib 0x00000001001874b5 thread_start_func_2 + 1669
16 libruby.1.9.1.dylib 0x000000010018764d thread_start_func_1 + 29
17 libSystem.B.dylib 0x00007fff85945456 _pthread_start + 331
18 libSystem.B.dylib 0x00007fff85945309 thread_start + 13
[NOTE]
You may have encountered a bug in the Ruby interpreter or extension libraries.
Bug reports are welcome.
For details: http://www.ruby-lang.org/bugreport.html
Abort trap
=end
--
http://redmine.ruby-lang.org
next parent reply other threads:[~2011-05-03 10:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-3804.20100908225830@ruby-lang.org>
2011-05-03 10:32 ` Eumir Gaspar [this message]
2011-05-04 9:46 ` [ruby-core:36000] [Ruby 1.9 - Bug #3804][Feedback] ruby crashed while running spork Shota Fukumori
2011-06-26 6:15 ` [ruby-core:37399] [Ruby 1.9 - Bug #3804] " Yui NARUSE
2011-07-10 1:57 ` [ruby-core:37943] [Ruby 1.9 - Bug #3804][Rejected] " Shota Fukumori
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.journal-16747.20110503193256@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).