Mirror of the gdb mailing list
 help / color / mirror / Atom feed
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: Thu, 27 Feb 2003 23:33:00 -0000	[thread overview]
Message-ID: <20030227233345.GA18807@nevyn.them.org> (raw)
In-Reply-To: <m3u1epibxi.fsf@bfnet.com>

On Thu, Feb 27, 2003 at 02:41:29PM -0800, David Wuertele wrote:
> I've tried all manner of experiments, including (gasp!) reading the
> GDB manual, but I can't seem to get line number info compiled into my
> executables.  Check this out:
> 
> # gcc -o hello -g -g3 -ggdb -ggdb3 -static hello.c
> # /usr/local/bin/gdb hello
> GNU gdb 5.3
> Copyright 2002 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for details.
> This GDB was configured as "mipsel-pc-linux-gnu"...
> (gdb) list hello.c:26
> 21	{
> 22	  int j;
> 23	
> 24	  for (i=0; i<2; i++) {
> 25	    for (j=0; j<2; j++) {
> 26	      printf ("Hello, World! (%d,%d)\n", i, j);
> 27	    }
> 28	  }
> 29	
> 30	  return 0;
> (gdb) b hello.c:26
> No line 26 in file "hello.c".

What does "info source" say?

> (gdb) 
> 
> What gives?!?  GDB can list line 26 of hello.c.  But it claims there
> is 'No line 26 in file "hello.c".' !?!
> 
> 

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-02-27 23:33 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 [this message]
2003-02-27 23:57     ` David Wuertele
2003-02-28  0:08       ` Daniel Jacobowitz
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=20030227233345.GA18807@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