[Bug gdb/16039] New: gdb "next " cmd stop working when a dynamic library(libc++ static linked in) unloaded

["xhengdf at gmail dot com" <sourceware-bugzilla at sourceware dot org>]

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

            Bug ID: 16039
           Summary: gdb "next " cmd stop working when a dynamic
                    library(libc++ static linked in) unloaded
           Product: gdb
           Version: 7.6
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: xhengdf at gmail dot com

there is a dynamic library with libc++ static linked.

when call dlclose on this library, gdb "next" cmd stop to work.

since gdb has internal breakpoints on std::terminate/longjmp/..., which set
when dlopen on the library. 
after dlclose, the address of mem-break is not valid, so
remove_breakpoints/insert_breakpoints failed with EIO error.
then gdb "next" failed with "cannot insert breapoint -XXX".

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