This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: GDB 5.2/5.3 breakpoint bug
On Wed, Jan 08, 2003 at 12:39:31PM -0500, Daniel Jacobowitz wrote:
> On Tue, Jan 07, 2003 at 03:49:31PM -0800, Sunil Alankar wrote:
> > Hi,
> >
> > While debugging this in function, find_pc_sect_line (CORE_ADDR pc, struct
> > sec *section, int notcurrent)
> > I found there were two line items in a line table with the same value of PC.
> > First one gets picked as the best match. But this had item->line == 0. The
> > next line item with the same value for item->pc, but a valid item->line ( >
> > 0) does not get picked as the best match.
> > I put in the following check to correct this. My question is,
> > Is it valid to have have more than one line item with same value faor PC and
> > possibly 0 for line in one of them? What causes this?
> > Would this be an appropriate fix? Or is the problem more deep rooted in
> > creating the symbol table?
>
> When this happens, are the two lines in different files?
I just can't get this to happen. If two items in a row have the same
PC, we should never be picking the first of the two.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer