mobile icon indicating copy to clipboard operation
mobile copied to clipboard

internal/mobileinit: redirect std{out,err} without using Go

Open gawen opened this issue 6 years ago • 7 comments

As stderr may be written while the world is frozen (e.g. the runtime dumping the traceback of a panic), the redirection of stdout and stderr to Android's logcat cannot be done in Go but in C.

This implementation spawns a detached thread which will wait for stdout or stderr to be readable, and when so, read one line at a time and write it to Android's logcat.

Fixes golang/go#35590

gawen avatar Dec 20 '19 15:12 gawen

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

:memo: Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.


What to do if you already signed the CLA

Individual signers
Corporate signers

ℹ️ Googlers: Go here for more info.

googlebot avatar Dec 20 '19 15:12 googlebot

@googlebot I signed it!

(FYI corporate signer)

gawen avatar Dec 20 '19 16:12 gawen

@googlebot I signed it!

gawen avatar Dec 30 '19 12:12 gawen

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

googlebot avatar Dec 30 '19 12:12 googlebot

This PR (HEAD: ca3f1f52559a08aae37846233af3cd1d14119178) has been imported to Gerrit for code review.

Please visit https://go-review.googlesource.com/c/mobile/+/212839 to see it.

Tip: You can toggle comments from me using the comments slash command (e.g. /comments off) See the Wiki page for more info

gopherbot avatar Dec 30 '19 12:12 gopherbot

Message from Gobot Gobot:

Patch Set 1:

Congratulations on opening your first change. Thank you for your contribution!

Next steps: Within the next week or so, a maintainer will review your change and provide feedback. See https://golang.org/doc/contribute.html#review for more info and tips to get your patch through code review.

Most changes in the Go project go through a few rounds of revision. This can be surprising to people new to the project. The careful, iterative review process is our way of helping mentor contributors and ensuring that their contributions have a lasting impact.

During May-July and Nov-Jan the Go project is in a code freeze, during which little code gets reviewed or merged. If a reviewer responds with a comment like R=go1.11, it means that this CL will be reviewed as part of the next development cycle. See https://golang.org/s/release for more details.


Please don’t reply on this GitHub thread. Visit golang.org/cl/212839. After addressing review feedback, remember to publish your drafts!

gopherbot avatar Dec 30 '19 12:12 gopherbot

Message from Go Bot:

Patch Set 1:

Congratulations on opening your first change. Thank you for your contribution!

Next steps: Within the next week or so, a maintainer will review your change and provide feedback. See https://golang.org/doc/contribute.html#review for more info and tips to get your patch through code review.

Most changes in the Go project go through a few rounds of revision. This can be surprising to people new to the project. The careful, iterative review process is our way of helping mentor contributors and ensuring that their contributions have a lasting impact.

During May-July and Nov-Jan the Go project is in a code freeze, during which little code gets reviewed or merged. If a reviewer responds with a comment like R=go1.11, it means that this CL will be reviewed as part of the next development cycle. See https://golang.org/s/release for more details.


Please don’t reply on this GitHub thread. Visit golang.org/cl/212839. After addressing review feedback, remember to publish your drafts!

gopherbot avatar Oct 15 '20 03:10 gopherbot