On 10/18/2016 2:03 PM, Wilfried wrote:
> Bill Smith wrote:
>> Thanks for all of the responses from everyone. 
>>> If you need to do interactive debugging, run it under cmd or with cygstart.
>> [Bill Smith] it seems that an ok workaround is for me to use cygstart to 
>> start a command prompt within a Cygwin shell and then in the command prompt, 
>> run the program which calls DebugBreak and cause the popup to appear.  The 
>> reason for needing to run within Cygwin is because we have a complex shell 
>> script that sets the user environment to run the application.
> OK, if that is the only reason for using cygwin, I can recommend another
> way to run a complex shell script in windows.
> There is a native windows port of the bash shell in
> http://win-bash.sourceforge.net/
> If you need more unix command line utilities, look in
> https://sourceforge.net/projects/gnuwin32/

Wilfried I think you miss the point of Bill's need and these items you
point to are a bit old as in maintenance appears lacking.  Last file
date for win-bash was 2011 and for gnuwin32 was 2010.

Bill needed to instruct others using Cygwin how to operate with a native
application.  There is no dependence on bash or other scripting language
on Bill's behalf.

cyg Simple

Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Reply via email to