Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Stefano Sabatini <stefano.sabatini-lala@poste.it>
To: gdb Mailing List <gdb@sources.redhat.com>
Subject: Re: Single stepping and "no line information"
Date: Mon, 08 Sep 2008 13:46:00 -0000	[thread overview]
Message-ID: <20080908134502.GB19559@geppetto> (raw)
In-Reply-To: <20080908133953.GA19559@geppetto>

On date Monday 2008-09-08 15:39:53 +0200, Stefano Sabatini wrote:
> I'm debugging an application which use a shared lib.
> 
> That library has been compiled on my system, and I added to the CFLAGS
> used the -ggdb -O0 flags, so I'm quite sure that lib should contain
> the source line symbol informations.
> 
> Nonetheless when I try to step into the library functions I get:
> 
> (gdb) s
> Single stepping until exit from function su_clone_start, 
> which has no line number information.
> 
> stefano@geppetto ~/s/ptlib> gdb --version
> GNU gdb 6.8-debian
> Copyright (C) 2008 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "i486-linux-gnu".
> 
> Why gdb can't find the source line informations?
> 
> How can I verify (e.g. with a commandline tool) wether that
> information is present directly analyzing the library files?

I tried with:
nm --line-numbers libfoo.so | grep foo

and indeed I get the symbol with its line and file information.

Could it be a gdb bug?

Regards.


  reply	other threads:[~2008-09-08 13:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-08 13:41 Stefano Sabatini
2008-09-08 13:46 ` Stefano Sabatini [this message]
2008-09-08 15:03 ` Paul Pluzhnikov

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=20080908134502.GB19559@geppetto \
    --to=stefano.sabatini-lala@poste.it \
    --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