This is the mail archive of the
cygwin
mailing list for the Cygwin project.
More on that stackdump issue
- From: SJ Wright <sjwright68 at charter dot net>
- To: cygwin at cygwin dot com
- Date: Thu, 16 Sep 2010 19:15:50 -0400
- Subject: More on that stackdump issue
1. Lost red bold text - the escape code for red bold returns white bold;
curiously, the code for yellow plain and yellow underline or any yellow
against a background other than black, return as red.
2. Any "missed" command or command or script not found throws a line
"Aborted" and then a standard prompt.
3. If I happen to keep a bash.exe.stackdump or sh.exe.stackdump in a
given folder without deleting it with an rm command or moving it to the
Recycle Bin from Explorer, no matter what the error may be afterward,
new ones are not created. It's as if the initial one/s is/are being used
as placeholder/s for catching future errors. However, they neither
change their timestamp nor is any data added to the content of the file
when new "errors" occur.
I hope this peculiar issue hasn't been forgotten by the experts on the
list. I should apologise for the peculiar tangent of my last post.
Steve Wright
--
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