[Bug 15039] New: lldb.SBProcess.GetSTDOUT() returns empty string instead of inferior output

http://llvm.org/bugs/show_bug.cgi?id=15039

             Bug #: 15039
           Summary: lldb.SBProcess.GetSTDOUT() returns empty string
                    instead of inferior output
           Product: lldb
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: All Bugs
        AssignedTo: lldb-dev@cs.uiuc.edu
        ReportedBy: daniel.malea@intel.com
    Classification: Unclassified

When using the python API to debug an inferior on Linux,
SBProcess.GetSTDOUT(1000) returns an empty string instead of what the
subprocess writes to the stdout stream.

I verified the subprocess is flushing the output both by setting stdout to be
unbuffered, and with an explicit "fflush(stdout)" but LLDB is not exposing this
output via the python API.

To reproduce, remove the @expectedFailureLinux decorator from
TestChangeValueAPI.py and run:

python dotest.py --executable <path-to-lldb> python_api/value/change_value

Daniel Malea changed bug 15039

What Removed Added
Status NEW RESOLVED
Resolution FIXED

Comment # 1 on bug 15039 from Daniel Malea

Fixed in trunk as of 175255. Re-enabling testcase.

Daniel Malea changed bug 15039

What Removed Added
Status RESOLVED REOPENED
Resolution FIXED

Comment # 2 on bug 15039 from Daniel Malea

Seems this is still an issue, but only reproduces (for me at least) when using
GCC as the test compiler (dotest.py -C gcc).

labath@google.com changed bug 15039

What Removed Added
Status REOPENED RESOLVED
CC labath@google.com
Resolution FIXED

Comment # 10 on bug 15039 from labath@google.com

I think this is fixed now.