home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!dtix!darwin.sura.net!spool.mu.edu!agate!stanford.edu!rock!concert!sas!mozart.unx.sas.com!walker
- From: walker@twix.unx.sas.com (Doug Walker)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: Help with my C program anyone?
- Message-ID: <Bxnqu9.4w6@unx.sas.com>
- Date: 13 Nov 92 13:58:57 GMT
- References: <1992Nov13.065904.1066@cs.uow.edu.au>
- Sender: news@unx.sas.com (Noter of Newsworthy Events)
- Organization: SAS Institute Inc.
- Lines: 22
- Originator: walker@twix.unx.sas.com
- Nntp-Posting-Host: twix.unx.sas.com
-
-
- In article <1992Nov13.065904.1066@cs.uow.edu.au>, u9155406@cs.uow.edu.au (Gerardo Bentancor) writes:
- |> By now, I assume that the UnLock function has unlocked the previous directory,
- |> and there is now a valid lock on the new directory, and it has become the
- |> current directory. Before my program finishes I make sure that it unlocks the
- |> new current directory.
-
- That's the problem. Your program started with a current directory
- lock, you should make sure it ends with one. When your program
- exits, the shell you invoked it from assumes that the current
- directory lock is valid; you have just freed it, so it crashes.
-
- |> Gerardo.
-
- --
- *****
- =*|_o_o|\\=====Doug Walker, Software Distiller====== BBS: (919)460-7430 =
- *|. o.| || 1200/2400/9600 Dual
- | o |// For all you do, this bug's for you!
- ======
- usenet: walker@unx.sas.com bix: djwalker
- Any opinions expressed are mine, not those of SAS Institute, Inc.
-