From: Daniel Jacobowitz <drow@mvista.com>
To: David Wuertele <dave-gnus@bfnet.com>
Cc: gdb@sources.redhat.com
Subject: Re: gdb 5.3 doesn't find line numbers
Date: Fri, 28 Feb 2003 00:08:00 -0000 [thread overview]
Message-ID: <20030228000759.GA19664@nevyn.them.org> (raw)
In-Reply-To: <m3adghjnw6.fsf@bfnet.com>
On Thu, Feb 27, 2003 at 03:37:45PM -0800, David Wuertele wrote:
> Me> (gdb) b hello.c:26
> Me> No line 26 in file "hello.c".
>
> Daniel> What does "info source" say?
>
> (gdb) info source
> Current source file is hello.c
> Compilation directory is /root
> Located in /root/hello.c
> Contains 31 lines.
> Source language is c.
> Compiled with DWARF 2 debugging format.
> Does not include preprocessor macro info.
> (gdb) d'oh!
>
> OK, looks like I used the wrong debug flags during compile.
> D'oh again.
Does that mean you can "break hello.c:26" now? The session you posted
before should have worked...
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-02-28 0:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-26 22:50 relative file paths? christopher j bottaro
2003-02-27 23:31 ` gdb 5.3 doesn't find line numbers David Wuertele
2003-02-27 23:33 ` Daniel Jacobowitz
2003-02-27 23:57 ` David Wuertele
2003-02-28 0:08 ` Daniel Jacobowitz [this message]
2003-02-28 0:23 ` David Wuertele
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030228000759.GA19664@nevyn.them.org \
--to=drow@mvista.com \
--cc=dave-gnus@bfnet.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox