Re: breakpoint on a non-executable line

["Jafa" <jafa@silicondust.com>]

Hi Daniel,

> Do you know if this is a change?

yes, we moved to the top of trunk in December last year and started to see
the problem. The previous version was about 2001 and worked as I would
expect.

I can check the exact dates if you like, or I don't mind working through
it... I just wanted to make sure it wasn't a deliberate change.

Thanks

Nick


----- Original Message ----- 
From: "Daniel Jacobowitz" <drow@mvista.com>
To: "Jafa" <jafa@silicondust.com>
Cc: <gdb@sources.redhat.com>
Sent: Thursday, August 28, 2003 12:02 PM
Subject: Re: breakpoint on a non-executable line


> *This message was transferred with a trial version of CommuniGate(tm) Pro*
> On Thu, Aug 28, 2003 at 12:00:02PM -0700, Jafa wrote:
> > Hi all,
> >
> > I am seeing a problem/feature? of gdb (June top of trunk) where if you
issue
> > a command to set a breakpoint on a non-executable line it will return
the
> > line specified, regardless of where it actually set.
> >
> > For example:
> >
> > (gdb) b  /ubicom/toolchain/src/ld/ldmain.c:1
> > Breakpoint 2 at 0x41b800: file /ubicom/toolchain/src/ld/ldmain.c, line
1.
> >
> > (It actually put the breakpoint on line 167).
> >
> > Is this the desired behavior? I would have expected it to return
success -
> > line 167.
>
> Do you know if this is a change?
>
> -- 
> Daniel Jacobowitz
> MontaVista Software                         Debian GNU/Linux Developer
>