rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Tim Goodwin <tgoodwin@cygnus.co.uk>
To: broman@nosc.mil
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: "rc" shell maintainer?
Date: Fri, 6 Feb 1998 13:00:37 -0500	[thread overview]
Message-ID: <Ml0AANpP2zTdVAwA@nan.cygnus.co.uk> (raw)
In-Reply-To: <19980205214831.17917.qmail@np.nosc.mil>

Thanks for the bug report.

> I tried out rc-1.5b2 on my SunOS 4.1.3 (with most Sun patches) machine
> and gcc-2.7.2, and I got a core dump during trip.  Any suggestions?

This change looks wrong to me.

> - -		ngroups = getgroups(0, (gid_t *)0);
> +		ngroups = getgroups(0, (GETGROUPS_T *)0);

There was a bug in rc-1.5b2, but the fix for 1.5b3 will be as appended.

(Incidentally, I finally tracked this one down using ElectricFence.
Thanks to Bruce Perens for a marvellous piece of software.)

Tim.

--- release/rc-1.5b2/which.c	Mon Jul  7 16:43:32 1997
+++ rc-1.5b3/which.c	Thu Feb  5 15:23:59 1998
@@ -88,7 +88,7 @@
 		gid = getegid();
 #if HAVE_GETGROUPS
 		ngroups = getgroups(0, (gid_t *)0);
-		gidset = malloc(ngroups * sizeof(gid_t));
+		gidset = malloc(ngroups * sizeof(GETGROUPS_T));
 		if (!gidset)
 			uerror("malloc");
 		else


  reply	other threads:[~1998-02-06 22:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-02-04 21:23 Vincent Broman
1998-02-05  1:17 ` Tom Culliton
1998-02-05 11:46 ` Tim Goodwin
1998-02-05 21:48   ` Vincent Broman
1998-02-06 18:00     ` Tim Goodwin [this message]
1998-02-06 22:54       ` Vincent Broman
1998-02-09 20:31       ` Vincent Broman
1998-02-09 23:45       ` Vincent Broman
1998-02-10 23:26         ` Tom Culliton
1998-02-11 10:45           ` Tim Goodwin
1998-02-11 22:23             ` Tom Culliton
1998-02-12 10:23               ` Tim Goodwin
1998-02-11 21:55           ` Vincent Broman
1998-02-05  5:01 smarry
1998-02-05 15:25 ` Tom Culliton
1998-02-06 17:45 ` Tim Goodwin
1998-02-05 19:59 smarry

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=Ml0AANpP2zTdVAwA@nan.cygnus.co.uk \
    --to=tgoodwin@cygnus.co.uk \
    --cc=broman@nosc.mil \
    --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).