From: "murugesan" <mukeshgct@hotpop.com>
To: <gdb@sources.redhat.com>
Subject: Re: ptype of prototype of a funtion
Date: Thu, 18 Mar 2004 04:46:00 -0000 [thread overview]
Message-ID: <00cb01c40ca3$fb609570$4b0110ac@munco> (raw)
In-Reply-To: <1079503114.4954.30.camel@mun-co>
After realising the prototype I am passing the correct parameter but it
produces warning
Here goes my script
# cat dinesh
Script started on Thu Mar 18 10:58:12 2004
# gcc -g test.c /home/dinesh/openssl-0.9.7c/libcrypto.sl.0.9.7
/home/dinesh/openssl-0.9.7c/libssl.sl.0.9.7
test.c: In function `main':
test.c:10: warning: passing arg 3 of `PEM_read_bio_PKCS8_PRIV_KEY_INFO' from
incompatible pointer type
# gdb -q a.out
(gdb) break main
Breakpoint 1 at 0x2800: file test.c, line 9.
(gdb) r
Starting program: /home/dinesh/openssl_test/a.out
Breakpoint 1, main () at test.c:9
9 bp=BIO_new_file(PATH"/pkcs8","r");
(gdb) n
10 PEM_read_bio_PKCS8_PRIV_KEY_INFO(bp,&pkcs8,&num, "test");
(gdb) ptype PEM_read_bio_PKCS8_PRIV_KEY_INFO
type = struct pkcs8_priv_key_info_st {
int broken;
struct asn1_string_st *version;
struct X509_algor_st *pkeyalg;
struct asn1_type_st *pkey;
struct stack_st *attributes;
} *(struct bio_st *, struct pkcs8_priv_key_info_st **, int *, signed char *)
(gdb) q
The program is running. Exit anyway? (y or n) y
# cat test.c
#include <openssl/pem.h>
#define PATH "./my_temp"
main()
{
BIO *bp;
FILE *fp;
PKCS8_PRIV_KEY_INFO *pkcs8;
int num;
PEM_read_bio_PKCS8_PRIV_KEY_INFO(bp,&pkcs8,&num, "test");
}
#
script done on Thu Mar 18 10:58:52 2004
// For simplicity the program has been reduced ( parameters has not been
initialized )
Regards,
Murugesan
============================================================================
=======================
----- Original Message -----
From: murugesan
To: Ramana Radhakrishnan
Cc: gdb@sources.redhat.com
Sent: Wednesday, March 17, 2004 11:28 AM
Subject: Re: ptype of prototype of a funtion
Cool!! This is working
I have been using the one which has not been built with debug option.
I have the 2 OpenSSL 1 being built with debug option ( in different dir
) and the other without debug option ( in default location )
Thanks Ramana & Elizabeth for reminding me.
Regards,
Murugesan.
next prev parent reply other threads:[~2004-03-18 4:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-18 19:52 Michael Elizabeth Chastain
2004-03-17 5:19 Michael Elizabeth Chastain
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='00cb01c40ca3$fb609570$4b0110ac@munco' \
--to=mukeshgct@hotpop.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