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
which would activate the
setting?
Regards,
Kiyo
Christopher Faylor wrote:
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
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
ode.
And that problem has been gone with 1.5.20-1.
Now, the infinite loop problem happens more unpredictably and just
occasionally.
--
Christopher Faylor wrote:
On Wed, Jul 19, 2006 at 05:30:05PM +1000, Kiyo Kelvin Lee wrote:
Actua
Using 1.5.20, occasionally sh.exe would crash with the standard Windows
crash dialog with these information:
[sh.exe - Application Error]
The instruction at "0x6100365f" referenced memory at "0x006cda90". The
memory could not be "written".
Click on OK to terminate the program.
Click on CANCEL
Have you tried something like (with explicit .exe extension):
/bin/rsync -Cavz -e "/usr/bin/ssh.exe" /cygdrive/d/ server:/home/ml/backups/
Probably won't help.
As both with or without extension work for me.
Regards,
Kiyo
ml wrote:
Hi!
[...]
If you call sh like this, sh will try to run the f
ml wrote:
Hi Kiyo,
> caption[sh.exe - Application Error]
> The instruction at "0x6100365f" referenced memory at "0x006cda90".
The memory could not be "written".
> Click on OK to terminate the program.
> Click on CANCEL to debug the program.
Any other (old) cygwin*.dll in Your path or reac
If you call sh like this, sh will try to run the file as shell script.
And of course ls is not a shell script.
To run a binary command (or any command actually) with sh, the command
should be:
sh -c ls
Regards,
Kiyo
ml wrote:
Hi,
i need some help with this:
My plan was to use rsync
If you call sh like this, sh will try to run the file as shell script.
And of course ls is not a shell script.
To run a binary command (or any command actually) with sh, the command
should be:
sh -c ls
Regards,
Kiyo
ml wrote:
Hi,
i need some help with this:
My plan was to use rsync
After upgraded to cygwin-1.5.20, sh.exe (bash) crashed occasionally upon
termination.
The standard Windows crash dialog is shown with this information:
caption[sh.exe - Application Error]
The instruction at "0x6100365f" referenced memory at "0x006cda90". The
memory could not be "written".
Cli
Eric Blake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Kiyo Kelvin Lee on 6/29/2006 10:15 PM:
I took some time to debug into the gvim process and found that actually
a crash (SIGSEGV as reported by gdb) would happen inside the function
tty_list::terminate() (in tty.cc
I am using cygwin-1.5.19-4 (with all related packages being latest) on
Windows XP SP2 and have built gvim 7.0 myself (official vim-6.4 from
cygwin has the same problem though).
After I run gvim in diff mode like:
gvim -d /tmp/a /tmp/b
When I quit gvim, the gvim process never terminates
12 matches
Mail list logo
