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

javac on BashOnWindows #566

Closed
ricardosantos9521 opened this issue Jun 22, 2016 · 12 comments
Closed

javac on BashOnWindows #566

ricardosantos9521 opened this issue Jun 22, 2016 · 12 comments

Comments

@ricardosantos9521
Copy link

After the update for the build 14367 the javac doesn't compile anymore. Please solve this.

@benhillis
Copy link
Member

@ricardosantos9521 Thank you for reporting this issue. Could you share some more information with me please?

  1. What is the location of the javac source you are compiling?
  2. What build command are you running?
  3. What errors are you seeing?

@ricardosantos9521
Copy link
Author

First i instal the default-jdk
The file is c/dev
i run javac tree.java to compile as i do on "real" ubuntu
doesn't appear any error just do not compile

@therealkenc
Copy link
Collaborator

therealkenc commented Jun 22, 2016

JRE is known to hang because one of the subprocesses goes into a loop and a futex blocks forever (#541). I compiled IcedTea on native Ubuntu and copied the tree over to WSL to try and track down why, but I couldn't get gdb running (it's a tough enough slog in the best of circumstances) and gave up before long. JRE tortures pretty much every syscall under the sun so it seems premature to try tackling such a big a codebase while there remains known unimplemented syscall surface. I am pretty sure it is a shm/signal/lock/wait pthready thing, but that doesn't tell Ben much.

@ghost
Copy link

ghost commented Jun 26, 2016

I tried the same with openjdk 7 with simple helloworld program, and it hangs. Had to close the terminal and restart again.

@therealkenc
Copy link
Collaborator

If you don't want to close the terminal you can hit Ctrl-Z (SIGTSTP) and then kill the process with a SIGKILL. I don't know why it doesn't trap Ctrl-C (SIGINT).

@ghost
Copy link

ghost commented Jun 26, 2016

Ctrl-Z did work, but not sure why Ctrl-C wasn't working. Probably its not implemented yet? Sorry to deviate from the actual topic, is there any document/link which has the list of syscalls that are implemented?

Edit: Ctrl-C is working for other executable (tried python http-server). So it is not working only with javac.

@therealkenc
Copy link
Collaborator

Yeah I should have been more explicit. I was meaning it is on-topic because SIGINT works in general. Whatever is hosing JRE apps that use (as of this writing ) unknown constructs hoses it good. I tried to track it to a concrete test case but stracing all of the javac threads is a bear.

@benhillis benhillis added the bug label Jun 27, 2016
@ghost
Copy link

ghost commented Jun 29, 2016

I also can not run javac in bash for windows. Is there any solution to this problem?

@therealkenc
Copy link
Collaborator

Workaround @leninalive posted in #541 seems to solve.

@ghost
Copy link

ghost commented Jun 29, 2016

Yep. That worked as of now.

@philharmonikerzzy
Copy link

Does this issue share the same cause as that of not being able to run maven for bash for windows? They seem to hang in the same way.

@benhillis
Copy link
Member

Marking as duplicate of #746.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants