Path: utzoo!utgpu!cunews!bnrgate!brtph3!brchh104!brchs1!bnr.ca!rice.edu!sun-spots-request
From: ivan!jhc@iris.brown.edu (James H. Coombs)
Newsgroups: comp.sys.sun
Subject: Re: Need Help with RPC
Keywords: Networks
Message-ID: <2245@brchh104.bnr.ca>
Date: 2 Apr 91 15:00:00 GMT
Sender: news@brchh104.bnr.ca
Organization: Sun-Spots
Lines: 20
Approved: Sun-Spots@rice.edu
X-Original-Date: 1 Apr 91 18:41:41 GMT
X-Refs:  Original: v10n66
X-Sun-Spots-Digest: Volume 10, Issue 66, message 7
X-Note: Submissions: sun-spots@rice.edu, Admin: sun-spots-request@rice.edu

In article <2190@brchh104.bnr.ca> tjelks@stl-08sima.army.mil (Tammie D. Jelks) writes:

>client/server program using rpcgen to generate the server and the client.
>
>When I run it on the SUN-4, a memory fault core dump appeared.  A trace
>was ran against the core, and it gave me a SIGSEGV error message.  I was
>told that the data alignment on the SUN-4 was very strict, but not on the
>SUN-3 and that the 16 bit buffer was full.  
>
>How do I go about fixing the data alignment? or How do I take care of this
>problem.

I have had no problems with Sun's RPC on a variety of Sun 4s, SPARCs, Mac
IIs, etc.  RPC uses XDR, which handles data alignment.  You might look for
NIL pointers in your data.  xdr_pointer() can handle them, but
xdr_reference() cannot.  Also, watch out for strings.  If you use
xdr_string() on a NIL (as opposed to ""), then you can expect SEGV.

If this does not help, you might post more information--at least your RPC
program.