[ANNOUNCEMENT] Updated: {lcms/liblcms1/liblcms-devel/python-lcms}-1.19-5: Little color management engine
Hi New versions of 'lcms/liblcms1/liblcms-devel/python-lcms' have been uploaded to a server near you. o Build for cygwin 1.7.34 with gcc-4.9.2 o Fix for CVE-2013-4276 - see https://cygwin.com/ml/cygwin-apps/2015-02/msg00235.html CYGWIN-ANNOUNCE UNSUBSCRIBE INFO If you want to unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain.com at cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- 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
[ANNOUNCEMENT] Updated: {openldap/openldap-server/libopenldap2_4_2/openldap-devel}-2.4.40-2: Lightweight Directory Access Protocol suite
Hi New versions of 'openldap/openldap-server/libopenldap2_4_2/openldap-devel' have been uploaded to a server near you. o Build for cygwin 1.7.34 with gcc-4.9.2 o Fix for CVE-2015-1545 - https://cygwin.com/ml/cygwin-apps/2015-02/msg00237.html CYGWIN-ANNOUNCE UNSUBSCRIBE INFO If you want to unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain.com at cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- 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
Updated: {lcms/liblcms1/liblcms-devel/python-lcms}-1.19-5: Little color management engine
Hi New versions of 'lcms/liblcms1/liblcms-devel/python-lcms' have been uploaded to a server near you. o Build for cygwin 1.7.34 with gcc-4.9.2 o Fix for CVE-2013-4276 - see https://cygwin.com/ml/cygwin-apps/2015-02/msg00235.html CYGWIN-ANNOUNCE UNSUBSCRIBE INFO If you want to unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain.com at cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL.
Updated: {openldap/openldap-server/libopenldap2_4_2/openldap-devel}-2.4.40-2: Lightweight Directory Access Protocol suite
Hi New versions of 'openldap/openldap-server/libopenldap2_4_2/openldap-devel' have been uploaded to a server near you. o Build for cygwin 1.7.34 with gcc-4.9.2 o Fix for CVE-2015-1545 - https://cygwin.com/ml/cygwin-apps/2015-02/msg00237.html CYGWIN-ANNOUNCE UNSUBSCRIBE INFO If you want to unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain.com at cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL.
Re: [SECURITY] vorbis-tools
On 2/19/2015 10:53 PM, Yaakov Selkowitz wrote: On Tue, 2015-02-17 at 22:42 -0600, Yaakov Selkowitz wrote: David, vorbis-tools requires a patch for CVE-2014-9640: http://pkgs.fedoraproject.org/cgit/vorbis-tools.git/plain/vorbis-tools-1.4.0-bz1185558.patch And now another one for CVE-2014-9638 and CVE-2014-9639: http://pkgs.fedoraproject.org/cgit/vorbis-tools.git/plain/vorbis-tools-1.4.0-CVE-2014-9638-CVE-2014-9639.patch There are other patches in that repo that you may wish to consider adding; at a minimum, I would recommend the patch for vcut: http://pkgs.fedoraproject.org/cgit/vorbis-tools.git/plain/vorbis-tools-1.4.0-bz1003607.patch I've uploaded a new package with these patches. Thanks for the pointers. -- David Rothenberger daver...@acm.org Professional wrestling: ballet for the common man.
[ITP] svm-3.20-1
This is needed for the upcoming clisp-2.49. [*]
D=http://sanibeltranquility.com/cygwin/x86/release/svm
wget -x -nH --cut-dirs=1 \
${D}/svm-3.20-1-src.tar.xz \
${D}/svm-3.20-1.tar.xz \
${D}/setup.hint \
${D}/svm-debuginfo/svm-debuginfo-3.20-1.tar.xz \
${D}/svm-debuginfo/setup.hint \
${D}/libsvm2/libsvm2-3.20-1.tar.xz \
${D}/libsvm2/setup.hint \
${D}/libsvm-devel/libsvm-devel-3.20-1.tar.xz \
${D}/libsvm-devel/setup.hint
D=http://sanibeltranquility.com/cygwin/x86_64/release/svm
wget -x -nH --cut-dirs=1 \
${D}/svm-3.20-1-src.tar.xz \
${D}/svm-3.20-1.tar.xz \
${D}/setup.hint \
${D}/svm-debuginfo/svm-debuginfo-3.20-1.tar.xz \
${D}/svm-debuginfo/setup.hint \
${D}/libsvm2/libsvm2-3.20-1.tar.xz \
${D}/libsvm2/setup.hint \
${D}/libsvm-devel/libsvm-devel-3.20-1.tar.xz \
${D}/libsvm-devel/setup.hint
Ken
[*] clisp has a libsvm module that requires an svm DLL. In
clisp-2.48, the svm sources were included, and the DLL was built in the
course of building clisp. The sources have been removed from
clisp-2.49, and users are expected to install a libsvm package.
[ANNOUNCEMENT] Updated: vorbis-tools-1.4.0-2
CYGWIN NEWS: * Applied patch for off-by-one error in vcut * Applied two security patches, including one for CVE-2014-9639. NEWS: = This is a new upstream release. Please see the Changes attachment below for more details. DESCRIPTION: vorbis-tools contains oggenc (an encoder) and ogg123 (a playback tool). It also has vorbiscomment (to add comments to vorbis files), ogginfo (to give all useful information about an ogg file, including streams in it), oggdec (a simple command line decoder), and vcut (which allows you to cut up vorbis files). QUESTIONS: == If you want to make a point or ask a question the Cygwin mailing list is the appropriate place. -- David Rothenberger daver...@acm.org -- 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
Re: ffcall
On 20/02/2015 9:30 AM, Ken Brown wrote: In that case, I think I'll go ahead and release what I have and see if it's of use to anyone. Ken I have built and tested maxima-5.43.1 with your clisp release on cygwin64. Perfect test results.I find clisp slow for routine work, but it is good to have it available. David
Re: db_prefix=none
Greetings, Fernando César! So I spent part of the afternoon dealing with a problem resulting from incompatible behavior from the last version of CygWin. (I know, I should have read the *CHANGES*). The problem is I manage a lot of PC's by ssh, using cygwin. All machines belong to the same AD, have different names, but the same Administrator user. However, now each ssh connection needs a different user name. Wait, what? Please clarify this part. I don't get it. So, I manage a lot of PC's (associated with an Active Directory) using cygwin and ssh PC1, PC2, PC3... I used to be able to login to any of them with ssh PC1 ssh PC2 ssh PC3 using the same user: sysadmin. I have my ~/ssh/config file configure like this Host PC* Username sysadmin ... rest of the configurations ... The problem now, is that each PC has a different user. Instead of sysadmin: PC1+sysadmin PC2+sysadmin ... Why not use single domain user instead of creating local user on each machine? So, it's more problematic to ssh to each machine. That's because you are doing it wrong, to begin with. If all systems are in same domain, there's no reason to create local users on them at all. Programs like clussh, that allow to issue a command to run in every machine will be harder to use. Why I don't have any problem with it? I was wondering if there is a possibility of getting the old user names back, without the prefix. See the end of my previous message: you're overcomplicating things that are essentially simple. Use one user to manage one domain, not tens of users. -- WBR, Andrey Repin (anrdae...@yandex.ru) 21.02.2015, 18:41 Sorry for my terrible english...
Re: Cygwin/X XDMCP Issue
On 20-2-2015 19:36, Maarten Hoes wrote: ( I tried to included my XWin.log and a wireshark tracefile to this message, but the mail server keeps bouncing my messages). Perhaps this works: Xwin.log: http://ur1.ca/jrrmb wireshark tracefile (txt): http://ur1.ca/jrrmh - Maarten -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: ffcall
On 2/21/2015 7:59 AM, Reini Urban wrote: On 02/21/2015 04:44 AM, Ken Brown wrote: On 2/19/2015 2:46 PM, Reini Urban wrote: And the deal with the latest clisp 2.49 was that modules can be dynaloaded. If the gnulib steps would work. I never did for me. And I fixed most of the other module compilation problems before. But I just discovered that clisp-2.49 builds fine with the configure option --without-dynamic-modules. Is there any reason not to do that? After all, clisp-2.48 is built without dynamic modules, so what's the harm in doing the same for 2.49? Technically this is the best. But I never published 2.49 with this option, because there were not many other changes. So it's almost the same as 2.48 and my version was not as confusing. OK, that makes sense. On the other hand, I think users are confused by not having the latest release in the distro, so I'll probably update to 2.49. Ken
Re: make android device file system visible as unix path
V.99 v.99 at seznam.cz writes: On 14.2.2015 4:25, andy wrote: It doesn't have a drive letter in Windows Explorer. The name is simply Moto G. When I ls /cygdrive, I see on the c-drive. I think that the handset's visibility to Windows Explorer is based on MTP USB, but that's just something I'm learning about right now. Root of the problem is in the nature of Media Transfer Protocol. This protocol behaves differently than usual filesystem. For this reason there is no drive letter for Your Moto G in Windows, nor in Cygwin. Best solution I found so far: install sshd on Your Moto G and use scp or rsync to backup files from Your android device. I am using SSHelper. I remember ssh from grad school days (Solaris machines at school). It's an encrypted command line session. And scp is like cp. But for syncing a folder of text files between the handset the laptop, it might be easier to simply use Windows Explorer to copy the handset folder to a temp area on the laptop, then use diff or vimdiff to reconciles differences. -- 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
Re: ffcall
On 2/21/2015 5:03 AM, David Billinghurst wrote: On 20/02/2015 9:30 AM, Ken Brown wrote: In that case, I think I'll go ahead and release what I have and see if it's of use to anyone. Ken I have built and tested maxima-5.43.1 with your clisp release on cygwin64. Perfect test results.I find clisp slow for routine work, but it is good to have it available. Thanks for testing. Ken
RE: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.35-0.3
From: Corinna Vinschen Maybe it is actually simpler than that. Invalidating the cache as a whole probably never makes sense. In fact there are two reasons for invalidation: - The pw_name, pw_shell, pw_home, pw_gecos settings for a user changed. How is pw_name going to change without a logoff? - The interface to the DC was broken and there are entries of the type Achim mentioned, DOM+User(RID). The first case can only be fixed by invalidating the cache on a regular basis. If we didn't fetch the info for a user for, say, 5 minutes, drop the entry from the cache and renew the information by asking the DC again. Maybe too many requests to the DC for all users? Couldn't you just reinitialize if the network data changes? There are times when I would be on the DC and times when I am not with the same account. As for the second case, the DOM+User(RID) entries are undesired and wrong anyway. So maybe the caching code could do what you said in the first place. Invalidate the cache on every network change. But then, only invalidate the entries of the aforementioned type. A network change event works fine for me but not a timer event. Care to hack a bit? I'll take to NET plea as well. I'm doing good to read the list mail. -- cyg Simple -- 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
Re: Clearing O_NONBLOCK from a pipe may lose data
Am 20.02.2015 um 11:13 schrieb Corinna Vinschen: On Feb 20 08:56, Thomas Wolff wrote: Am 20.02.2015 um 00:47 schrieb Andrey Repin: Greetings, Thomas Wolff! Am 19.02.2015 um 10:51 schrieb Corinna Vinschen: On Feb 18 22:08, Lasse Collin wrote: (Please Cc me when replying, I'm not subscribed to the list.) Hi! I suspect that there is a bug in Cygwin: 1. Create a pipe with both ends in blocking mode (O_NONBLOCK is not set). 2. The writer sets its end to non-blocking mode. 3. The writer writes to the pipe. 4. The writer restores its end of the pipe to blocking mode before the reader has read anything from the pipe. 5. The writer closes its end of the pipe. 6. The reader reads from the pipe in blocking mode. The last bytes written by the writer never appear at the reader, thus data is silently lost. Omitting the step 4 above makes the problem go away. I can imagine. A few years back, when changing the pipe code to using overlapped IO, we stumbled over a problem in Windows. When closing an overlapped pipe while I/O is still ongoing, Windows simply destroys the pipe buffers without flushing the data to the reader. This is not much of a problem for blocking IO, but it obviously is for non-blocking. The workaround for this behaviour is this: If the pipe is closed, and this is the writing side of a nonblocking pipe, a background thread gets started which keeps the overlapped structure open and continues to wait for IO completion (i.e. the data has been sent to the reader). However, if you switch back to blocking before closing the pipe, the aforementioned mechanism does not kick in. Could not switching back to blocking simply be handled like closing as far as the waiting is concerned, thus effectively flushing the pipe buffer? You can't just flush it, if the receiving end isn't reading from it. By flushing I meant actually waiting until it's been consumed at the other end in this case, if that's technically feasible. You mean the actual act of changing the descriptor from non-blocking to blocking, as in fcntl(fd, F_SETFL), shall perform the same action of waiting as the close call on non-blocking descriptors does? Yes. I see no strict requirement that the fcntl call removing O_NONBLOCK from a file descriptor should itself still be handled as nonblocking (it can well be argued that the flag is changed first and then the call is allowed to block) - and even if this were not proper it is certainly more acceptable than losing data. I'm not sure that works as desired, but it's probably worth a try. An fcntl method for pipes has to be added (there is none yet, it's all done in fhandler_base::fcntl), then the F_SETFL command would have to be augmented to create a thread calling FlushFileBuffers (which is *supposed* to work on pipe handles but I never tried it myself), and the fcntl call would have to wait for thread completion, allowing interruption by signals (calling cygwait, that is). where the actual code (as I understood you) could be copied from close() code. Although I looked into the code and didn't find the place where close would lead to FlushFileBuffers... The question with stuff like this is usually, how long are you willing to wait? Indefinitely... You never know what the reader side of a pipe is doing. It might just be busy and intends to read from the pipe in a second, a minute, or an hour. ... like it is normal when feeding a pipe in blocking mode (which we just switched to). I don't see a problem here. -- Thomas -- 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
RE: Very slow Cygwin startup on Windows 7
Sysinternals ADInsight is a 32bit only tool and, in order to work on
a 64bit Windows you seem to have to manually inject the DLL
ADInsightDll.dll (which is extracted into %TEMP%) into the target
(32-bit!) process.
So, it seems ADInsight seems a non-starter - for my skill level anyway.
In case it helps you, or another reader of the list, here is a simple
program that injects a named dll into a target process.
Example of using it to examine the ldap calls for cygwin's echo.exe:
- Compile as a 32-bit program using *32bit* cygwin (as ADInsight is a 32bit
process): g++ inject.cpp -o inject.exe
- Start ADInsight from SysInternals
- Start Windows command shell
- Invoke: inject.exe %TEMP%\ADInsightDll.dll c:\cygwin\bin\echo.exe hello
Regards,
Roger.
- inject.cpp -
/*
NAME
Inject.cpp
DESCRIPTION
Inject a DLL into another process
COPYRIGHT
Copyright (C) 2002,2015 by Roger Orr rog...@howzatt.demon.co.uk
This software is distributed in the hope that it will be useful, but
without WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Permission is granted to anyone to make or distribute verbatim
copies of this software provided that the copyright notice and
this permission notice are preserved, and that the distributor
grants the recipient permission for further distribution as permitted
by this notice.
Comments and suggestions are always welcome.
Please report bugs to rog...@howzatt.demon.co.uk.
EXAMPLE
Inject MyDll fred.exe
*/
#include windows.h
#include string
#include iostream
//
// Local functions
int CreateProcessHelper(char ** it, char ** end, HANDLE hProcess,
HANDLE hThread);
int InjectDLL(std::string const dllName, HANDLE hProcess);
//
int main(int argc, char **argv)
{
if (argc 3)
{
std::cerr Syntax: inject dllname progname std::endl;
return 1;
}
std::string const dllName = argv[1];
std::string const progName = argv[2];
HANDLE hProcess = 0;
HANDLE hThread = 0;
if (CreateProcessHelper(argv+2, argv+argc, hProcess, hThread) != 0)
{
return 1;
}
if (InjectDLL(dllName, hProcess) != 0)
{
TerminateProcess(hProcess, GetLastError());
return 1;
}
// resume the created process once we've loaded the DLL
if (::ResumeThread(hThread) == (DWORD)-1)
{
std::cout ResumeThread failed with GetLastError()
std::endl;
return 1;
}
DWORD ret = ::WaitForSingleObject(hProcess, INFINITE);
if (ret == WAIT_OBJECT_0)
{
DWORD exitCode;
if (GetExitCodeProcess(hProcess, exitCode))
{
std::cout Process progName terminated:
return code: exitCode std::endl;
ret = exitCode;
}
else
{
ret = GetLastError();
std::cout Process terminated: return code unavailable:
ret std::endl;
}
}
else if (ret == WAIT_FAILED)
{
std::cout Process wait failed: GetLastError() std::endl;
}
else
{
std::cout Process wait failed: ret std::endl;
}
return ret;
}
//
// Inject DLL 'dllName' into process 'hProcess'
int InjectDLL(std::string const dllName, HANDLE hProcess)
{
LPTHREAD_START_ROUTINE lpStartAddress = 0;
// Create memory in target process
LPVOID const chDllName = VirtualAllocEx(hProcess, 0, dllName.size() + 1,
MEM_COMMIT, PAGE_READWRITE);
if (chDllName == 0)
{
std::cerr VirtualAllocEx failed: GetLastError()
std::endl;
return 1;
}
// Map into my process
if (! WriteProcessMemory(hProcess, chDllName,
dllName.c_str(), dllName.size()+1, 0))
{
std::cerr WriteProcessMemory failed: GetLastError()
std::endl;
return 1;
}
lpStartAddress = (LPTHREAD_START_ROUTINE)LoadLibrary;
// Start a remote thread, at LoadLibraryA in the target process
// Note we assume KERNEL32 has a fixed load address
DWORD threadId(0);
HANDLE const hRemoteThread = CreateRemoteThread(hProcess, 0, 0,
lpStartAddress, chDllName, 0, threadId);
if (hRemoteThread == 0)
{
std::cerr CreateRemoteThread failed: GetLastError()
std::endl;
return 1;
}
WaitForSingleObject(hRemoteThread, 1);
DWORD exitCode;
if (! GetExitCodeThread(hRemoteThread, exitCode))
{
std::cerr GetExitCodeThread failed: GetLastError()
std::endl;
return 1;
}
if (exitCode == STILL_ACTIVE)
{
std::cout Remote thread still running... std::endl;
return 1;
Re: ffcall
David Billinghurst writes:
I have built and tested maxima-5.43.1 with your clisp release on
cygwin64. Perfect test results.I find clisp slow for routine
work, but it is good to have it available.
I've built maxima-5.35.1 for both architectures. The makefiles don't
really want to cooperate with cygport, you'll have to link the sourcedir
and then it still looks for some files that configure produces in
sourcedire while testing… but other than that, everything looks OK, all
tests are pass.
--8---cut here---start-8---
NAME=maxima
VERSION=5.35.1
RELEASE=1
HOMEPAGE=http://maxima.sourceforge.net/index.html;
SRC_URI=mirror://sourceforge/${P}.tar.gz
CATEGORY=Science
SUMMARY=Maxima Computer Algebra System
DESCRIPTION=${SUMMARY}
Maxima is a system for the manipulation of symbolic and numerical
expressions, including differentiation, integration, Taylor series,
Laplace transforms, ordinary differential equations, systems of linear
equations, polynomials, sets, lists, vectors, matrices and
tensors. Maxima yields high precision numerical results by using exact
fractions, arbitrary-precision integers and variable-precision
floating-point numbers. Maxima can plot functions and data in two and
three dimensions.
Maxima is written in CommonLisp and based on the DOE Macsyma that was
developed at MIT.
CYGCONF_ARGS=--enable-clisp-exec --enable-gettext
src_compile() {
cd ${S}
cygautoreconf
lndirs
cd ${B}
cygconf
cygmake
}
src_test() {
cd ${B}
# need to patch test/Makefile here or fix configury
cygtest
}
--8---cut here---end---8---
I also tried building gcl (with the intention of running maxima on gcl);
again you'll have to lndirs and the configure script doesn't check how
to include the xdr headers. It also doesn't find the bfd and liberty
libraries that are static only on Cygwin, not sure if it needs them.
The include hiccup out of the way things start to compile, but then
raw_pre_gcl segfaults.
--8---cut here---start-8---
NAME=gcl
VERSION=2.6.12
RELEASE=1
HOMEPAGE=http://www.gnu.org/software/${PN}/;
SRC_URI=mirror://gnu/${PN}/${P}.tar.gz
SRC_DIR=${PN}
CATEGORY=Text
SUMMARY=GNU Common Lisp
DESCRIPTION=${SUMMARY}
GCL is the official Common Lisp for the GNU project. Its design makes
use of the system's C compiler to compile to native object code,
providing for both good performance and facile portability.
CYGCONF_ARGS=--enable-notify=no --enable-readline --enable-ansi
MAKEOPTS+= -j1 -k
CFLAGS+= -I/usr/include/tirpc
src_compile() {
cd ${S}
cygautoreconf
lndirs
cd ${B}
cygconf
cygmake
}
--8---cut here---end---8---
Regards,
Achim.
--
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+
SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada
Re: ffcall
Achim Gratz writes: The include hiccup out of the way things start to compile, but then raw_pre_gcl segfaults. Something for Corinna it seems… :-) --8---cut here---start-8--- ...gcl.x86/build/unixport (1673) strace /mnt/share/maint/gcl.x86/build/unixport/raw_pre_gcl.exe /mnt/share/maint/gcl.x86/build/unixport/ -libdir /mnt/share/maint/gcl.x86/build/ foo 2 2 [main] raw_pre_gcl (2616) ** 112 114 [main] raw_pre_gcl (2616) Program name: D:\Freeware\CygShare\maint\gcl.x86\build\unixport\raw_pre_gcl.exe (windows pid 2616) 56 170 [main] raw_pre_gcl (2616) OS version: Windows NT-6.3 49 219 [main] raw_pre_gcl (2616) ** 123 342 [main] raw_pre_gcl (2616) sigprocmask: 0 = sigprocmask (0, 0x0, 0x61292748) 339 681 [main] raw_pre_gcl 2616 open_shared: name shared.5, n 5, shared 0x60FF (wanted 0x60FF), h 0x78, *m 6 70 751 [main] raw_pre_gcl 2616 user_heap_info::init: heap base 0x8000, heap top 0x8000, heap size 0x1800 (402653184) 72 823 [main] raw_pre_gcl 2616 open_shared: name S-1-5-21-3709744764-2796632336-1210317817-1001.1, n 1, shared 0x60FE (wanted 0x60FE), h 0x74, *m 6 51 874 [main] raw_pre_gcl 2616 user_info::create: opening user shared for 'S-1-5-21-3709744764-2796632336-1210317817-1001' at 0x60FE 59 933 [main] raw_pre_gcl 2616 user_info::create: user shared version AB1FCCE8 811014 [main] raw_pre_gcl 2616 fhandler_pipe::create: name \\.\pipe\cygwin-08dae4ebc0ee1e22-2616-sigwait, size 5412, mode PIPE_TYPE_MESSAGE 1051119 [main] raw_pre_gcl 2616 fhandler_pipe::create: pipe read handle 0x8C 501169 [main] raw_pre_gcl 2616 fhandler_pipe::create: CreateFile: name \\.\pipe\cygwin-08dae4ebc0ee1e22-2616-sigwait 601229 [main] raw_pre_gcl 2616 fhandler_pipe::create: pipe write handle 0x90 411270 [main] raw_pre_gcl 2616 dll_crt0_0: finished dll_crt0_0 initialization 5911861 [sig] raw_pre_gcl 2616 wait_sig: entering ReadFile loop, my_readsig 0x8C, my_sendsig 0x90 661927 [main] raw_pre_gcl 2616 set_signal_mask: setmask 0, newmask 0, mask_bits 0 471974 [main] raw_pre_gcl 2616 sigprocmask: 0 = sigprocmask (2, 0x10ECAA8, 0x10ECAAC) 342008 [main] raw_pre_gcl 2616 set_signal_mask: setmask 0, newmask 0, mask_bits 0 292037 [main] raw_pre_gcl 2616 sigprocmask: 0 = sigprocmask (2, 0x10ECAA8, 0x10ECAAC) 322069 [main] raw_pre_gcl 2616 sigaction_worker: signal 11, newact 0x10ECAB4 (handler 0x409200), oa 0x0 292098 [main] raw_pre_gcl 2616 sigaction: 0 = sigaction(11, 0x10ECAB4, 0x0) 292127 [main] raw_pre_gcl 2616 sigaction_worker: signal 10, newact 0x10ECAB4 (handler 0x409200), oa 0x0 282155 [main] raw_pre_gcl 2616 sigaction: 0 = sigaction(10, 0x10ECAB4, 0x0) 14680 16835 [main] raw_pre_gcl 2616 mount_info::conv_to_posix_path: conv_to_posix_path (D:\Freeware\CygShare\maint\gcl.x86\build\unixport, no-keep-rel, no-add-slash) 134 16969 [main] raw_pre_gcl 2616 normalize_win32_path: D:\Freeware\CygShare\maint\gcl.x86\build\unixport = normalize_win32_path (D:\Freeware\CygShare\maint\gcl.x86\build\unixport) 53 17022 [main] raw_pre_gcl 2616 mount_info::conv_to_posix_path: /mnt/share/maint/gcl.x86/build/unixport = conv_to_posix_path (D:\Freeware\CygShare\maint\gcl.x86\build\unixport) 125 17147 [main] raw_pre_gcl 2616 sigprocmask: 0 = sigprocmask (0, 0x0, 0x980DD510) 205 17352 [main] raw_pre_gcl 2616 _cygwin_istext_for_stdio: fd 0: not open 67 17419 [main] raw_pre_gcl 2616 _cygwin_istext_for_stdio: fd 1: not open 51 17470 [main] raw_pre_gcl 2616 _cygwin_istext_for_stdio: fd 2: not open 226 17696 [main] raw_pre_gcl (2616) open_shared: name cygpid.2616, n 2616, shared 0x60FD (wanted 0x60FD), h 0xBC, *m 2 90 17786 [main] ? (2616) time: 1424552435 = time(0x0) 48 17834 [main] raw_pre_gcl 2616 pinfo::thisproc: myself dwProcessId 2616 188 18022 [main] raw_pre_gcl 2616 environ_init: GetEnvironmentStrings returned 0x2056D8 120 18142 [main] raw_pre_gcl 2616 environ_init: 0x980EEA28: ALLUSERSPROFILE=C:\ProgramData 77 18219 [main] raw_pre_gcl 2616 environ_init: 0x980EEA48: APPDATA=C:\Users\ASSI\AppData\Roaming 121 18340 [main] raw_pre_gcl 2616 environ_init: 0x980EEA70: COMPUTERNAME=CYGWIN 103 18443 [main] raw_pre_gcl 2616 environ_init: 0x980EEA88: COMSPEC=C:\Windows\system32\cmd.exe 102 18545 [main] raw_pre_gcl 2616 parse_options: glob (called func) 96 18641 [main] raw_pre_gcl 2616 parse_options: returning 47 18688 [main] raw_pre_gcl 2616 environ_init: 0x980EEAB0: CYGWIN=noglob 81 18769 [main] raw_pre_gcl 2616 environ_init: 0x980EEAC8: CYGWIN32_ROOT=D:\Freeware\Cygwin32\ 62 18831 [main] raw_pre_gcl 2616 environ_init: 0x980EEAF0: CYGWIN64_ROOT=D:\Freeware\Cygwin64\ 54 18885 [main] raw_pre_gcl 2616
