Redirect NaCl application STDERR without --no-sandbox flag

[Dima Kuzmin]

Hello,

I have read NaCl Debugging guide where it is described how to redirect the STDOUT and STDERR streams for NaCl application. 

I tried it locally and it works, STDERR contains a lot of useful information about the app crashes that I cannot get in any other way.

It would help me a lot if I could use this feature to obtain STDERR output when my app crashes on production. The problem is, my app runs on many machines, and there is no way I can get them all running Chrome with --no-sandbox flag.

So the question is, can I obtain STDERR output of NaCl application in any other way?  Even tweaking Native Client sources will be okay, as long as the solution is not required to run under any special Chrome flags.

[Russell Valentine]

I would check out the nacl_io_demo. You can pipe stderr and stdout messages from nacl side to javascript.

--
You received this message because you are subscribed to the Google Groups "Native-Client-Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to native-client-di...@googlegroups.com.
To post to this group, send email to native-cli...@googlegroups.com.
Visit this group at https://groups.google.com/group/native-client-discuss.
For more options, visit https://groups.google.com/d/optout.