https://bugs.kde.org/show_bug.cgi?id=432215
--- Comment #4 from Mark Wielaard <m...@klomp.org> --- (In reply to Aaron Merey from comment #3) > (In reply to Mark Wielaard from comment #1) > > - I think you need to drain stderr first in a while loop before doing the > > VG_(waitpid)(pid, NULL, 0); and VG_(read)(out_fds[0], buf, BUF_SIZE); > > because based if the user has set DEBUGINFOD_PROGRESS or DEBUGINFOD_VERBOSE > > stderr can see a lot of output (stdout is always just the filename if > > anything was found). > > Good point. It may be easier to simply redirect debuginfod-find's stderr to > a temporary file to avoid any complications with the pipe filling up. The > error message can instead be read from that file if needed. You might have to experiment with how that interacts with the DEBUGINFOD_PROGRESS output. It might be that VG_(umsg) and "interactive" stderr from the inferior don't really mix anyway. -- You are receiving this mail because: You are watching all bug changes.
