[Bug 34865] New: Can't execute mingw toolchain provided by Rtools

List overview All Threads

newer

older

[Bug 48501] New: U.S. Naval...

[Bug 35344] New: Cygwin's...

wine-bugs＠winehq.org

6 Nov 2013 6 Nov '13

10:23 a.m.

http://bugs.winehq.org/show_bug.cgi?id=34865

Bug #: 34865 Summary: Can't execute mingw toolchain provided by Rtools Product: Wine Version: 1.7.4 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: mail@kirill-mueller.de Classification: Unclassified

I can't execute "R CMD INSTALL" on an installation of R + Rtools in Wine (latest version from PPA "ppa:ubuntu-wine/ppa"). A reproducible script and console output can be found here: https://gist.github.com/krlmlr/7333242 . The script will set and write to $WINEPREFIX and download to $DOWNLOAD_DIR.

Unfortunately, the logs do not show enough detail. After the line `about to run R CMD SHLIB -o kimisc.dll rcpp_hello_world.cpp RcppExports.cpp --debug`, a call to `gcc` is made. (I have added the output of the same call on my Linux system to the Gist.) To me, it seems that the calling process is not notified when the child process has completed, and it stops after a timeout. My hope is that this has been seen before and that there's an easy fix. I'm really new to Wine.

-- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

Show replies by date

wine-bugs＠winehq.org

11 Nov 11 Nov

12:04 a.m.

New subject: [Bug 34865] 64-bit mingw toolchain from Rtools fails to execute (cygwin 1.7.15-1, queued user APC not executed for signal handling)

http://bugs.winehq.org/show_bug.cgi?id=34865

Anastasius Focht focht@gmx.net changed:

--- Comment #1 from Anastasius Focht focht@gmx.net 2013-11-10 18:04:54 CST --- Hello folks,

confirming. Run it with 'wineconsole' to avoid messed up tty and see more diagnostics ...

You initial analysis seems somewhat right, it's about signal delivery between processes through named pipes (this is what cygwin uses).

Actually the real problem seems to be delivery on the _same_ process :-)

Getting trace log:

--- snip --- $ pwd /home/focht/.wine-rtools/drive_c/Program Files/R/R-3.0.2/bin/x64

$ WINEDEBUG=+tid,+seh,+loaddll,+process,+relay wine ./R.exe --verbose --vanilla CMD INSTALL "C:\kimisc-master" --no-multiarch -d

... 002c:Call KERNEL32.CreateProcessW(0062dd30 L"C:\Rtools\bin\make.exe",00220692 L"C:\Rtools\bin\make.exe -f "Makevars.win" -f "C:/PROG~FBU/R/R-3_~NRD.2/etc/x64/Makeconf" -f "C:/PROG~FBU/R/R-3_~NRD.2/share/make/winshlib.mk" SHLIB_LDFLAGS='$(SHLIB_CXXLDFLAGS)' SHLIB_LD='$(SHLIB_CXXLD)' SHLIB="kimisc.dll" DEBUG=T WIN=64 TCLBIN=64 OBJECTS="rcpp_hello_world.o RcppExports.o"",00000000,00000000,00000001,04000020,00000000,00000000,0062fd30,0062fd74) ret=6110d206 ... 002c:trace:process:create_process_impl starting L"C:\Rtools\bin\make.exe" as Win32 binary (0x400000-0x425000) ... 002e:Call KERNEL32.__wine_kernel_init() ret=7bc5968d ... 002c:trace:process:create_process_impl started process pid 002d tid 002e 002c:Ret KERNEL32.CreateProcessW() retval=00000001 ret=6110d206 ... --- snip ---

Child 'make' (pid=0x2e) creates name pipe and event creation for signal communication:

Pipe handle to observe: 0x0000009c

(secondary) signal thread though user APC

--- snip --- 002e:Call KERNEL32.CreateNamedPipeA(0062f78c "\\.\pipe\cygwin-2b6b078c083f2559-45-",00000001,00000004,00000001,000000a4,000000a4,00000000,0062f8d0) ret=610b1b29 002e:Ret KERNEL32.CreateNamedPipeA() retval=00000098 ret=610b1b29 002e:Call KERNEL32.CreateFileA(0062f78c "\\.\pipe\cygwin-2b6b078c083f2559-45-",40000080,00000000,0062f8d0,00000003,00000000,00000000) ret=610b1a11 002e:Ret KERNEL32.CreateFileA() retval=0000009c ret=610b1a11 002e:Call ntdll.NtCreateEvent(0062f62c,001f0003,0062f60c,00000001,00000000) ret=6107f9f4 002e:Ret ntdll.NtCreateEvent() retval=00000000 ret=6107f9f4 002e:Call KERNEL32.QueueUserAPC(61003db0,fffffffe,61188380) ret=610daa42 002e:Ret KERNEL32.QueueUserAPC() retval=00000001 ret=610daa42 002e:Call KERNEL32.TlsAlloc() ret=6107f46c 002e:Ret KERNEL32.TlsAlloc() retval=00000000 ret=6107f46c 002e:Ret PE DLL (proc=0x6107f390,module=0x61000000 L"cygwin1.dll",reason=PROCESS_ATTACH,res=0x1) retval=1 002e:Starting process L"C:\Rtools\bin\make.exe" (entryproc=0x401000) 002e:Call KERNEL32.GetModuleHandleA(00000000) ret=0041edba 002e:Ret KERNEL32.GetModuleHandleA() retval=00400000 ret=0041edba 002e:Call ntdll.NtCreateEvent(0062a864,001f0003,0062a844,00000001,00000000) ret=6107f9f4 002e:Ret ntdll.NtCreateEvent() retval=00000000 ret=6107f9f4 --- snip ---

--- snip --- 002e:Call ntdll.NtWriteFile(000000b8,00000000,00000000,00000000,00629360,20042918,000000f3,611d0210,00000000) ret=6103442c g++ -m64 -I"C:/PROG~FBU/R/R-3_~NRD.2/include" -DNDEBUG -I"C:/Program Files/R/R-3.0.2/library/Rcpp/include" -I"d:/RCompile/CRANpkg/extralibs64/local/include" -O2 -Wall -gdwarf-2 -mtune=core2 -c rcpp_hello_world.cpp -o rcpp_hello_world.o 002e:Ret ntdll.NtWriteFile() retval=00000000 ret=6103442c 002e:Call ntdll.NtCreateEvent(00629494,001f0003,00629474,00000001,00000000) ret=6107f9f4 002e:Ret ntdll.NtCreateEvent() retval=00000000 ret=6107f9f4 ... 002e:Call KERNEL32.CreateNamedPipeA(00629824 "\\.\pipe\cygwin-2b6b078c083f2559-45-pipe-0x1",40000001,00000004,00000001,00010000,00010000,00000000,6119a7e0) ret=610b1b29 002e:Ret KERNEL32.CreateNamedPipeA() retval=000000e0 ret=610b1b29 002e:Call KERNEL32.CreateFileA(00629824 "\\.\pipe\cygwin-2b6b078c083f2559-45-pipe-0x1",40000080,00000000,6119a7e0,00000003,40000000,00000000) ret=610b1a11 002e:Ret KERNEL32.CreateFileA() retval=000000e8 ret=610b1a11 002e:Call KERNEL32.DuplicateHandle(ffffffff,00000000,ffffffff,61279f28,00000000,00000001,00000002) ret=6117c75e 002e:Ret KERNEL32.DuplicateHandle() retval=00000000 ret=6117c75e 002e:Call KERNEL32.DuplicateHandle(ffffffff,00000000,ffffffff,6127a208,00000000,00000001,00000002) ret=6117c75e 002e:Ret KERNEL32.DuplicateHandle() retval=00000000 ret=6117c75e 002e:Call ntdll.NtCreateEvent(00629684,001f0003,00629664,00000000,00000001) ret=6107f9f4 002e:Ret ntdll.NtCreateEvent() retval=00000000 ret=6107f9f4 002e:Call ntdll.NtCreateEvent(00629684,001f0003,00629664,00000000,00000001) ret=6107f9f4 002e:Ret ntdll.NtCreateEvent() retval=00000000 ret=6107f9f4 ... 002e:Call KERNEL32.SetEvent(000000f0) ret=610389b6 002e:Ret KERNEL32.SetEvent() retval=00000001 ret=610389b6 002e:Call KERNEL32.CloseHandle(000000f0) ret=610389c4 002e:Ret KERNEL32.CloseHandle() retval=00000001 ret=610389c4 002e:Call KERNEL32.CloseHandle(000000e8) ret=61033f9a 002e:Ret KERNEL32.CloseHandle() retval=00000001 ret=61033f9a 002e:Call KERNEL32.SetHandleInformation(000000e0,00000001,00000000) ret=61033d58 002e:Ret KERNEL32.SetHandleInformation() retval=00000001 ret=61033d58 002e:Call ntdll.NtCreateEvent(00629664,001f0003,00629644,00000001,00000000) ret=6107f9f4 002e:Ret ntdll.NtCreateEvent() retval=00000000 ret=6107f9f4 002e:Call KERNEL32.DuplicateHandle(ffffffff,ffffffff,ffffffff,00629974,00000000,00000001,00000002) ret=610dc0f8 002e:Ret KERNEL32.DuplicateHandle() retval=00000001 ret=610dc0f8 002e:Call ntdll.NtCreateEvent(006294d4,001f0003,006294b4,00000001,00000000) ret=6107f9f4 002e:Ret ntdll.NtCreateEvent() retval=00000000 ret=6107f9f4 002e:Call KERNEL32.WriteFile(0000009c,00629778,000000a4,0062981c,00000000) ret=610daef0 002e:Ret KERNEL32.WriteFile() retval=00000001 ret=610daef0 002e:Call KERNEL32.WaitForSingleObject(000000f4,0000ea60) ret=610db059 002a:Ret KERNEL32.WaitForSingleObject() retval=00000102 ret=6c71a3b1 ... 002e:Call KERNEL32.CloseHandle(000000f4) ret=610db06b 002e:Ret KERNEL32.CloseHandle() retval=00000001 ret=610db06b ... 002e:Call KERNEL32.GetStdHandle(fffffff4) ret=610e221d 002e:Ret KERNEL32.GetStdHandle() retval=000000bc ret=610e221d 002e:Call KERNEL32.WriteFile(000000bc,00621794,00000068,00629794,00000000) ret=610e2245 60014615 [main] make 45 sig_send: wait for sig_complete event failed, signal -40, rc 258, Win32 error 0 002e:Ret KERNEL32.WriteFile() retval=00000001 ret=610e2245 ... --- snip ---

Write a "signal" packet to pipe 0x0000009c and wait for event 0x000000f4 to be signaled. The event 0x000000f4 ought to be signaled from the other end of pipe - either by another process or from same process using a signal handling thread. Well, guess ... cygwin queues a user APC for that.

Main thread waits 60 sec for 0x000000f4 to become signaled and runs into WAIT_TIMEOUT (0x102 -> 258).

Using Winedbg we can figure out who calls this (NOTE: pids don't match, another run just to illustrate):

--- snip --- Wine-dbg>info process pid threads executable (all id:s are in hex) 00000033 1 'wineconsole.exe' 00000035 1 _ 'R.exe' 00000037 1 _ 'cmd.exe' 00000039 2 _ 'Rterm.exe' 0000003c 1 _ 'make.exe' 0000003e 1 _ 'make.exe' 0000002c 1 'make.exe' 00000021 1 'explorer.exe' 0000000e 5 'services.exe' 0000001b 3 _ 'plugplay.exe' 00000012 4 _ 'winedevice.exe' ... <attach to highest child pid> ... Backtrace: =>0 0xf777742e __kernel_vsyscall+0xe() in [vdso].so (0x00629328) 1 0xf756c233 __libc_read+0x22() in libpthread.so.0 (0x00629328) 2 0x7bc7e876 wait_select_reply+0x30(cookie=0x62940c) [/home/focht/projects/wine/wine-git/dlls/ntdll/server.c:333] in ntdll (0x00629328) 3 0x7bc7f65d server_select+0x182(select_op=0x629464, size=0x8, flags=0x2, timeout=0x6295a8) [/home/focht/projects/wine/wine-git/dlls/ntdll/server.c:597] in ntdll (0x00629438) 4 0x7bc88bdb NtWaitForMultipleObjects+0xd4(count=0x1, handles=0x6295b0, wait_all=0, alertable=0, timeout=0x6295a8) [/home/focht/projects/wine/wine-git/dlls/ntdll/sync.c:835] in ntdll (0x00629578) 5 0x7b875dc0 WaitForMultipleObjectsEx+0x160(count=<couldn't compute location>, handles=<couldn't compute location>, wait_all=<couldn't compute location>, timeout=<couldn't compute location>, alertable=<couldn't compute location>) [/home/focht/projects/wine/wine-git/dlls/kernel32/sync.c:188] in kernel32 (0x006296d8) 6 0x7b875ba7 WaitForSingleObject+0x45(handle=<couldn't compute location>, timeout=<couldn't compute location>) [/home/focht/projects/wine/wine-git/dlls/kernel32/sync.c:128] in kernel32 (0x00629718) 7 0x610db059 in cygwin1 (+0xdb058) (0x00629840) 8 0x610db897 in cygwin1 (+0xdb896) (0x00629910) 9 0x6107835e in cygwin1 (+0x7835d) (0x00629aa0) 10 0x610d50f5 in cygwin1 (+0xd50f4) (0x00629af0) 11 0x0040b0f5 in make (+0xb0f4) (0x00629b20) 12 0x0040b51c in make (+0xb51b) (0x00629b70) ... 24 0x0040efb8 in make (+0xefb7) (0x0062a970) 25 0x61007128 in cygwin1 (+0x7127) (0x0062ab70) --- snip ---

The child 'make' process has only one main thread.

Using the info from callstack and a disassembler on "cygwin1.dll" we can deduce where this binary comes from:

--- snip --- /home/corinna/src/cygwin/cygwin-1.7.15/cygwin-1.7.15-1/src/cygwin-1.7.15/winsup/cygwin/sigproc.cc --- snip ---

Source to CVS HEAD: http://cygwin.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/sigproc.cc?cvsroot=sr...

Checking if a tag exists for "cygwin-1.7.15-x":

--- snip --- Revision 1.384 / (download) - annotate - [select for diffs] , Wed May 2 16:39:39 2012 UTC (18 months, 1 week ago) by cgf Branch: MAIN CVS Tags: cygwin-1_7_15-release --- snip ---

Looking at the CVS commit history there seem to be lots of bugfixes and partial rewrite (merge) _after_ that tag (18 months old).

Source to CVS tag: http://cygwin.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/sigproc.cc?rev=1.384&...

You can cross-check between source code of "sig_send" function and looking at Wine trace log API calls.

For me it looks like the user APC which ought to handle the other pipe end/signalling is not called in between WriteFile() and WaitForSingleObject() because the main thread didn't enter an alertable state.

The be in alertable state, the (main) thread has to call SleepEx, SignalObjectAndWait, WaitForSingleObjectEx, WaitForMultipleObjectsEx, or MsgWaitForMultipleObjectsEx.

WaitForSingleObject() -> WaitForMultipleObjectsEx( ... bAlertable = FALSE)

Can standard WriteFile() cause queued APC to be executed? I don't know.

Regards

wine-bugs＠winehq.org

9:18 p.m.

New subject: [Bug 34865] 64-bit mingw toolchain from Rtools fails to execute (cygwin 1.7.15-1, queued user APC not executed for signal handling)

http://bugs.winehq.org/show_bug.cgi?id=34865

--- Comment #2 from Anastasius Focht focht@gmx.net 2013-11-11 15:18:01 CST --- Hello again,

it seems the Cygwin dll distributed with R-studio is a custom build (snapshot) that has a very short-lived patch applied which introduces the use of APC to create the signal receiver thread.

Again: that patch never made it into official source tree!

After unsuccessfully digging the CVS history and I found a discussion related to user APC on the Cygwin mailing list:

http://marc.info/?t=131176630600003

Patch: http://www.mail-archive.com/cygwin-patches@cygwin.com/msg05242.html

--- quote --- As sigproc_init is called during dll initialization, wait_sig thread is not created as soon as possible.(this is known in msdn createthread reference. http://msdn.microsoft.com/en-us/library/ms682453(v=vs.85).aspx) And then wait_sig starts to wake up as sig_dispatch_pending enters waitforsingleobject. then main thread stops for few ms. and it shows poor performance.

as a workaround, issue user apc call, let the os decide when to call them. And the result was quite good. patch,changelog modified are attached. Please review it. --- quote ---

Corinna's answer:

--- quote --- The slowdown of the code was the result of a patch which was supposed to fix a potential race condition. Jojelino's patch looks nice, but it might reintroduce a new race. Handle with care. --- quote ---

Compare Cygwin1.dll disassembly (see patch source):

--- snip --- 610DA9E9 mov edx, 611EA590h ; "sync_proc_subproc" ... 610DAA04 mov dword ptr [eax+18h], 611EA5A2h ; "sig" ... 610DAA29 call GetCurrentThread 610DAA2E mov [esp+8], ebx 610DAA32 mov dword ptr [esp], 61003DB0h ; address of user APC 610DAA39 mov [esp+4], eax 610DAA3D call QueueUserAPC ... --- snip ---

Date/size of cygwin dll:

--- snip --- -rw-rw-r--. 1 focht focht 2288181 Jul 16 2012 cygwin1.dll --- snip ---

--- quote --- On Sat, Jul 30, 2011 at 05:09:08PM -0400, Christopher Faylor wrote:

Oops. Forgot to mention that these changes are available in the most recent snapshot at: http://cygwin.com/snapshots/ . --- quote ---

Unfortunately this snapshot is too far away and not available anymore.

The queued APC needs to be executed only once to create the real signal receiver thread which handles the other end of the pipe. My guess would be that this APC is implicitly triggered by some win API calls that have alertable wait under the hood.

I manually triggered the APC and it indeed created the signal thread.

The APC entry point address 0x61003db0. Direct win64 API calls from within the APC can be easily found at that range 0x61003xxx:

--- snip --- ... 002f:Call KERNEL32.QueueUserAPC(61003db0,fffffffe,61188380) ret=610daa42 002f:Ret KERNEL32.QueueUserAPC() retval=00000001 ret=610daa42 ... 002f:Call KERNEL32.CreateThread(6119a7ec,00000000,61003f30,61188380,00000000,61188384) ret=61003d33 ... 002f:Ret KERNEL32.CreateThread() retval=00000138 ret=61003d33 002f:Call KERNEL32.SetThreadPriority(00000138,00000002) ret=61003dd2 0030:Call PE DLL (proc=0x6107f390,module=0x61000000 L"cygwin1.dll",reason=THREAD_ATTACH,res=(nil)) 002f:Ret KERNEL32.SetThreadPriority() retval=00000001 ret=61003dd2 0030:Ret PE DLL (proc=0x6107f390,module=0x61000000 L"cygwin1.dll",reason=THREAD_ATTACH,res=(nil)) retval=1 002f:Call KERNEL32.CloseHandle(00000138) ret=61003de0 0030:Call PE DLL (proc=0x7ecf6e94,module=0x7ec40000 L"user32.dll",reason=THREAD_ATTACH,res=(nil)) 0030:Ret PE DLL (proc=0x7ecf6e94,module=0x7ec40000 L"user32.dll",reason=THREAD_ATTACH,res=(nil)) retval=1 ... 0030:Starting thread proc 0x6107f360 (arg=0x61188380) --- snip ---

I'm not sure why RStudio chose a Cygwin snapshot with custom patches applied for their official 3.0.2 release for Windows.

Regards

wine-bugs＠winehq.org

13 Nov 13 Nov

10:31 a.m.

New subject: [Bug 34865] 64-bit mingw toolchain from Rtools fails to execute (cygwin 1.7.15-1, queued user APC not executed for signal handling)

http://bugs.winehq.org/show_bug.cgi?id=34865

--- Comment #3 from mail@kirill-mueller.de 2013-11-13 04:31:53 CST --- Thanks for your extensive analysis, the messages from this list got lost in my spam folder :-(

Just to clarify, it's "Rtools", not "Rstudio". I've got to ask the people over there if they might consider upgrading to a more recent cygwin.

Can anything be done on the Wine end to work around this?

wine-bugs＠winehq.org

8 Jan 8 Jan

10:13 p.m.

New subject: [Bug 34865] 64-bit mingw toolchain from Rtools fails to execute (cygwin 1.7.15-1, queued user APC not executed for signal handling)

http://bugs.winehq.org/show_bug.cgi?id=34865

--- Comment #4 from Anastasius Focht focht@gmx.net --- Hello folks,

it seems the Rtools release 3.0.2 download location was silently updated with a cygwin dll (1.7.25) that doesn't have that short-lived APC patch applied .

Unfortunately I didn't sha1sum when I wrote the analysis (I usually do) so I verified the installed 'cygwin1.dll' in question:

--- snip --- $ ll cygwin1.dll -rw-rw-r--. 1 focht focht 3115385 Aug 31 14:40 cygwin1.dll

$ strings cygwin1.dll | grep cygwin-1.7

/home/corinna/src/cygwin/cygwin-1.7.25/32/cygwin-1.7.25-1/src/src/winsup/cygwin/cygheap.cc ... --- snip ---

OP: I can't reproduce the bug anymore with your script, can you confirm?

FYI I had to install an additional package, named 'plyr' your 'kimisc' package depends on.

Interesting tidbit from http://bugs.winehq.org/show_bug.cgi?id=24018#c13 ( Andrey Turkin):

--- quote --- ... unfortunately the latest cygwin build still doesn't work as it should due to another regression. This one is a Wine bug.

Basically it boils down to the fact that user APCs queued before starting process' WinMain (that is, queued in DllMain handlers and in TLS callbacks) should be executed after dlls are loaded, tls callbacks are executed, loader lock is released but before starting WinMain. Wine doesn't do that (which is not surprising given how Wine process startup differs from Windows') To properly fix this bug one would need to implement NtTestAlert (to make sure APC queue is empty).

In meantime I attached a small hack which is enough to make Cygwin happy (with regard to this bug). With this hack and latest Cygwin snapshot cygwin's setup completes, though not entirely successfully - some of postinstall steps are failing. --- quote ---

That's definitely the same issue I analyzed here because Andrey's comment is dated 2013-06-30 which matches the date where this short-lived APC sneaked into snapshot.

--- quote --- On Sat, Jul 30, 2011 at 05:09:08PM -0400, Christopher Faylor wrote:

Oops. Forgot to mention that these changes are available in the most recent snapshot at: http://cygwin.com/snapshots/ . --- quote ---

With the original Rtools release 3.0.2 and this short lived cygwin dll snapshot version no longer available there is no app to reproduce this anymore.

So the issue is more of theoretical nature.

Regards

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

10:30 p.m.

New subject: [Bug 34865] 64-bit mingw toolchain from Rtools fails to execute (cygwin 1.7.15-1, queued user APC not executed for signal handling)

http://bugs.winehq.org/show_bug.cgi?id=34865

--- Comment #5 from Anastasius Focht focht@gmx.net --- Hello folks,

I should really re-read before hitting submit :| It's two years between mailing list post and Andrey's comment.

The code underwent several changes/refactorings though there is still a usage of QueueUserAPC() API in current cygwin CVS source:

--- snip --- class cygthread { ...

cygthread (LPVOID_THREAD_START_ROUTINE start, LPVOID param, const char *name) : __name (name), func ((LPTHREAD_START_ROUTINE) start), arglen (0), arg (param), notify_detached (NULL) { QueueUserAPC (async_create, GetCurrentThread (), (ULONG_PTR) this); }

... /* This function is called via QueueUserAPC. Apparently creating threads asynchronously is a huge performance win on Win64. */ void CALLBACK cygthread::async_create (ULONG_PTR arg) { cygthread *that = (cygthread *) arg; that->create (); ::SetThreadPriority (that->h, THREAD_PRIORITY_HIGHEST); that->zap_h (); } --- snip ---

Regards

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

10:49 p.m.

New subject: [Bug 34865] 64-bit mingw toolchain from Rtools fails to execute (cygwin 1.7.15-1, queued user APC not executed for signal handling)

http://bugs.winehq.org/show_bug.cgi?id=34865

mail@kirill-mueller.de changed:

--- Comment #6 from mail@kirill-mueller.de --- Works as if this bug never existed. Thanks for checking again, I wouldn't have.

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

4 Nov 4 Nov

10:21 a.m.

New subject: [Bug 34865] 64-bit mingw toolchain from Rtools fails to execute ( cygwin 1.7.15-1, queued user APC not executed for signal handling)

https://bugs.winehq.org/show_bug.cgi?id=34865

Austin English austinenglish@gmail.com changed:

What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED

--- Comment #7 from Austin English austinenglish@gmail.com --- Closing.

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

5 Nov 5 Nov

10:19 p.m.

New subject: [Bug 34865] 64-bit mingw toolchain from Rtools fails to execute ( cygwin 1.7.15-1, queued user APC not executed for signal handling)

https://bugs.winehq.org/show_bug.cgi?id=34865

Austin English austinenglish@gmail.com changed:

What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |RESOLVED

--- Comment #8 from Austin English austinenglish@gmail.com --- This was inadvertently caught up in my unclosed bugs filter. NOTOURBUG should only be closed when fixed upstream.

Setting back to RESOLVED NOTOURBUG.

Sorry for the spam.

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

20 Nov 20 Nov

8:32 p.m.

New subject: [Bug 34865] 64-bit mingw toolchain from Rtools fails to execute ( cygwin 1.7.15-1, queued user APC not executed for signal handling)

https://bugs.winehq.org/show_bug.cgi?id=34865

Matteo Bruni matteo.mystral@gmail.com changed:

What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED

--- Comment #9 from Matteo Bruni matteo.mystral@gmail.com --- (In reply to mail from comment #6)

...

Works as if this bug never existed. Thanks for checking again, I wouldn't have.

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

WineHQ Bugzilla

21 Jan 21 Jan

3:19 p.m.

New subject: [Bug 34865] 64-bit mingw toolchain from Rtools fails to execute (cygwin 1.7.15-1, queued user APC not executed for signal handling)

https://bugs.winehq.org/show_bug.cgi?id=34865

Zebediah Figura z.figura12@gmail.com changed:

--- Comment #10 from Zebediah Figura z.figura12@gmail.com --- Resolving duplicate.

*** This bug has been marked as a duplicate of bug 35561 ***

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

WineHQ Bugzilla

23 Jan 23 Jan

2:32 a.m.

New subject: [Bug 34865] 64-bit mingw toolchain from Rtools fails to execute (cygwin 1.7.15-1, queued user APC not executed for signal handling)

https://bugs.winehq.org/show_bug.cgi?id=34865

Alistair Leslie-Hughes leslie_alistair@hotmail.com changed:

What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED

--- Comment #11 from Alistair Leslie-Hughes leslie_alistair@hotmail.com --- Closing Duplicate.

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1795

Age (days ago)

4064

Last active (days ago)

wine-bugs@winehq.org

11 comments

2 participants

tags (0)

participants (2)

wine-bugs＠winehq.org
WineHQ Bugzilla