From: Scott Merrilees <Sm@cerberus.bhpese.oz.au>
To: rc@hawkwind.utcs.toronto.edu
Subject: Re: rc under hp-ux
Date: Tue, 12 Jan 1993 19:27:47 -0500 [thread overview]
Message-ID: <199301130027.AA05376@cerberus.bhpese.oz.au> (raw)
In-Reply-To: Your message of "Tue, 12 Jan 93 16:57:37 EST." <9301121657.aa22344@golem.waterloo.on.ca>
>>From: Scott Merrilees <Sm@cerberus.bhpese.oz.au>
>>We have aquired a hp 9000/817 running hp-ux A.09.00, and I started
>>my usual porting sequence, compile rc. Unfortunately, it doesn't
>>work. More specifically stdargs/varargs seems to be playing up.
>>Compiling -O causes the compiler to barf on print.c, compiling -g
>>completes, but then execution results in core dumps.
>
>If I had to guess I would say that this is the fact that rc
>tries to save a va_list in a struct and pass it around. I had
>the same problem on another system. I don't know if what rc is
>doing is legit. according to ANSI, but I also don't quite know
>how to change it so that it doesn't do that.
This is what I have found, rc core dumps because format->args is zero.
Sm
next prev parent reply other threads:[~1993-01-13 0:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-01-12 7:12 Scott Merrilees
1993-01-12 21:57 ` David J. Fiander
1993-01-13 0:27 ` Scott Merrilees [this message]
1993-01-13 6:06 Scott Merrilees
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=199301130027.AA05376@cerberus.bhpese.oz.au \
--to=sm@cerberus.bhpese.oz.au \
--cc=rc@hawkwind.utcs.toronto.edu \
/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).