[comp.sys.next] bug?

t68@nikhefh.nikhef.nl (Jos Vermaseren) (06/28/91)

I believe the following to be a bug in the caching of
NeXTstep (2.0):
1:	I have a program in the bin directory.
2:	I run the program
3:	I copy a newer version of the program to the
	bin directory to overwrite the old version.
4:	I run the program --> still the old version.
It doesn't do this with data files, only with executables,
as far as I can tell.
Is this a bug or a feature?
Has it been altered in 2.1 or later?

Jos Vermaseren
t68@nikhef.nl

coco@cbnewsl.cb.att.com (felix.a.lugo) (06/29/91)

In article <1261@nikhefh.nikhef.nl> t68@nikhefh.nikhef.nl (Jos Vermaseren) writes:
| I believe the following to be a bug in the caching of
| NeXTstep (2.0):
| 1:	I have a program in the bin directory.
| 2:	I run the program
| 3:	I copy a newer version of the program to the
| 	bin directory to overwrite the old version.
| 4:	I run the program --> still the old version.
| It doesn't do this with data files, only with executables,
| as far as I can tell.
| Is this a bug or a feature?
| Has it been altered in 2.1 or later?
| 
| Jos Vermaseren
| t68@nikhef.nl

	I've seen this happen!  It occured while playing with the -object
	option of cc (ld?).  I compiled a small program using this option
	and ended up with an executable which was ~ 4000 bytes.  When I
	modified the source, recompiled (including -object), and executed
	it, I got the output from the previous version (I had changed some
	printf statements)!  I made more changes, believing I had done
	something wrong before, but the same thing happened!

	A reboot fixed(?) the executable/problem.  Now I only use -object
	when I complete a project.  I've never seen this happen in any other
	situation, so it might be coincidental!!!!!!

===============================================================================
Felix A. Lugo

E-Mail: (NeXTmail preferred)
   AT&T Bell Laboratories, Naperville, IL	Felix_A_Lugo@ATT.COM
						coco@ihcoco.att.com
   AT&T NeXT User Group				nug@ihcoco.att.com
   T.Y.C. Software, Lisle, IL			coco@ihtyc.att.com
===============================================================================