public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Chris January" <chris@atomice.net>
To: <cygwin@cygwin.com>
Subject: RE: cat /proc/registry/HKEY_PERFOMANCE_DATA/@ hangs
Date: Mon, 26 Jul 2004 16:50:00 -0000	[thread overview]
Message-ID: <006401c47328$9e7d62c0$0207a8c0@avocado> (raw)
In-Reply-To: <Pine.GSO.4.58.0407261042030.6434@slinky.cs.nyu.edu>

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

Could you send me a copy of the stackdump and the strace output by
private mail please?

Chris


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

  reply	other threads:[~2004-07-26 15:52 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-13 14:10 Reini Urban
2004-07-13 14:30 ` Igor Pechtchanski
2004-07-13 15:09   ` Dave Korn
2004-07-13 15:19     ` Corinna Vinschen
2004-07-13 15:28       ` Dave Korn
2004-07-13 15:41         ` Igor Pechtchanski
2004-07-13 15:57           ` Dave Korn
2004-07-13 16:21             ` Igor Pechtchanski
2004-07-13 22:05               ` Yitzchak Scott-Thoennes
2004-07-13 22:20                 ` Igor Pechtchanski
2004-07-13 22:44                   ` Yitzchak Scott-Thoennes
2004-07-13 23:18                     ` Igor Pechtchanski
2004-07-14  2:23                       ` Igor Pechtchanski
2004-07-14  2:32                         ` Yitzchak Scott-Thoennes
2004-07-14  3:22               ` Igor Pechtchanski
2004-07-14 17:14                 ` Dave Korn
2004-07-14 17:17                   ` Corinna Vinschen
2004-07-14 17:28                     ` [OT] " Dave Korn
2004-07-14 18:34                       ` Dave Korn
2004-07-15  2:28                         ` Christopher Faylor
2004-07-14 18:42                       ` Developer's list archive policy - was " Larry Hall
2004-07-14 17:38                     ` Igor Pechtchanski
2004-07-14 18:30                   ` Igor Pechtchanski
2004-07-14 18:40                     ` Igor Pechtchanski
2004-07-14 18:45                     ` Dave Korn
2004-07-14 18:48                     ` Corinna Vinschen
2004-07-14 21:42                       ` Igor Pechtchanski
2004-07-19 18:36                 ` Chris January
2004-07-19 19:47                   ` Igor Pechtchanski
2004-07-19 21:56                     ` Robert Pendell
2004-07-20  0:25                       ` Igor Pechtchanski
2004-07-20 20:06                         ` Robert Pendell
2004-07-26 15:15                     ` Chris January
2004-07-26 15:52                       ` Igor Pechtchanski
2004-07-26 16:50                         ` Chris January [this message]
2004-07-14 10:58   ` Reini Urban
2004-07-14 12:39     ` Igor Pechtchanski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='006401c47328$9e7d62c0$0207a8c0@avocado' \
    --to=chris@atomice.net \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).