breakpoints/1915: gdb offers to set a pending breakpoint even when it will never be able to resolve the breakpoint

greenrd@greenrd.org greenrd@greenrd.org
Mon Apr 11 22:58:00 GMT 2005


>Number:         1915
>Category:       breakpoints
>Synopsis:       gdb offers to set a pending breakpoint even when it will never be able to resolve the breakpoint
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Apr 11 22:58:00 UTC 2005
>Closed-Date:
>Last-Modified:
>Originator:     greenrd@greenrd.org
>Release:        gdb-6.3.0.0-1.11
>Organization:
>Environment:
Fedora Core 3
>Description:
When gdb is used to attach to a running process, it won't be able to track dynamic shared library loads that occur after it has attached. However, it still offers to set pending breakpoints if a symbol the user wants to break on is not known, which is misleading to the user.
>How-To-Repeat:
Attach to a running process
Attempt to set a breakpoint in a lib that has not yet loaded
gdb will ask you whether you want to set a pending breakpoint
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:



More information about the Gdb-prs mailing list