Is your keyboard symbol correctly set at the
startxwin.sh
log?
--
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/
Oh, well, I thought that needed to be a 1 lines program. :-)
Anyway, indeed gdb does pop up for the sample program but doesn't so for
the "real" crashes. Bad luck.
Regards,
Kiyo
Christopher Faylor wrote:
On Fri, Jul 28, 2006 at 08:35:15PM +1000, Kiyo Kelvin Lee wrote:
I am quite sure I am
On Fri, Jul 28, 2006 at 08:35:15PM +1000, Kiyo Kelvin Lee wrote:
>I am quite sure I am doing that correctly.
>I have checked all cygwin processes using System Explorer (from System
>Internals) and they all are having the suggested CYGWIN setting.
>BTW, is there any way to test if the setting is re
> Jon Harrison selex-sas.com> writes:
> >
> > Updating to 1.5.12 doesn't seem to help.
> Sorry, finger trouble: meant 5.1.21
Wow, this thing will take at least another 42 years to fix! ;)
Erik
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cy
Jon Harrison selex-sas.com> writes:
>
> Updating to 1.5.12 doesn't seem to help.
>
>
Sorry, finger trouble: meant 5.1.21
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.h
Larry Hall (Cygwin cygwin.com> writes:
>
> Does 1.5.21 help?
>
Updating to 1.5.12 doesn't seem to help.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:
I am quite sure I am doing that correctly.
I have checked all cygwin processes using System Explorer (from System
Internals) and they all are having the suggested CYGWIN setting.
BTW, is there any way to test if the setting is really effectively?
Say, is there any intentionally broken program wh
On Thu, Jul 27, 2006 at 05:55:55PM +1000, Kiyo Kelvin Lee wrote:
>At least not for me. See my another post in this thread. Both 1.5.21
>and snapshot 20060718 do not help. And I have the feeling that crashes
>happen more often with 1.5.21. Great to hear that I am not alone
>having the problem.
At least not for me.
See my another post in this thread.
Both 1.5.21 and snapshot 20060718 do not help.
And I have the feeling that crashes happen more often with 1.5.21.
Great to hear that I am not alone having the problem.
Regards,
Kiyo
Larry Hall (Cygwin) wrote:
Jon Harrison wrote:
Hi,
I to
Jon Harrison wrote:
Hi,
I too have been experiencing the same sort of psuedo random crash of
sh.exe/bash.exe when running any form of shell script. Again, other than the
irritation of the Windoze Application Error it appears that the scripts have
"worked"
I'd have a hard time putting any kind o
On Sun, Jul 23, 2006 at 03:55:05AM +1000, Kiyo Kelvin Lee wrote:
>Now it seems the crashes are relating to another problem reported
>earlier: 1.5.20: Occasionally infinite loop happens in do_exit()
>(dcrt0.cc) (see attached original text below)
>
>I managed to make sure the infinite loop had not ha
Now it seems the crashes are relating to another problem reported earlier:
1.5.20: Occasionally infinite loop happens in do_exit() (dcrt0.cc) (see
attached original text below)
I managed to make sure the infinite loop had not happened (more about
that later) and then tested to run configure fo
> I'm not sure what this means. If bash kept running
then
> that would indicate that it isn't the bash which is
> crashing. Possibly a forked
>
> cgf
> copy is crashing.
There are copies of cgf that fork?
Actually, that explains an awful lot.
Ant.
__
On Wed, Jul 19, 2006 at 05:30:05PM +1000, Kiyo Kelvin Lee wrote:
>Actually, I have 2 systems (one XP [AMD Athlon 64 3500] and one Win2K
>[Celeron 900]) both have the same problem and attached are the cygcheck
>output.
>
>My sh.exe is bash.exe.
>
>The crashes happen just sparsely and not upon all
14 matches
Mail list logo
