Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: mukeshgct@hotpop.com
Cc: gdb@sources.redhat.com
Subject: Re: ptype of prototype of a funtion
Date: Wed, 17 Mar 2004 05:19:00 -0000	[thread overview]
Message-ID: <20040317051906.3A8AB4B104@berman.michael-chastain.com> (raw)

Hello Murugesan,

Yes, this is everything I need, thanks.

The function PEM_write_PKCS8 is in a library.  Debugging information
("gcc -g ...") takes more disk space, so most libraries are built
without debugging information.

You can look at the place where you obtained the "crypto" lib and
the "ssl" lib and see if there are debugging versions available.
If you built these libraries yourself from source code, then you
can rebuild them with -g ("CFLAGS=-g").  If you did not build these
libraries yourself, then you have to find the person who installed
these libraries and ask them for a debugging version.

Usually, you can debug your program effectively even if the libraries
do not have debugging information.  You just can't debug the
library itself.

Michael C


             reply	other threads:[~2004-03-17  5:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-17  5:19 Michael Elizabeth Chastain [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-03-18 19:52 Michael Elizabeth Chastain
2004-03-16 14:16 Michael Elizabeth Chastain
2004-03-17  4:20 ` murugesan
2004-03-17  4:35   ` Ramana Radhakrishnan
2004-03-17  5:58     ` murugesan
2004-03-18  4:46       ` murugesan
2004-03-16 11:31 murugesan
2004-03-12 15:39 Michael Elizabeth Chastain
2004-03-12  7:53 murugesan
2004-03-12 15:39 ` Daniel Jacobowitz
2004-03-16  3:58   ` murugesan
2004-03-16 10:39     ` Muthukumar

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=20040317051906.3A8AB4B104@berman.michael-chastain.com \
    --to=mec.gnu@mindspring.com \
    --cc=gdb@sources.redhat.com \
    --cc=mukeshgct@hotpop.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