From:	lauras AT softhome DOT net
Date:	Sun, 7 Jan 2001 15:55:32 +0200
To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Cc:	lauras AT softhome DOT net, djgpp-workers AT delorie DOT com,
	Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
Subject:	Re: Bug in lstat() - wrong arguments to FSEXT
Message-ID:	<20010107155532.A4259@lauras.lt>
References:	<20010107141016 DOT A314 AT lauras DOT lt> <Pine DOT SUN DOT 3 DOT 91 DOT 1010107141348 DOT 25836D-100000 AT is>
Mime-Version:	1.0
User-Agent:	Mutt/1.2.5i
In-Reply-To:	<Pine.SUN.3.91.1010107141348.25836D-100000@is>; from eliz@is.elta.co.il on Sun, Jan 07, 2001 at 02:20:14PM +0200
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Sun, Jan 07, 2001 at 02:20:14PM +0200, Eli Zaretskii wrote:
> This will only work if `path' is on the stack with the other arguments 
> passed to `stat', because the FSEXT hook expects to find the same 
> argument list on its stack when it is called.  `path' satisfies this 
> requirement, because it is `stat's argument.  But `real_path' is a local 
> variable inside `stat' (now `lstat'), so it is further down the stack, 
> far from the struct stat buffer which sits near `path' on the stack.
> 

Oh, thanks for explanation. But I still feel not very confident 
about how should I fix it. Would passing `real_path' itself 
instead of `&real_path' work?

Laurynas
  

- Raw text -