2010.02.26 08:11 "[Tiff] Patch for tif_unix.c", by Eric Doenges
- 2010.02.26 14:30 "Re: [Tiff] Patch for tif_unix.c", by Edward Lam
-
2010.02.26 17:05 "Re: [Tiff] Patch for tif_unix.c", by Bob Friesenhahn
- 2010.02.26 17:43 "Re: [Tiff] Patch for tif_unix.c", by Edward Lam
-
2010.03.02 08:14 "Re: [Tiff] Patch for tif_unix.c", by Eric Doenges
- 2010.03.02 14:11 "Re: [Tiff] Patch for tif_unix.c", by Toby Thain
- 2010.03.02 14:21 "Re: [Tiff] Patch for tif_unix.c", by Edward Lam
2010.03.02 16:51 "Re: [Tiff] Patch for tif_unix.c", by Scott Ribe
> e.g. if the user hit ^C
Even then, would a well-behaved app quit mid-output and leave a corrupted file behind? Or would it finish writing the current image?
Remember, if the app does not install a signal handler, ^C will cause an immediate exit. If libtiff gets EINTR because of ^C, it means the app is interested in cleaning up & exiting gracefully.
--
Scott Ribe
scott_ribe@killerbytes.com
http://www.killerbytes.com/
(303) 722-0567 voice