From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: cat /proc/registry/HKEY_PERFOMANCE_DATA/@ hangs
Date: Wed, 14 Jul 2004 18:48:00 -0000 [thread overview]
Message-ID: <20040714184540.GZ1389@cygbert.vinschen.de> (raw)
In-Reply-To: <Pine.GSO.4.58.0407141408220.29800@slinky.cs.nyu.edu>
On Jul 14 14:29, Igor Pechtchanski wrote:
> Since Dave is not subscribed to cygwin-developers anyway, I'll continue
> this here. More below.
Ok. That's why I wrote "mildly OT".
> Can't for a while. Can you do me a favor and submit this as a fix, if you
> have a copyright assignment for Cygwin? If it makes you feel better, feel
> free to mention me in the ChangeLog as well.
David has no copyright assignment on file so far. But that doesn't matter
since the below is definitely a "trivial" patch. Just a ChangeLog entry,
please.
Corinna
> > Index: winsup/cygwin/fhandler_registry.cc
> > ===================================================================
> > RCS file: /cvs/src/src/winsup/cygwin/fhandler_registry.cc,v
> > retrieving revision 1.24
> > diff -p -u -r1.24 fhandler_registry.cc
> > --- winsup/cygwin/fhandler_registry.cc 9 Feb 2004 04:04:23 -0000 1.24
> > +++ winsup/cygwin/fhandler_registry.cc 14 Jul 2004 16:47:53 -0000
> > @@ -575,6 +575,7 @@ fhandler_registry::fill_filebuf ()
> > {
> > bufalloc += 1000;
> > filebuf = (char *) realloc (filebuf, bufalloc);
> > + size = bufalloc;
> > error = RegQueryValueEx (handle, value_name, NULL, &type,
> > (BYTE *) filebuf, &size);
> > if (error != ERROR_SUCCESS && error != ERROR_MORE_DATA)
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Co-Project Leader mailto:cygwin@cygwin.com
Red Hat, Inc.
--
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/
next prev parent reply other threads:[~2004-07-14 18:45 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 [this message]
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
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=20040714184540.GZ1389@cygbert.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).