[Bug gdb/27773] 'Dump memory' command aborted in GDB

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

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

--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Simon Marchi <simark@sourceware.org>:

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

commit bea3329b76cf131ad4ac27acb6728b38984998b9
Author: Simon Marchi <simon.marchi@polymtl.ca>
Date:   Mon Apr 26 11:27:07 2021 -0400

    gdb: check result of gdb_fopen_cloexec in dump_binary_file

    Bug 27773 shows that passing a filename in a non-existent directory to
    the "dump binary" command leads to a gdb crash.  This is because the
    gdb_fopen_cloexec in dump_binary_file fails (returns nullptr) and the
    return value is not checked.  Fix that by erroring out if
    gdb_fopen_cloexec fails.

    gdb/ChangeLog:

            PR gdb/27773
            * cli/cli-dump.c (dump_binary_file): Check result of
            gdb_fopen_cloexec.

    gdb/testsuite/ChangeLog:

            PR gdb/27773
            * gdb.base/dump.exp: Test dump to non-existent dir.

    Change-Id: Iea89a3bf9e6b9dcc31142faa5ae17bc855759328

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