This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
Re: breakpoints/1915: gdb offers to set a pending breakpoint evenwhen it will never be able to resolve the breakpoint
- From: Ramana Radhakrishnan <ramana dot radhakrishnan at codito dot com>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 30 Jun 2005 09:18:01 -0000
- Subject: Re: breakpoints/1915: gdb offers to set a pending breakpoint evenwhen it will never be able to resolve the breakpoint
- Reply-to: Ramana Radhakrishnan <ramana dot radhakrishnan at codito dot com>
The following reply was made to PR breakpoints/1915; it has been noted by GNATS.
From: Ramana Radhakrishnan <ramana.radhakrishnan@codito.com>
To: greenrd@greenrd.org, gdb-prs@sources.redhat.com, nobody@sources.redhat.com,
gdb-gnats@sources.redhat.com
Cc:
Subject: Re: breakpoints/1915: gdb offers to set a pending breakpoint even
when it will never be able to resolve the breakpoint
Date: Thu, 30 Jun 2005 14:40:43 +0530
http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gdb&pr=1915
> 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
Eh, Is this not expected behaviour ? If it cannot set a breakpoint at a particular symbol it looks for
the symbol otherwise. A testcase would be useful.
cheers
Ramana