public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: Igor Peshansky <pechtcha@cs.nyu.edu>
To: The Cygwin-Talk Maiming List <cygwin-talk@cygwin.com>
Subject: RE: cygwin + windows update = lock up (W2K SP4)
Date: Wed, 03 May 2006 12:21:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.63.0605030819580.8518@access1.cims.nyu.edu> (raw)
In-Reply-To: <008f01c66e9d$adf5b640$a501a8c0@CAM.ARTIMI.COM>

On Wed, 3 May 2006, Dave Korn wrote:

> On 02 May 2006 22:11, Christopher Faylor wrote:
>
> > On Tue, May 02, 2006 at 01:59:12PM -0700, Shankar Unni wrote:
> >> Brian Dessent wrote:
> >>> It's a real shame that Russinovich is apparently aware of this
> >>> defect but remains uninterested in dealing with it past calling it a
> >>> Cygwin deficiency.
> >>
> >> Time for a Russinovitch-CGF cage match!
> >>
> >> (First one who tries to debug the problem loses..)
> >
> > If either Corinna or I could reproduce the problem it would be fixed
> > by now.
> >
> > cgf
>
>   Attached please find PPAST!
>
>   Compile with "gcc -g -O0 -mno-cygwin cygdeath.c -o cygdeath -l ntdll"
>
>   Runs with one arg: windows pid of any handy cygwin process, such as
> the shell you've just used to compile it in, or an instance of cat, or
> whatever.
>
>   Press any key when it tells you.  Watch csrss and chosen cygwin
> process start to thrash.
>
>     cheers,
>       DaveK

[Attachment: cygdeath.c (2KB) deleted]

My only question is: why isn't it using the undocumented WinAPI function
ProcessDropHippo() (the 48-argument version)?

IOW, aren't you on the wrong list for this useful technical discussion?
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_	    pechtcha@cs.nyu.edu | igor@watson.ibm.com
ZZZzz /,`.-'`'    -.  ;-;;,_		Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-'		old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"

  reply	other threads:[~2006-05-03 12:21 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <003e01c66e19$caab4ea0$a501a8c0@CAM.ARTIMI.COM>
     [not found] ` <4457C0DB.F0093A96@dessent.net>
2006-05-02 20:59   ` Shankar Unni
2006-05-02 21:10     ` Christopher Faylor
2006-05-03 10:38       ` Dave Korn
2006-05-03 12:21         ` Igor Peshansky [this message]
2006-05-03 12:33           ` Gary R. Van Sickle
2006-05-03 13:43             ` Dave Korn
2006-05-03  9:12 Ludovic Drolez
2006-05-03 15:59 ` Christopher Faylor
2006-05-03 17:30   ` Dave Korn
2006-05-03 17:46     ` Christopher Faylor
2006-05-03 18:14       ` Dave Korn
2006-05-13 22:49       ` Christopher Faylor
2006-05-19 12:03 John Hackett
2006-05-19 12:13 ` Danilo Turina
2006-05-19 12:15 ` Dave Korn
2006-05-19 12:30   ` John Hackett
2006-05-19 12:44     ` Dave Korn
2006-05-19 15:12     ` mwoehlke
2006-05-19 15:18       ` Dave Korn
2006-05-19 15:25         ` mwoehlke
2006-05-19 23:22         ` Gary R. Van Sickle
2006-05-22 12:27           ` Dave Korn
2006-05-19 15:26     ` Christopher Faylor
2006-05-19 15:46       ` Dave Korn
2006-05-20  1:01         ` Igor Peshansky
2006-05-20  1:03           ` Christopher Faylor
2006-05-20  1:14             ` Igor Peshansky
2006-05-20  1:34         ` Igor Peshansky
2006-05-20  1:35           ` Igor Peshansky

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=Pine.GSO.4.63.0605030819580.8518@access1.cims.nyu.edu \
    --to=pechtcha@cs.nyu.edu \
    --cc=cygwin-talk@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).