🚀 go-pugleaf

In article <1992Jan23.170311.3952@cherokee.uswest.com> dir@lookout.uswest.com (Daniel I. Rosenblatt) writes:
>In article <1992Jan22.233901.29599@mprgate.mpr.ca>, murphy@photon.mpr.ca (Gail Murphy) writes:
+> We are experiencing segmentation violations when we attempt to use rpc
+> calls from a program compiled with gcc (1.37.1). This is on a SparcStation.
+
+Try adding -fwritable-strings to the gcc command line.
+Gcc puts constant strings into read-only memory and there are
+some anti-social libc.a routines that try to write to their string

Most notably, 'mktemp' and the casual
'char *tmp = "IMGOINGTOBOMBXXXXXX"' type of declaration.

Other than that there's the infamous 'ioctl' definitions in the
include files, and the even worse old cpp string concatenation in
the 'rpc' code libraries. The '-traditional' option would also be
useful in some of these cases.(in some cases one would meet these in
trying to compile the code, in others its only during execution does
one wonder why there's so many core droppings all over the file
system).

-- 

John Clark
jclark@ucsd.edu