> > it.  If you can, debugging Cygwin via gdb would be the best way to go.
> > Alternatively, if you can't do that, calling gcc indirectly through 
> > strace in your IDE environment would provide some trace information 
> 
> 
        Here is a strace snippet right around the error's occurrence:

        09:19:17 [main] make 384 dtable::build_fhandler: fd 3, fh 0x61550820
        09:19:17 [main] make 384 dtable::build_fhandler: fd 4, fh 0x61550960
        09:19:17 [main] make 384 fhandler_base::init: created new
fhandler_base for handle 0xD8
        09:19:17 [main] make 384 fhandler_base::init: created new
fhandler_base for handle 0x154
        09:19:17 [main] make 384 make_pipe: 0 = make_pipe ([3, 4], 16384,
0x10000)
        09:19:17 [main] make 384 _close: close (4)
        09:19:17 [main] make 384 fhandler_base::close: closing '(null)'
handle 0x154
        09:19:17 [main] make 384 dtable::not_open: in not_open,
fds=0x61550128 fd=4 fds[fd]=1632962912 res=0 size=32
        09:19:17 [main] make 384 _close: 0 = close (4)
        09:19:17 [main] make 384 fhandler_base::set_close_on_exec: set
close_on_exec for (null) to 1
        09:19:17 [main] make 384 _fcntl: 0 = fcntl (3, 2, 0x1)
        09:19:17 [main] make 384 set_process_mask: old mask = 0, new mask =
1804007
        09:19:17 [main] make 384 dtable::not_open: in not_open,
fds=0x61550128 fd=0 fds[fd]=1632961224 res=0 size=32
        09:19:17 [main] make 384 dtable::build_fhandler: fd -1, fh
0x61550960
        09:19:17 [main] make 384 fhandler_base::dup: in fhandler_base dup
        09:19:17 [main] make 384 fhandler_base::dup: dup(unknown disk file)
failed, handle 0, Win32 error 6
        09:19:17 [main] make 384 seterrno_from_win_error:
/usr/src/cygwin/winsup/cygwin/fhandler.cc:926 errno 6
        09:19:17 [main] make 384 geterrno_from_win_error: windows error 6 ==
errno 9
        09:19:17 [main] make 384 vfork: 0 = vfork()
        09:19:17 [main] make 384 vfork: exiting vfork, res 0

        I'm not sure how far back is relevant to the vfork's setting up for
the make-file's "echo" command that occurs next vs. cleaning up from
checking dependencies (the previous task make was doing)

        the build_fhandler: fd=-1 is expected; that's a new dtable being
built, so aside from that the error occurring in fhandler_base::dup (which
we already knew) there's no new info.

        Larry, would posting a complete strace be useful?  What might I look
for in the strace?

        Warm Regards,
        Chris


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Reply via email to