linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darío Mariani" <dmarian@fi.uba.ar>
To: "Ramanan, Venkat (MED)" <Venkat.ramanan@geind.ge.com>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: Debug flag for libraries.
Date: Tue, 01 Jul 2003 12:00:13 -0300	[thread overview]
Message-ID: <3F01A1FD.8020903@fi.uba.ar> (raw)
In-Reply-To: DD9E117A8BE9F34FA4130376EC9C1F6A048B48B7@BANMLVEM01.e2k.ad.ge.com

   In general you will have no problems, I did not work with static 
libraries, but with shared ones never had a problem. I do not think that 
recompiling the libraries with debug info provides much help, unless the 
libraries are buggy.

Ramanan, Venkat (MED) wrote:
> Hi all,
> 
> I need to compile a program with the debug flag "-g". The program uses some (static) libraries which have already been compiled without the "-g" flag. So, if I need all the debugging information ( line numbers etc. ) even from the libraries, do I need to recompile the libraries? Or is the "-g" flag just for the program, enough to bring all info?
> 
> I use "gcc" and "gdb".
> 
> What is the "correct" thing to do? Any advice would be greatly appreciated.
> 
> Thanks in advance,
> Venkat.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 



  parent reply	other threads:[~2003-07-01 15:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-01  5:53 Debug flag for libraries Ramanan, Venkat (MED)
2003-07-01 11:02 ` Glynn Clements
2003-07-02 18:48   ` Elias Athanasopoulos
2003-07-01 15:00 ` Darío Mariani [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-07-03  7:24 Ramanan, Venkat (MED)

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=3F01A1FD.8020903@fi.uba.ar \
    --to=dmarian@fi.uba.ar \
    --cc=Venkat.ramanan@geind.ge.com \
    --cc=linux-c-programming@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).