On Wed, Aug 18, 2010 at 09:51:29PM +0800, Huang Bambo wrote: >2010/8/18 Eric Blake <ebl...@redhat.com>: >> On 08/18/2010 05:08 AM, Corinna Vinschen wrote: >>>>> Looks like this behaviour is a problem and we should better close the >>>>> old handle. ?What to do with the new one? ?Just set it to NULL and >>>>> disallow stackdumps as long as we're in a virtual path? ?Or set it to >>>>> some well known path, like Cygwin's root? >>>> >>>> /var or /tmp would be more sensible. >>> >>> Maybe, but it also costs time. ?/var and /tmp Windows paths have to be >>> generated by a full path conversion every time you call chdir() to a >>> virtual directory. >>> The Cygwin installation path (aka the root dir) is just available. >> >> Using / as the fallback during a virtual directory makes sense to me >> (there may be other permission problems if / is not writable by the >> current user, but a stack dump is a best effort attempt anyways). >> >Even in linux, you can't generate core file in virtual directory also, >so just don't generate core file if you can't write at anywhere.
Right. I don't think we need a fallback. How is this any different than what happens when you generate a core dump in linux in a read-only directory? cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
