linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alina Valea <avalea@home.ro>
To: linux-c-programming@vger.kernel.org
Subject: xdr functions cause segmentation fault
Date: 7 Jun 2002 05:59:53 -0000	[thread overview]
Message-ID: <20020607055953.2129.qmail@relay1.home.ro> (raw)



Hello everybody,

I have one client program that sends a message string to a
server program, which echoes it back to the client.

The server side: ... char * print_message(char *message) {

printf("Arg: %s\n",message); return message; }

void main() {

... if(registerrpc (PRINTPROG,PRINTVERS,PRINTPROC_NUM,
print_message,xdr_message,xdr_message, "visible")==-1) { ...}
svc_run(); }

The client side: ... char
*tokens[]={"message1","message2","message3","message4"}; char
result[20];

while(1) { i=counter++ % 4; if( (error_code=callrpc(
"localhost", PRINTPROG, PRINTVERS, PRINTPROC_NUM, xdr_message,
tokens[i], xdr_message, result))!=RPC_SUCCESS) 	{...}
printf("client: %s\n",result); }

where bool_t xdr_message(XDR *xdrs, char *message) { return
(xdr_string(xdrs,&message,20)); }

The problem is I always get a segmentation fault on the
server side (using any of the xdr_message(),
xdr_wrapstring(),xdr_string()) after the receipt and printing
of the first string. The only time the server doesn't crash is
when using xdr_message() on the client side, and
xdr_wrapstring() on the server side. Except that the server
won't print the right string, but 'I', over and over.

Even more, I get a gcc warning on compiling the client: args
5,7 of callrpc of incompatible pointer type.

Thanks for your help, Alina


----

Home, no matter how far...
http://www.home.ro

                 reply	other threads:[~2002-06-07  5:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20020607055953.2129.qmail@relay1.home.ro \
    --to=avalea@home.ro \
    --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).