Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs
Date: Mon, 26 Jul 2004 11:15:21 -0400 (EDT)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: Chris January <chris AT atomice DOT net>
cc: cygwin AT cygwin DOT com
Subject: RE: cat /proc/registry/HKEY_PERFOMANCE_DATA/@ hangs
In-Reply-To: <001001c4730f$fadb3470$0207a8c0@avocado>
Message-ID: <Pine.GSO.4.58.0407261042030.6434@slinky.cs.nyu.edu>
References: <001001c4730f$fadb3470$0207a8c0 AT avocado>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Scanned-By: MIMEDefang 2.39

On Mon, 26 Jul 2004, Chris January wrote:

> > Yes, I'm still seeing the segfault in the latest snapshot,
> > but only when run under gdb or strace.  Here are some sample tests:
> >
> > $ cat /proc/registry/HKEY_PERFORMANCE_DATA/\@ > e.out
> > cat: /proc/registry/HKEY_PERFORMANCE_DATA/@: No such file or directory
> > $ # no segfault
> > $ strace -o cat_HKPD.strace cat /proc/registry/HKEY_PERFORMANCE_DATA/\@ > e.out
> > 2262669 [main] cat 2400 handle_exceptions: Exception: STATUS_ACCESS_VIOLATION
> > 2264445 [main] cat 2400 open_stackdumpfile: Dumping stack trace to cat.exe.stackdump
> > $
>
> I can't reproduce this with CVS. Can you?
> Chris

Yes, I can.  I just compiled ([1]) the latest CVS cygwin0.dll (as of
today, 14:31 UTC), then tested with the new DLL ([2]).  I get the same
exact errors (including the stackdump).  Interestingly enough, I had other
unexplained exceptions with this test approach, so I'd appreciate if
anyone points out what's wrong with it.
	Igor

[1] "cd build/i686-pc-cygwin/winsup/cygwin && make clean all"
[2] "cd test && cygstart ./bash.exe" then run the above commands from
    the prompt, where "test" is a directory containing executables
    binary-edited to use cygwin0.dll instead of cygwin1.dll, confirmed by
    cygcheck.  Note that my build was configured with --enable-debugging.
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Happiness lies in being privileged to work hard for long hours in doing
whatever you think is worth doing."  -- Dr. Jubal Harshaw

--
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/