[Bug gdb/7233] Send output to gdb_stdout et.al.

["cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=7233

--- Comment #4 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom Tromey <tromey@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=d68510ac191cb8b4b662a5fd1f3bcf9f4b136971

commit d68510ac191cb8b4b662a5fd1f3bcf9f4b136971
Author: Tom Tromey <tom@tromey.com>
Date:   Sun Dec 26 13:41:36 2021 -0700

    Use correct stream for process record output

    The process record code often emits unfiltered output.  In some cases,
    this output ought to go to gdb_stderr (but see below).  In other
    cases, the output is guarded by a logging variable and so ought to go
    to gdb_stdlog.  This patch makes these changes.

    Note that in many cases, the output to stderr is followed by a
    "return -1", which is how process record indicates an error.  It seems
    to me that calling error here would be preferable, because, in many
    cases, that's all the caller does when it sees a -1.  However, I
    haven't made this change.

    This is part of PR gdb/7233.

    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=7233

-- 
You are receiving this mail because:
You are on the CC list for the bug.