public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Heribert Dahms <heribert_dahms@icon-scm.com>
To: 'Troy Noble' <troy.noble@channelpoint.com>,
	"'cygwin@cygwin.com'" <cygwin@cygwin.com>
Subject: RE: broken CTRL-BREAK handling
Date: Wed, 18 Jul 2001 13:42:00 -0000	[thread overview]
Message-ID: <BF35D9C143BCCC4EB63181B67C9320C804DE17@serv-075.icon-germany.local> (raw)

Hi Troy,

for the unix-emulation-centered like me it's a non issue
and I'd turn the question into:
Is there a (standard) way of generating a JVM dump under Unix?
If so, you may try that under Cygwin.

Bye, Heribert (heribert_dahms@icon-gmbh.de)

> -----Original Message-----
> From:	Troy Noble [SMTP:troy.noble@channelpoint.com]
> Sent:	Wednesday, July 18, 2001 18:33
> To:	'cygwin@cygwin.com'
> Subject:	RE: broken CTRL-BREAK handling
> 
	[Heribert]  [snip]

> I want to go on record as saying that I'm still not convinced it's
> entirely right for the ctrl handler to swallow the CTRL-BREAK and
> turn it into a SIGINT in all cases.  Let me explain.  If I press
> CTRL-BREAK in a cmd window JVM dumps stack traces, if I do the same
> in bash/cygwin console window it doesn't.
> 
> Bottom line... that still feels broken to me if the intent is for
> cygwin (more specifically, the bash shell running with cygwin) to
> be able to launch/stop native win32 apps with the same semantics one
> has come to expect when running cmd shell.
> If that's not the goal, then it's a non-issue.
> 
	[Heribert]  [snip]
>  

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

             reply	other threads:[~2001-07-18 13:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-18 13:42 Heribert Dahms [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-07-18 16:48 Karr, David
2001-07-18 14:01 Troy Noble
2001-07-18 12:55 Troy Noble
2001-07-18  9:32 Troy Noble
2001-07-18  9:56 ` Christopher Faylor
2001-07-18 16:36 ` Michael A. Chase
2001-07-17 13:50 Troy Noble
2001-07-17 19:55 ` Christopher Faylor
2001-07-17 13:25 Puttkammer, Roman
2001-07-17 14:10 ` Larry Hall (RFK Partners, Inc)
2001-07-17 15:38   ` Michael Schaap
2001-07-17 13:06 Troy Noble
2001-07-17 13:15 ` Christopher Faylor
2001-07-17 13:28   ` Christopher Faylor
2001-07-17 12:00 Troy Noble
2001-07-17 12:37 ` Christopher Faylor

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=BF35D9C143BCCC4EB63181B67C9320C804DE17@serv-075.icon-germany.local \
    --to=heribert_dahms@icon-scm.com \
    --cc=cygwin@cygwin.com \
    --cc=troy.noble@channelpoint.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).