Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Process.respond_to?(:fork) returns true when profiling is enabled #1145

Closed
benweint opened this issue Oct 21, 2013 · 1 comment
Closed

Process.respond_to?(:fork) returns true when profiling is enabled #1145

benweint opened this issue Oct 21, 2013 · 1 comment
Assignees
Milestone

Comments

@benweint
Copy link

@benweint benweint commented Oct 21, 2013

With JRuby 1.7.5 (and 1.7.4, haven't checked other versions), when I enable profiling with the --profile or --profile.flat options in JRUBY_OPTS, Process.respond_to?(:fork) starts returning true (expected behavior on JRuby is for it to return false, since fork is not supported).

Correct (without profiling):

$ ruby -e "p Process.respond_to?(:fork)" 2>/dev/null
false
$ JRUBY_OPTS="" ruby -e "p Process.respond_to?(:fork)" 2>/dev/null
false

Incorrect (with profiling enabled):

$ JRUBY_OPTS="--profile" ruby -e "p Process.respond_to?(:fork)" 2>/dev/null
true
$ JRUBY_OPTS="--profile.flat" ruby -e "p Process.respond_to?(:fork)" 2>/dev/null
true

Version info:

$ ruby --version
jruby 1.7.5 (1.9.3p392) 2013-10-07 74e9291 on Java HotSpot(TM) 64-Bit Server VM 1.7.0_21-b12 [darwin-x86_64]
$ uname -a
Darwin koan.local 12.5.0 Darwin Kernel Version 12.5.0: Sun Sep 29 13:33:47 PDT 2013; root:xnu-2050.48.12~1/RELEASE_X86_64 x86_64
headius added a commit that referenced this issue Oct 22, 2013
@ghost ghost assigned headius Oct 22, 2013
@BanzaiMan
Copy link
Member

@BanzaiMan BanzaiMan commented Oct 22, 2013

Closing, based on the commit message above.

@BanzaiMan BanzaiMan closed this Oct 22, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants