* breakpoint on a non-executable line
[not found] <3F4E35CB.3080300@redhat.com>
@ 2003-08-28 19:00 ` Jafa
2003-08-28 19:02 ` Daniel Jacobowitz
0 siblings, 1 reply; 3+ messages in thread
From: Jafa @ 2003-08-28 19:00 UTC (permalink / raw)
To: gdb
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.
Nick
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: breakpoint on a non-executable line
2003-08-28 19:00 ` breakpoint on a non-executable line Jafa
@ 2003-08-28 19:02 ` Daniel Jacobowitz
2003-08-28 20:20 ` Jafa
0 siblings, 1 reply; 3+ messages in thread
From: Daniel Jacobowitz @ 2003-08-28 19:02 UTC (permalink / raw)
To: Jafa; +Cc: gdb
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: breakpoint on a non-executable line
2003-08-28 19:02 ` Daniel Jacobowitz
@ 2003-08-28 20:20 ` Jafa
0 siblings, 0 replies; 3+ messages in thread
From: Jafa @ 2003-08-28 20:20 UTC (permalink / raw)
To: Daniel Jacobowitz; +Cc: gdb
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
>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2003-08-28 20:20 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <3F4E35CB.3080300@redhat.com>
2003-08-28 19:00 ` breakpoint on a non-executable line Jafa
2003-08-28 19:02 ` Daniel Jacobowitz
2003-08-28 20:20 ` Jafa
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).