need a way to see native code output
GoogleCodeExporter opened this issue · 5 comments
GoogleCodeExporter commented
if you add a System.err.println, you get to see the output. if you add a LOGE
to native code, you don't. likewise if you run valgrind or whatever: you don't
see valgrind's output.
Original issue reported on code.google.com by e...@google.com
on 22 Jun 2010 at 10:16
GoogleCodeExporter commented
Original comment by e...@google.com
on 22 Jun 2010 at 10:42
GoogleCodeExporter commented
As I mentioned offline, this is tricky because the native output stream doesn't
delimit individual test methods. The easiest fix here is to print the native
output unattached to any particular test's output stream.
Original comment by jessewil...@google.com
on 23 Jun 2010 at 3:46
GoogleCodeExporter commented
This is what I had been discussing on the whiteboard in terms of running in a
subprocess to capture the standard output. In my case, I usually do this when
debugging a specific test so the local of correlation to a particular test is
unnecessary.
Original comment by b...@google.com
on 23 Jun 2010 at 4:29
GoogleCodeExporter commented
Issue 17 has been merged into this issue.
Original comment by e...@google.com
on 7 Jul 2010 at 10:18
GoogleCodeExporter commented
Fixed with r178.
Original comment by jessewil...@google.com
on 16 Oct 2010 at 8:17
- Changed state: Fixed