From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from pippin.tausq.org (gandalf.tausq.org [64.81.244.94]) by dsl2.external.hp.com (Postfix) with ESMTP id 60B914829 for ; Sun, 12 Jan 2003 20:13:49 -0700 (MST) Date: Sun, 12 Jan 2003 19:11:09 -0800 From: Randolph Chung To: Matthew Wilcox Cc: Luigi Gangitano , parisc-linux@lists.parisc-linux.org Subject: Re: [parisc-linux] Issues with seteuid()? Message-ID: <20030113031109.GI1177@tausq.org> Reply-To: Randolph Chung References: <1042386569.3329.4.camel@luigi> <20030113030635.I26554@parcelfarce.linux.theplanet.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20030113030635.I26554@parcelfarce.linux.theplanet.co.uk> Sender: parisc-linux-admin@lists.parisc-linux.org Errors-To: parisc-linux-admin@lists.parisc-linux.org List-Help: List-Post: List-Subscribe: , List-Id: parisc-linux developers list List-Unsubscribe: , List-Archive: > I wonder how it can be a problem at all. The kernel implements only > sys_setresuid() and i would imagine that glibc implements both > seteuid() and setresuid() in terms of this system call. > > Perhaps someone who's willing to touch glibc would care to comment? seteuid() works fine in simple tests. i don't think it's seteuid... something else is broken. can someone provide a simple test case for the segfault? randolph -- Randolph Chung Debian GNU/Linux Developer, hppa/ia64 ports http://www.tausq.org/