Re: error running cygcheck 1.32

[Kevin Van Workum <vanw at nist dot gov>]

On Tue, 8 Jul 2003, Igor Pechtchanski wrote:

> On Tue, 8 Jul 2003, Kevin Van Workum wrote:
>
> > On Tue, 8 Jul 2003, Igor Pechtchanski wrote:
> >
> > > On Tue, 8 Jul 2003, Kevin Van Workum wrote:
> > >
> > > > I have cygcheck version 1.32. If I run cygcheck -s, a window titled
> > > > "Program Error" pops up. The window says "cygcheck.exe has generated
> > > > errors and will be closed by Windows. You will need to restart the
> > > > program. An error log is being created." cygcheck stops printing
> > > > information after the PATH is printed. The output is below.
> > > >
> > > > What causes this problem?
> > > > How can I fix it?
> > > > Where is this error log created?
> > > >
> > > > <<begin cygcheck output>>
> > > >[snip]
> > >
> > > Kevin,
> > >
> > > After printing the PATH, the later versions of cygcheck attempt to execute
> > > "id.exe" to get user information.  For some reason this fails for you.
> > > Can you try executing "id" and "CYGWIN=nontsec id" on the command line and
> > > posting the output?  Try also running "cygcheck -s" under strace and
> > > seeing what is the last system call cygcheck makes before it fails.
> > >       Igor
> >
> > Running "id" prints:
> > uid=1003(vanw) gid=513(None) groups=513(None),544(Administrators),545(Users)
> >
> > Running "CYGWIN=nontsec id" prints:
> > uid=1003(vanw) gid=513(None) groups=513(None)
>
> Well, this shows that you can run "id" with no crashes...
>
> > I'm not sure what to look for in the strace output. Below is the
> > last few lines and attached is the entire output of "strace cygcheck -s".
> > [snip]
> > Kevin Van Workum, PhD
>
> The included strace lines look like a normal termination sequence...
> However, the strace output you've attached says
>
>    Program name: c:\cygwin\bin\id.exe (2476)
>
> at the top, which means you ran "id", not "cygcheck -s" under strace.
> The idea was to try to get "cygcheck -s" to crash under strace, and see
> what the last action before the crash would be.

Yeah, I noticed that too, but I really did run "strace /usr/bin/cygcheck
-s".

> Could you also run "cygcheck -s" under gdb and see if it crashes?  If it
> does, try to get a backtrace.
> 	Igor

After running "cygcheck -s" under gdb, it exited normally. I then realized
that the problem is with my terminal under X. Running "cygcheck
-s" from a non-X terminal works (rxvt). Does that sound plausible? Maybe
there's a problem with X?

Anyways, thanks for the help.

Kevin.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/