Re: deadlock with busy waiting on sigfe

2013-03-16 Thread Christopher Faylor
On Sat, Mar 16, 2013 at 11:00:49AM +0900, jojelino wrote: >On 2013-03-16 AM 10:46, jojelino wrote: >> On 2013-03-16 AM 4:41, Christopher Faylor wrote: >>> On Mon, Mar 11, 2013 at 04:45:54PM -0400, Christopher Faylor wrote: >>> Actually, if you are running this on a DOS console, and you hit CTRL-C,

Re: deadlock with busy waiting on sigfe

2013-03-15 Thread jojelino
On 2013-03-16 AM 10:46, jojelino wrote: On 2013-03-16 AM 4:41, Christopher Faylor wrote: On Mon, Mar 11, 2013 at 04:45:54PM -0400, Christopher Faylor wrote: Actually, if you are running this on a DOS console, and you hit CTRL-C, you will have at least one other thread executing. Were you runnin

Re: deadlock with busy waiting on sigfe

2013-03-15 Thread jojelino
On 2013-03-16 AM 4:41, Christopher Faylor wrote: On Mon, Mar 11, 2013 at 04:45:54PM -0400, Christopher Faylor wrote: Actually, if you are running this on a DOS console, and you hit CTRL-C, you will have at least one other thread executing. Were you running this under mintty (aka a pty) or in a W

Re: deadlock with busy waiting on sigfe

2013-03-15 Thread Christopher Faylor
On Mon, Mar 11, 2013 at 04:45:54PM -0400, Christopher Faylor wrote: >On Tue, Mar 12, 2013 at 04:35:41AM +0900, jojelino wrote: >>On 2013-03-11 PM 11:36, Christopher Faylor wrote: >>> A "proper bug report" would at least include what you were actually doing >>> to trigger this problem. >>> >>I was t

Re: deadlock with busy waiting on sigfe

2013-03-11 Thread Christopher Faylor
On Tue, Mar 12, 2013 at 04:35:41AM +0900, jojelino wrote: >On 2013-03-11 PM 11:36, Christopher Faylor wrote: >> A "proper bug report" would at least include what you were actually doing >> to trigger this problem. >> >I was trying to CTRL+C cygwin python process that is executing some >operation a

Re: deadlock with busy waiting on sigfe

2013-03-11 Thread jojelino
On 2013-03-12 AM 4:35, jojelino wrote: I was trying to CTRL+C cygwin python process that is executing some operation and fell asleep for 60 seconds repeatedly. I'm pretty sure that the process was sleeping as i tried interrupt it. And some operation includes making connection to localhost tcp ser

Re: deadlock with busy waiting on sigfe

2013-03-11 Thread jojelino
On 2013-03-11 PM 11:36, Christopher Faylor wrote: A "proper bug report" would at least include what you were actually doing to trigger this problem. I was trying to CTRL+C cygwin python process that is executing some operation and fell asleep for 60 seconds repeatedly. I'm pretty sure that the

Re: deadlock with busy waiting on sigfe

2013-03-11 Thread Christopher Faylor
On Mon, Mar 11, 2013 at 05:53:50PM +0900, jojelino wrote: >On 2013-01-20 PM 3:54, Christopher Faylor wrote: >> On Sun, Jan 20, 2013 at 02:23:23PM +0900, jojelino wrote: >> Once again: don't care about your backtraces. Submit a proper bug report. >> >> cgf >> >And found another livelock with CYGWIN

Re: deadlock with busy waiting on sigfe

2013-03-11 Thread jojelino
On 2013-01-20 PM 3:54, Christopher Faylor wrote: On Sun, Jan 20, 2013 at 02:23:23PM +0900, jojelino wrote: Once again: don't care about your backtraces. Submit a proper bug report. cgf And found another livelock with CYGWIN_NT-5.2 F8G6S6D42HGDY4 1.7.18s(0.263/5/3) 20130309 21:57:01 i686 Cygwi

Re: deadlock with busy waiting on sigfe

2013-01-19 Thread Christopher Faylor
On Sun, Jan 20, 2013 at 02:23:23PM +0900, jojelino wrote: >On 2013-01-16 AM 11:14, Christopher Faylor wrote: >> On Tue, Jan 15, 2013 at 08:46:46PM -0500, Christopher Faylor wrote: >> Sorry, the backtraces were actually useful because they show that you >> are apparently running cygwin-snapshot-2013

Re: deadlock with busy waiting on sigfe

2013-01-19 Thread jojelino
On 2013-01-16 AM 11:14, Christopher Faylor wrote: On Tue, Jan 15, 2013 at 08:46:46PM -0500, Christopher Faylor wrote: Sorry, the backtraces were actually useful because they show that you are apparently running cygwin-snapshot-20130107. Apparently you haven't been watching the discussion about t

Re: deadlock with busy waiting on sigfe

2013-01-15 Thread Christopher Faylor
On Tue, Jan 15, 2013 at 08:46:46PM -0500, Christopher Faylor wrote: >On Tue, Jan 15, 2013 at 11:00:16AM +0900, jojelino wrote: >>Caused by executing following command and ctrl+c to interrupt in bash shell. >>sh -c "cd /tmp/openjpeg/src/bin/jp2 && /usr/bin/i686-pc-mingw32-gcc.exe >> -DOPJ_EXPORTS

Re: deadlock with busy waiting on sigfe

2013-01-15 Thread Christopher Faylor
On Tue, Jan 15, 2013 at 11:00:16AM +0900, jojelino wrote: >Caused by executing following command and ctrl+c to interrupt in bash shell. >sh -c "cd /tmp/openjpeg/src/bin/jp2 && /usr/bin/i686-pc-mingw32-gcc.exe > -DOPJ_EXPORTS -ffast-math -O3 -DNDEBUG >@CMakeFiles/opj_compress.dir/includes_C.rsp

deadlock with busy waiting on sigfe

2013-01-14 Thread jojelino
Caused by executing following command and ctrl+c to interrupt in bash shell. sh -c "cd /tmp/openjpeg/src/bin/jp2 && /usr/bin/i686-pc-mingw32-gcc.exe -DOPJ_EXPORTS -ffast-math -O3 -DNDEBUG @CMakeFiles/opj_compress.dir/includes_C.rsp -o CMakeFiles/opj_compress.dir/convert.c.obj -c /tmp/open