From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30135 invoked by alias); 17 Mar 2004 05:19:09 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 30007 invoked from network); 17 Mar 2004 05:19:08 -0000 Received: from unknown (HELO barry.mail.mindspring.net) (207.69.200.25) by sources.redhat.com with SMTP; 17 Mar 2004 05:19:08 -0000 Received: from user-119a90a.biz.mindspring.com ([66.149.36.10] helo=berman.michael-chastain.com) by barry.mail.mindspring.net with esmtp (Exim 3.33 #1) id 1B3TSJ-0000v1-00; Wed, 17 Mar 2004 00:19:03 -0500 Received: by berman.michael-chastain.com (Postfix, from userid 502) id 3A8AB4B104; Wed, 17 Mar 2004 00:19:06 -0500 (EST) To: mukeshgct@hotpop.com Subject: Re: ptype of prototype of a funtion Cc: gdb@sources.redhat.com Message-Id: <20040317051906.3A8AB4B104@berman.michael-chastain.com> Date: Wed, 17 Mar 2004 05:19:00 -0000 From: mec.gnu@mindspring.com (Michael Elizabeth Chastain) X-SW-Source: 2004-03/txt/msg00155.txt.bz2 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