This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug backtrace/16577] GDB crash on attempted read from deleted shared library


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

--- Comment #5 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=416675305692976aca45860e24b963982a2e682a

commit 416675305692976aca45860e24b963982a2e682a
Author: Mike Gulick <mike.gulick@mathworks.com>
Date:   Mon Oct 30 18:13:44 2017 -0400

    Fix gdb segv when objfile can't be opened

    This fixes PR 16577.

    This patch changes gdb_bfd_map_section to issue a warning rather than an
error
    if it is unable to read the object file, and sets the size of the
section/frame
    that it attempted to read to 0 on error.

    The description of gdb_bfd_map_section states that it will try to read or
map
    the contents of the section SECT, and if successful, the section data is
    returned and *SIZE is set to the size of the section data.  This function
was
    throwing an error and leaving *SIZE as-is.  Setting the section size to 0
    indicates to dwarf2_build_frame_info that there is no data to read,
otherwise
    it will try to read from an invalid frame pointer.

    Changing the error to a warning allows this to be handled gracefully.
    Additionally, the error was clobbering the breakpoint output indicating the
    current frame (function name, arguments, source file, and line number). 
E.g.

    Thread 3 "foo" hit Breakpoint 1, BFD: reopening
/tmp/jna-1013829440/jna2973250704389291330.tmp: No such file or directory
    BFD: reopening /tmp/jna-1013829440/jna2973250704389291330.tmp: No such file
or directory
    (gdb)

    While the "BFD: reopening ..." messages will still appear interspersed in
the
    breakpoint output, the current frame info is now displayed:

    Thread 3 "foo" hit Breakpoint 1, BFD: reopening
/tmp/jna-1013829440/jna1875755897659885075.tmp: No such file or directory
    BFD: reopening /tmp/jna-1013829440/jna1875755897659885075.tmp: No such file
or directory
    warning: Can't read data for section '.eh_frame' in file
'/tmp/jna-1013829440/jna1875755897659885075.tmp'
    do_something () at file.cpp:80
    80  {
    (gdb)

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

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]