* Compiled programs fail to run from Cygwin Terminal, but work from windows cmd
@ 2017-06-21 21:10 Wouter van Doorn
2017-06-21 21:49 ` René Berber
` (2 more replies)
0 siblings, 3 replies; 24+ messages in thread
From: Wouter van Doorn @ 2017-06-21 21:10 UTC (permalink / raw)
To: cygwin
[-- Attachment #1: Type: text/plain, Size: 1176 bytes --]
Hi,
Having installed Cygwin with no errors I could see, I went on to
compile and run "hello world" - as you do. I could make it go from a
windows command prompt after modifying the system path to include
cygwin\bin, so - so far so good.
From the cygwin terminal, however, the same executable refuses to play
ball. No text is shown; the command prompt returns instantly.
I have tried looking in the mailing list archive, and the answer may
well be there (in which case I apologise). But the searches I have
tried either returned nothing, or an incredible amount of information
that was not apparently relevant to my problem.
Maybe the attached strace output tells somebody something; to me its
only helpful thing is that it shows that the cygwin1.dll is found and
loaded, which eliminates the most likely potential problem that I
could see. Dependency Walker only mutters about 64-bit and 32-bit
libraries being mixed, but as the program runs under the Windows
command prompt, I am discounting that as a reason for the failure.
All the standard pre-compiled utilities I tried run as expected from
the cygwin terminal.
I'd be very grateful for a pointer!
Wouter van Doorn
[-- Attachment #2: cygcheck.out --]
[-- Type: application/octet-stream, Size: 44469 bytes --]
Cygwin Configuration Diagnostics
Current System Time: Wed Jun 21 15:44:57 2017
Windows 7 Professional Ver 6.1 Build 7601 Service Pack 1
Running under WOW64 on AMD64
Path: C:\cygwin\home\User\exe.CYGWIN
C:\cygwin\home\User\bin
C:\cygwin\usr\local\bin
C:\cygwin\bin
C:\ProgramData\Oracle\Java\javapath
C:\Program Files\Dell\DW WLAN Card
C:\Windows\system32
C:\Windows
C:\Windows\System32\Wbem
C:\Windows\System32\WindowsPowerShell\v1.0
C:\Program Files\WIDCOMM\Bluetooth Software
C:\Program Files\WIDCOMM\Bluetooth Software\syswow64
C:\Program Files\Git\cmd
C:\cygwin\bin
.
C:\cygwin\cygrive\c\cygwin\bin
C:\cygwin\bin
Output from C:\cygwin\bin\id.exe
UID: 197608(User) GID: 197121(None)
197121(None) 545(Users)
4(INTERACTIVE) 66049(CONSOLE LOGON)
11(Authenticated Users) 15(This Organization)
113(Local account) 4095(CurrentSession)
66048(LOCAL) 262154(NTLM Authentication)
401408(Medium Mandatory Level)
SysDir: C:\Windows\system32
WinDir: C:\Windows
LD_LIBRARY_PATH = '/cygdrive/c/cygwin/bin'
PWD = '/home/User/c_dir'
HOME = '/home/User'
TVlines = '50'
USERDOMAIN = 'User-PC'
OS = 'Windows_NT'
COMMONPROGRAMFILES = 'C:\Program Files (x86)\Common Files'
PROCESSOR_LEVEL = '6'
PSModulePath = 'C:\Windows\system32\WindowsPowerShell\v1.0\Modules\;C:\Program Files (x86)\AutoIt3\AutoItX'
PROCESSOR_ARCHITEW6432 = 'AMD64'
CommonProgramW6432 = 'C:\Program Files\Common Files'
BIN = '/home/User/bin'
BUGPLATFORM = 'CYGWIN'
CommonProgramFiles(x86) = 'C:\Program Files (x86)\Common Files'
MTXHOST = 'l4gep04'
FP_NO_HOST_CHECK = 'NO'
LANG = 'en_US.UTF-8'
TZ = 'Europe/London'
HOSTNAME = 'User-PC'
PUBLIC = 'C:\Users\Public'
OLDPWD = '/home/User/c_dir/numgen'
EDITOR = 'gvim'
MTXPORT = '10101'
lock_status = '0'
USERNAME = 'User'
LOGONSERVER = '\\USER-PC'
PROCESSOR_ARCHITECTURE = 'x86'
EXE = '/home/User/exe.CYGWIN'
CYGWIN_NT61WOW = 'GENERIC'
LOCALAPPDATA = 'C:\Users\User\AppData\Local'
COMPUTERNAME = 'USER-PC'
SYSTEMDRIVE = 'C:'
BUGLIB = '/home/User/c_dir/buglib'
USERPROFILE = 'C:\Users\User'
PATHEXT = '.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC'
SYSTEMROOT = 'C:\Windows'
PROCESSOR_IDENTIFIER = 'Intel64 Family 6 Model 78 Stepping 3, GenuineIntel'
TMP = '/tmp'
HOST = 'User-PC'
windows_tracing_logfile = 'C:\BVTBin\Tests\installpackage\csilogfile.log'
PROCESSOR_REVISION = '4e03'
PROFILEREAD = 'true'
NUMBER_OF_PROCESSORS = '4'
ProgramW6432 = 'C:\Program Files'
windows_tracing_flags = '3'
MTXSCRIPTS = '/home/User/c_dir/mutex/scripts'
COMSPEC = 'C:\Windows\system32\cmd.exe'
APPDATA = 'C:\Users\User\AppData\Roaming'
SHELL = '/bin/bash'
TERM = 'cygwin'
MTXADMIN = '/home/User/.mutex'
TVback = '/home/User/.tvback'
WINDIR = 'C:\Windows'
ProgramData = 'C:\ProgramData'
SHLVL = '1'
PRINTER = 'Dell C1760nw (bw)'
PROGRAMFILES = 'C:\Program Files (x86)'
TVexe = '/home/User/.tvexe'
ALLUSERSPROFILE = 'C:\ProgramData'
TEMP = '/tmp'
SESSIONNAME = 'Console'
ProgramFiles(x86) = 'C:\Program Files (x86)'
PS1 = 'User-PC-> '
PS2 = '-> '
HOMEDRIVE = 'C:'
INFOPATH = '/usr/local/info:/usr/share/info:/usr/info'
HOMEPATH = '\Users\User'
TVini = '/home/User/.tvexe/TVini'
ORIGINAL_PATH = '/cygdrive/c/ProgramData/Oracle/Java/javapath:/cygdrive/c/Program Files/Dell/DW WLAN Card:/cygdrive/c/Windows/system32:/cygdrive/c/Windows:/cygdrive/c/Windows/System32/Wbem:/cygdrive/c/Windows/System32/WindowsPowerShell/v1.0:/cygdrive/c/Program Files/WIDCOMM/Bluetooth Software:/cygdrive/c/Program Files/WIDCOMM/Bluetooth Software/syswow64:/cygdrive/c/Program Files/Git/cmd:/usr/bin'
MINES_HOME = '/home/User'
TVcolumns = '132'
EXECIGNORE = '*.dll'
_ = '/usr/bin/cygcheck'
HKEY_CURRENT_USER\Software\Cygwin
HKEY_CURRENT_USER\Software\Cygwin\Installations
(default) = '\??\C:\cygwin'
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\Installations
(default) = '\??\C:\cygwin'
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\setup
(default) = 'C:\cygwin'
HKEY_LOCAL_MACHINE\SYSTEM\VritualRoot\USER\S-1-5-21-3651929431-2828919770-727385248-1000\Software\Cygwin
HKEY_LOCAL_MACHINE\SYSTEM\VritualRoot\USER\S-1-5-21-3651929431-2828919770-727385248-1000\Software\Cygwin\Installations
(default) = '\??\C:\cygwin'
obcaseinsensitive set to 1
Cygwin installations found in the registry:
System: Key: c5e39b7a9d22bafb Path: C:\cygwin
User: Key: c5e39b7a9d22bafb Path: C:\cygwin
c: hd NTFS 1001059Mb 8% CP CS UN PA FC EN
f: cd N/A N/A
C:\cygwin / system binary,auto
C:\cygwin\bin /usr/bin system binary,auto
C:\cygwin\lib /usr/lib system binary,auto
cygdrive prefix /cygdrive user binary,posix=0,auto
Found: C:\cygwin\bin\awk
Found: C:\cygwin\bin\awk
Found: C:\cygwin\bin\awk
-> C:\cygwin\bin\gawk.exe
Found: C:\cygwin\bin\bash.exe
Found: C:\cygwin\bin\bash.exe
Found: C:\cygwin\bin\bash.exe
Found: C:\cygwin\bin\cat.exe
Found: C:\cygwin\bin\cat.exe
Found: C:\cygwin\bin\cat.exe
Found: C:\cygwin\bin\cp.exe
Found: C:\cygwin\bin\cp.exe
Found: C:\cygwin\bin\cp.exe
Found: C:\cygwin\bin\cpp.exe
Found: C:\cygwin\bin\cpp.exe
Found: C:\cygwin\bin\cpp.exe
Not Found: crontab
Found: C:\cygwin\bin\find.exe
Found: C:\Windows\system32\find.exe
Warning: C:\cygwin\bin\find.exe hides C:\Windows\system32\find.exe
Found: C:\cygwin\bin\find.exe
Found: C:\cygwin\bin\find.exe
Found: C:\cygwin\bin\gcc.exe
Found: C:\cygwin\bin\gcc.exe
Found: C:\cygwin\bin\gcc.exe
Found: C:\cygwin\bin\gdb.exe
Found: C:\cygwin\bin\gdb.exe
Found: C:\cygwin\bin\gdb.exe
Found: C:\cygwin\bin\grep.exe
Found: C:\cygwin\bin\grep.exe
Found: C:\cygwin\bin\grep.exe
Found: C:\cygwin\bin\kill.exe
Found: C:\cygwin\bin\kill.exe
Found: C:\cygwin\bin\kill.exe
Found: C:\cygwin\bin\ld.exe
Found: C:\cygwin\bin\ld.exe
Found: C:\cygwin\bin\ld.exe
Found: C:\cygwin\bin\ls.exe
Found: C:\cygwin\bin\ls.exe
Found: C:\cygwin\bin\ls.exe
Found: C:\cygwin\bin\make.exe
Found: C:\cygwin\bin\make.exe
Found: C:\cygwin\bin\make.exe
Found: C:\cygwin\bin\mv.exe
Found: C:\cygwin\bin\mv.exe
Found: C:\cygwin\bin\mv.exe
Found: C:\cygwin\bin\patch.exe
Found: C:\cygwin\bin\patch.exe
Found: C:\cygwin\bin\patch.exe
Found: C:\cygwin\bin\perl.exe
Found: C:\cygwin\bin\perl.exe
Found: C:\cygwin\bin\perl.exe
Found: C:\cygwin\bin\rm.exe
Found: C:\cygwin\bin\rm.exe
Found: C:\cygwin\bin\rm.exe
Found: C:\cygwin\bin\sed.exe
Found: C:\cygwin\bin\sed.exe
Found: C:\cygwin\bin\sed.exe
Not Found: ssh
Found: C:\cygwin\bin\sh.exe
Found: C:\cygwin\bin\sh.exe
Found: C:\cygwin\bin\sh.exe
Found: C:\cygwin\bin\tar.exe
Found: C:\cygwin\bin\tar.exe
Found: C:\cygwin\bin\tar.exe
Found: C:\cygwin\bin\test.exe
Found: C:\cygwin\bin\test.exe
Found: C:\cygwin\bin\test.exe
Found: C:\cygwin\bin\vi.exe
Found: C:\cygwin\bin\vi.exe
Found: C:\cygwin\bin\vi.exe
Not Found: vim
39k 2016/09/19 C:\cygwin\bin\cygargp-0.dll - os=4.0 img=1.0 sys=4.0
"cygargp-0.dll" v0.0 ts=2016-09-19 02:25
87k 2016/06/14 C:\cygwin\bin\cygatomic-1.dll - os=4.0 img=1.0 sys=4.0
"cygatomic-1.dll" v0.0 ts=2016-06-14 06:44
14k 2012/05/04 C:\cygwin\bin\cygattr-1.dll - os=4.0 img=1.0 sys=4.0
"cygattr-1.dll" v0.0 ts=2012-05-04 12:35
203k 2015/03/23 C:\cygwin\bin\cygblkid-1.dll - os=4.0 img=1.0 sys=4.0
"cygblkid-1.dll" v0.0 ts=2015-03-23 09:55
67k 2017/02/22 C:\cygwin\bin\cygbz2-1.dll - os=4.0 img=1.0 sys=4.0
"cygbz2-1.dll" v0.0 ts=2017-02-22 07:22
28k 2017/05/09 C:\cygwin\bin\cygcord-1.dll - os=4.0 img=1.0 sys=4.0
"cygcord-1.dll" v0.0 ts=2017-05-09 14:06
10k 2016/06/09 C:\cygwin\bin\cygcrypt-0.dll - os=4.0 img=1.0 sys=4.0
"cygcrypt-0.dll" v0.0 ts=2016-06-09 16:02
2012k 2017/01/26 C:\cygwin\bin\cygcrypto-1.0.0.dll - os=4.0 img=1.0 sys=4.0
"cygcrypto-1.0.0.dll" v0.0 ts=2017-01-26 20:11
1284k 2011/11/10 C:\cygwin\bin\cygdb-4.8.dll - os=4.0 img=1.0 sys=4.0
"cygdb-4.8.dll" v0.0 ts=2011-11-10 18:45
1650k 2016/08/22 C:\cygwin\bin\cygdb-5.3.dll - os=4.0 img=1.0 sys=4.0
"cygdb-5.3.dll" v0.0 ts=2016-08-22 12:18
105k 2011/11/10 C:\cygwin\bin\cygdb_cxx-4.8.dll - os=4.0 img=1.0 sys=4.0
"cygdb_cxx-4.8.dll" v0.0 ts=2011-11-10 18:46
134k 2016/08/22 C:\cygwin\bin\cygdb_cxx-5.3.dll - os=4.0 img=1.0 sys=4.0
"cygdb_cxx-5.3.dll" v0.0 ts=2016-08-22 12:18
605k 2016/08/22 C:\cygwin\bin\cygdb_sql-5.3.dll - os=4.0 img=1.0 sys=4.0
"cygdb_sql-5.3.dll" v0.0 ts=2016-08-22 12:18
157k 2016/06/21 C:\cygwin\bin\cygexpat-1.dll - os=4.0 img=1.0 sys=4.0
"cygexpat-1.dll" v0.0 ts=2016-06-21 23:22
32k 2014/10/14 C:\cygwin\bin\cygfam-0.dll - os=4.0 img=1.0 sys=4.0
"cygfam-0.dll" v0.0 ts=2014-10-14 21:21
27k 2015/01/02 C:\cygwin\bin\cygffi-6.dll - os=4.0 img=1.0 sys=4.0
"cygffi-6.dll" v0.0 ts=2015-01-02 01:11
60k 2017/06/18 C:\cygwin\bin\cygformw-10.dll - os=4.0 img=1.0 sys=4.0
"cygformw-10.dll" v0.0 ts=2017-06-18 18:49
126k 2017/05/09 C:\cygwin\bin\cyggc-1.dll - os=4.0 img=1.0 sys=4.0
"cyggc-1.dll" v0.0 ts=2017-05-09 14:06
9k 2017/05/09 C:\cygwin\bin\cyggccpp-1.dll - os=4.0 img=1.0 sys=4.0
"cyggccpp-1.dll" v0.0 ts=2017-05-09 14:06
108k 2016/06/14 C:\cygwin\bin\cyggcc_s-1.dll - os=4.0 img=1.0 sys=4.0
"cyggcc_s-1.dll" v0.0 ts=2016-06-14 05:44
18555k 2016/06/14 C:\cygwin\bin\cyggcj-16.dll - os=4.0 img=1.0 sys=4.0
"cyggcj-16.dll" v0.0 ts=2016-06-14 07:43
13043k 2016/06/14 C:\cygwin\bin\cyggcj-noncore-16.dll - os=4.0 img=1.0 sys=4.0
"cyggcj-noncore-16.dll" v0.0 ts=2016-06-14 07:47
3730k 2016/06/14 C:\cygwin\bin\cyggcj-tools-16.dll - os=4.0 img=1.0 sys=4.0
"cyggcj-tools-16.dll" v0.0 ts=2016-06-14 07:48
44k 2016/10/10 C:\cygwin\bin\cyggdbm-4.dll - os=4.0 img=1.0 sys=4.0
"cyggdbm-4.dll" v0.0 ts=2016-10-10 18:13
14k 2016/10/10 C:\cygwin\bin\cyggdbm_compat-4.dll - os=4.0 img=1.0 sys=4.0
"cyggdbm_compat-4.dll" v0.0 ts=2016-10-10 18:13
14k 2016/06/14 C:\cygwin\bin\cyggij-16.dll - os=4.0 img=1.0 sys=4.0
"cyggij-16.dll" v0.0 ts=2016-06-14 07:48
1520k 2017/03/17 C:\cygwin\bin\cyggio-2.0-0.dll - os=4.0 img=1.0 sys=4.0
"cyggio-2.0-0.dll" v0.0 ts=2017-03-15 16:20
1056k 2017/03/17 C:\cygwin\bin\cygglib-2.0-0.dll - os=4.0 img=1.0 sys=4.0
"cygglib-2.0-0.dll" v0.0 ts=2017-03-15 16:17
16k 2017/03/17 C:\cygwin\bin\cyggmodule-2.0-0.dll - os=4.0 img=1.0 sys=4.0
"cyggmodule-2.0-0.dll" v0.0 ts=2017-03-17 20:25
506k 2017/01/21 C:\cygwin\bin\cyggmp-10.dll - os=4.0 img=1.0 sys=4.0
"cyggmp-10.dll" v0.0 ts=2017-01-21 18:25
318k 2017/03/17 C:\cygwin\bin\cyggobject-2.0-0.dll - os=4.0 img=1.0 sys=4.0
"cyggobject-2.0-0.dll" v0.0 ts=2017-03-15 16:18
113k 2016/06/14 C:\cygwin\bin\cyggomp-1.dll - os=4.0 img=1.0 sys=4.0
"cyggomp-1.dll" v0.0 ts=2016-06-14 05:49
11k 2016/06/14 C:\cygwin\bin\cyggomp-plugin-host_nonshm-1.dll - os=4.0 img=1.0 sys=4.0
"cyggomp-plugin-host_nonshm-1.dll" v0.0 ts=2016-06-14 05:50
9k 2017/03/17 C:\cygwin\bin\cyggthread-2.0-0.dll - os=4.0 img=1.0 sys=4.0
"cyggthread-2.0-0.dll" v0.0 ts=2017-03-15 16:17
820k 2017/04/01 C:\cygwin\bin\cygguile-17.dll - os=4.0 img=1.0 sys=4.0
"cygguile-17.dll" v0.0 ts=2017-04-01 13:52
1327k 2017/04/01 C:\cygwin\bin\cygguile-2.0-22.dll - os=4.0 img=1.0 sys=4.0
"cygguile-2.0-22.dll" v0.0 ts=2017-04-01 13:15
34k 2017/02/13 C:\cygwin\bin\cyghistory7.dll - os=4.0 img=1.0 sys=4.0
"cyghistory7.dll" v0.0 ts=2017-02-11 22:26
1010k 2015/02/20 C:\cygwin\bin\cygiconv-2.dll - os=4.0 img=1.0 sys=4.0
"cygiconv-2.dll" v0.0 ts=2015-02-20 16:52
42k 2016/10/23 C:\cygwin\bin\cygintl-8.dll - os=4.0 img=1.0 sys=4.0
"cygintl-8.dll" v0.0 ts=2016-10-23 07:19
1191k 2015/09/20 C:\cygwin\bin\cygisl-13.dll - os=4.0 img=1.0 sys=4.0
"cygisl-13.dll" v0.0 ts=2015-09-20 12:39
9k 2016/06/14 C:\cygwin\bin\cygjvm.dll - os=4.0 img=1.0 sys=4.0
"cygjvm.dll" v0.0 ts=2016-06-14 07:48
5k 2017/04/01 C:\cygwin\bin\cyglsa.dll - os=4.0 img=1.0 sys=4.0
"cyglsa.dll" v0.0 ts=2017-04-01 19:42
6k 2017/04/01 C:\cygwin\bin\cyglsa64.dll (not x86 dll)
36k 2016/06/28 C:\cygwin\bin\cygltdl-7.dll - os=4.0 img=1.0 sys=4.0
"cygltdl-7.dll" v0.0 ts=2016-06-28 18:57
157k 2017/05/10 C:\cygwin\bin\cyglzma-5.dll - os=4.0 img=1.0 sys=4.0
"cyglzma-5.dll" v0.0 ts=2017-05-10 03:19
133k 2017/05/03 C:\cygwin\bin\cygmagic-1.dll - os=4.0 img=1.0 sys=4.0
"cygmagic-1.dll" v0.0 ts=2017-05-03 04:09
173k 2016/10/10 C:\cygwin\bin\cygman-2-7-5.dll - os=4.0 img=1.0 sys=4.0
"cygman-2-7-5.dll" v0.0 ts=2016-10-10 22:07
21k 2016/10/10 C:\cygwin\bin\cygmandb-2-7-5.dll - os=4.0 img=1.0 sys=4.0
"cygmandb-2-7-5.dll" v0.0 ts=2016-10-10 22:08
30k 2017/06/18 C:\cygwin\bin\cygmenuw-10.dll - os=4.0 img=1.0 sys=4.0
"cygmenuw-10.dll" v0.0 ts=2017-06-18 18:48
98k 2015/03/01 C:\cygwin\bin\cygmpc-3.dll - os=4.0 img=1.0 sys=4.0
"cygmpc-3.dll" v0.0 ts=2015-03-01 20:24
374k 2017/04/08 C:\cygwin\bin\cygmpfr-4.dll - os=4.0 img=1.0 sys=4.0
"cygmpfr-4.dll" v0.0 ts=2017-04-08 12:07
56k 2017/06/18 C:\cygwin\bin\cygncurses++w-10.dll - os=4.0 img=1.0 sys=4.0
"cygncurses++w-10.dll" v0.0 ts=2017-06-18 18:53
316k 2017/06/18 C:\cygwin\bin\cygncursesw-10.dll - os=4.0 img=1.0 sys=4.0
"cygncursesw-10.dll" v0.0 ts=2017-06-18 18:47
1074k 2017/04/28 C:\cygwin\bin\cygp11-kit-0.dll - os=4.0 img=1.0 sys=4.0
"cygp11-kit-0.dll" v0.0 ts=2017-04-28 05:28
15k 2017/06/18 C:\cygwin\bin\cygpanelw-10.dll - os=4.0 img=1.0 sys=4.0
"cygpanelw-10.dll" v0.0 ts=2017-06-18 18:48
471k 2017/04/24 C:\cygwin\bin\cygpcre-1.dll - os=4.0 img=1.0 sys=4.0
"cygpcre-1.dll" v0.0 ts=2017-04-24 01:00
2162k 2017/01/15 C:\cygwin\bin\cygperl5_22.dll - os=4.0 img=1.0 sys=4.0
"cygperl5_22.dll" v0.0 ts=2017-01-15 12:24
41k 2015/04/09 C:\cygwin\bin\cygpipeline-1.dll - os=4.0 img=1.0 sys=4.0
"cygpipeline-1.dll" v0.0 ts=2015-04-09 20:58
43k 2016/07/13 C:\cygwin\bin\cygpopt-0.dll - os=4.0 img=1.0 sys=4.0
"cygpopt-0.dll" v0.0 ts=2016-07-13 06:17
500k 2016/06/14 C:\cygwin\bin\cygquadmath-0.dll - os=4.0 img=1.0 sys=4.0
"cygquadmath-0.dll" v0.0 ts=2016-06-14 06:50
223k 2017/02/13 C:\cygwin\bin\cygreadline7.dll - os=4.0 img=1.0 sys=4.0
"cygreadline7.dll" v0.0 ts=2017-02-11 22:26
11k 2015/07/17 C:\cygwin\bin\cygsigsegv-2.dll - os=4.0 img=1.0 sys=4.0
"cygsigsegv-2.dll" v0.0 ts=2015-07-17 22:33
98k 2015/03/23 C:\cygwin\bin\cygsmartcols-1.dll - os=4.0 img=1.0 sys=4.0
"cygsmartcols-1.dll" v0.0 ts=2015-03-23 09:55
1021k 2017/04/20 C:\cygwin\bin\cygsqlite3-0.dll - os=4.0 img=1.0 sys=4.0
"cygsqlite3-0.dll" v0.0 ts=2017-04-19 17:32
424k 2017/01/26 C:\cygwin\bin\cygssl-1.0.0.dll - os=4.0 img=1.0 sys=4.0
"cygssl-1.0.0.dll" v0.0 ts=2017-01-26 20:11
13k 2016/06/14 C:\cygwin\bin\cygssp-0.dll - os=4.0 img=1.0 sys=4.0
"cygssp-0.dll" v0.0 ts=2016-06-14 06:42
1439k 2016/06/14 C:\cygwin\bin\cygstdc++-6.dll - os=4.0 img=1.0 sys=4.0
"cygstdc++-6.dll" v0.0 ts=2016-06-14 06:06
69k 2017/05/29 C:\cygwin\bin\cygtasn1-6.dll - os=4.0 img=1.0 sys=4.0
"cygtasn1-6.dll" v0.0 ts=2017-05-29 23:33
56k 2017/06/18 C:\cygwin\bin\cygticw-10.dll - os=4.0 img=1.0 sys=4.0
"cygticw-10.dll" v0.0 ts=2017-06-18 18:47
1570k 2015/10/16 C:\cygwin\bin\cygunistring-2.dll - os=4.0 img=1.0 sys=4.0
"cygunistring-2.dll" v0.0 ts=2015-10-16 21:39
16k 2015/03/23 C:\cygwin\bin\cyguuid-1.dll - os=4.0 img=1.0 sys=4.0
"cyguuid-1.dll" v0.0 ts=2015-03-23 09:55
8k 2016/06/14 C:\cygwin\bin\cygvtv-0.dll - os=4.0 img=1.0 sys=4.0
"cygvtv-0.dll" v0.0 ts=2016-06-14 06:42
8k 2016/06/14 C:\cygwin\bin\cygvtv_stubs-0.dll - os=4.0 img=1.0 sys=4.0
"cygvtv_stubs-0.dll" v0.0 ts=2016-06-14 06:42
1290k 2017/03/15 C:\cygwin\bin\cygxml2-2.dll - os=4.0 img=1.0 sys=4.0
"cygxml2-2.dll" v0.0 ts=2017-03-15 20:21
87k 2017/03/03 C:\cygwin\bin\cygz.dll - os=4.0 img=1.0 sys=4.0
"cygz.dll" v0.0 ts=2017-03-03 21:51
3370k 2017/04/01 C:\cygwin\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0
"cygwin1.dll" v0.0 ts=2017-04-01 19:42
Cygwin DLL version info:
DLL version: 2.8.0
DLL epoch: 19
DLL old termios: 5
DLL malloc env: 28
Cygwin conv: 181
API major: 0
API minor: 309
Shared data: 5
DLL identifier: cygwin1
Mount registry: 3
Cygwin registry name: Cygwin
Installations name: Installations
Cygdrive default prefix:
Build date:
Shared id: cygwin1S5
39k 2016/09/19 C:\cygwin\bin\cygargp-0.dll - os=4.0 img=1.0 sys=4.0
"cygargp-0.dll" v0.0 ts=2016-09-19 02:25
87k 2016/06/14 C:\cygwin\bin\cygatomic-1.dll - os=4.0 img=1.0 sys=4.0
"cygatomic-1.dll" v0.0 ts=2016-06-14 06:44
14k 2012/05/04 C:\cygwin\bin\cygattr-1.dll - os=4.0 img=1.0 sys=4.0
"cygattr-1.dll" v0.0 ts=2012-05-04 12:35
203k 2015/03/23 C:\cygwin\bin\cygblkid-1.dll - os=4.0 img=1.0 sys=4.0
"cygblkid-1.dll" v0.0 ts=2015-03-23 09:55
67k 2017/02/22 C:\cygwin\bin\cygbz2-1.dll - os=4.0 img=1.0 sys=4.0
"cygbz2-1.dll" v0.0 ts=2017-02-22 07:22
28k 2017/05/09 C:\cygwin\bin\cygcord-1.dll - os=4.0 img=1.0 sys=4.0
"cygcord-1.dll" v0.0 ts=2017-05-09 14:06
10k 2016/06/09 C:\cygwin\bin\cygcrypt-0.dll - os=4.0 img=1.0 sys=4.0
"cygcrypt-0.dll" v0.0 ts=2016-06-09 16:02
2012k 2017/01/26 C:\cygwin\bin\cygcrypto-1.0.0.dll - os=4.0 img=1.0 sys=4.0
"cygcrypto-1.0.0.dll" v0.0 ts=2017-01-26 20:11
1284k 2011/11/10 C:\cygwin\bin\cygdb-4.8.dll - os=4.0 img=1.0 sys=4.0
"cygdb-4.8.dll" v0.0 ts=2011-11-10 18:45
1650k 2016/08/22 C:\cygwin\bin\cygdb-5.3.dll - os=4.0 img=1.0 sys=4.0
"cygdb-5.3.dll" v0.0 ts=2016-08-22 12:18
105k 2011/11/10 C:\cygwin\bin\cygdb_cxx-4.8.dll - os=4.0 img=1.0 sys=4.0
"cygdb_cxx-4.8.dll" v0.0 ts=2011-11-10 18:46
134k 2016/08/22 C:\cygwin\bin\cygdb_cxx-5.3.dll - os=4.0 img=1.0 sys=4.0
"cygdb_cxx-5.3.dll" v0.0 ts=2016-08-22 12:18
605k 2016/08/22 C:\cygwin\bin\cygdb_sql-5.3.dll - os=4.0 img=1.0 sys=4.0
"cygdb_sql-5.3.dll" v0.0 ts=2016-08-22 12:18
157k 2016/06/21 C:\cygwin\bin\cygexpat-1.dll - os=4.0 img=1.0 sys=4.0
"cygexpat-1.dll" v0.0 ts=2016-06-21 23:22
32k 2014/10/14 C:\cygwin\bin\cygfam-0.dll - os=4.0 img=1.0 sys=4.0
"cygfam-0.dll" v0.0 ts=2014-10-14 21:21
27k 2015/01/02 C:\cygwin\bin\cygffi-6.dll - os=4.0 img=1.0 sys=4.0
"cygffi-6.dll" v0.0 ts=2015-01-02 01:11
60k 2017/06/18 C:\cygwin\bin\cygformw-10.dll - os=4.0 img=1.0 sys=4.0
"cygformw-10.dll" v0.0 ts=2017-06-18 18:49
126k 2017/05/09 C:\cygwin\bin\cyggc-1.dll - os=4.0 img=1.0 sys=4.0
"cyggc-1.dll" v0.0 ts=2017-05-09 14:06
9k 2017/05/09 C:\cygwin\bin\cyggccpp-1.dll - os=4.0 img=1.0 sys=4.0
"cyggccpp-1.dll" v0.0 ts=2017-05-09 14:06
108k 2016/06/14 C:\cygwin\bin\cyggcc_s-1.dll - os=4.0 img=1.0 sys=4.0
"cyggcc_s-1.dll" v0.0 ts=2016-06-14 05:44
18555k 2016/06/14 C:\cygwin\bin\cyggcj-16.dll - os=4.0 img=1.0 sys=4.0
"cyggcj-16.dll" v0.0 ts=2016-06-14 07:43
13043k 2016/06/14 C:\cygwin\bin\cyggcj-noncore-16.dll - os=4.0 img=1.0 sys=4.0
"cyggcj-noncore-16.dll" v0.0 ts=2016-06-14 07:47
3730k 2016/06/14 C:\cygwin\bin\cyggcj-tools-16.dll - os=4.0 img=1.0 sys=4.0
"cyggcj-tools-16.dll" v0.0 ts=2016-06-14 07:48
44k 2016/10/10 C:\cygwin\bin\cyggdbm-4.dll - os=4.0 img=1.0 sys=4.0
"cyggdbm-4.dll" v0.0 ts=2016-10-10 18:13
14k 2016/10/10 C:\cygwin\bin\cyggdbm_compat-4.dll - os=4.0 img=1.0 sys=4.0
"cyggdbm_compat-4.dll" v0.0 ts=2016-10-10 18:13
14k 2016/06/14 C:\cygwin\bin\cyggij-16.dll - os=4.0 img=1.0 sys=4.0
"cyggij-16.dll" v0.0 ts=2016-06-14 07:48
1520k 2017/03/17 C:\cygwin\bin\cyggio-2.0-0.dll - os=4.0 img=1.0 sys=4.0
"cyggio-2.0-0.dll" v0.0 ts=2017-03-15 16:20
1056k 2017/03/17 C:\cygwin\bin\cygglib-2.0-0.dll - os=4.0 img=1.0 sys=4.0
"cygglib-2.0-0.dll" v0.0 ts=2017-03-15 16:17
16k 2017/03/17 C:\cygwin\bin\cyggmodule-2.0-0.dll - os=4.0 img=1.0 sys=4.0
"cyggmodule-2.0-0.dll" v0.0 ts=2017-03-17 20:25
506k 2017/01/21 C:\cygwin\bin\cyggmp-10.dll - os=4.0 img=1.0 sys=4.0
"cyggmp-10.dll" v0.0 ts=2017-01-21 18:25
318k 2017/03/17 C:\cygwin\bin\cyggobject-2.0-0.dll - os=4.0 img=1.0 sys=4.0
"cyggobject-2.0-0.dll" v0.0 ts=2017-03-15 16:18
113k 2016/06/14 C:\cygwin\bin\cyggomp-1.dll - os=4.0 img=1.0 sys=4.0
"cyggomp-1.dll" v0.0 ts=2016-06-14 05:49
11k 2016/06/14 C:\cygwin\bin\cyggomp-plugin-host_nonshm-1.dll - os=4.0 img=1.0 sys=4.0
"cyggomp-plugin-host_nonshm-1.dll" v0.0 ts=2016-06-14 05:50
9k 2017/03/17 C:\cygwin\bin\cyggthread-2.0-0.dll - os=4.0 img=1.0 sys=4.0
"cyggthread-2.0-0.dll" v0.0 ts=2017-03-15 16:17
820k 2017/04/01 C:\cygwin\bin\cygguile-17.dll - os=4.0 img=1.0 sys=4.0
"cygguile-17.dll" v0.0 ts=2017-04-01 13:52
1327k 2017/04/01 C:\cygwin\bin\cygguile-2.0-22.dll - os=4.0 img=1.0 sys=4.0
"cygguile-2.0-22.dll" v0.0 ts=2017-04-01 13:15
34k 2017/02/13 C:\cygwin\bin\cyghistory7.dll - os=4.0 img=1.0 sys=4.0
"cyghistory7.dll" v0.0 ts=2017-02-11 22:26
1010k 2015/02/20 C:\cygwin\bin\cygiconv-2.dll - os=4.0 img=1.0 sys=4.0
"cygiconv-2.dll" v0.0 ts=2015-02-20 16:52
42k 2016/10/23 C:\cygwin\bin\cygintl-8.dll - os=4.0 img=1.0 sys=4.0
"cygintl-8.dll" v0.0 ts=2016-10-23 07:19
1191k 2015/09/20 C:\cygwin\bin\cygisl-13.dll - os=4.0 img=1.0 sys=4.0
"cygisl-13.dll" v0.0 ts=2015-09-20 12:39
9k 2016/06/14 C:\cygwin\bin\cygjvm.dll - os=4.0 img=1.0 sys=4.0
"cygjvm.dll" v0.0 ts=2016-06-14 07:48
5k 2017/04/01 C:\cygwin\bin\cyglsa.dll - os=4.0 img=1.0 sys=4.0
"cyglsa.dll" v0.0 ts=2017-04-01 19:42
6k 2017/04/01 C:\cygwin\bin\cyglsa64.dll (not x86 dll)
36k 2016/06/28 C:\cygwin\bin\cygltdl-7.dll - os=4.0 img=1.0 sys=4.0
"cygltdl-7.dll" v0.0 ts=2016-06-28 18:57
157k 2017/05/10 C:\cygwin\bin\cyglzma-5.dll - os=4.0 img=1.0 sys=4.0
"cyglzma-5.dll" v0.0 ts=2017-05-10 03:19
133k 2017/05/03 C:\cygwin\bin\cygmagic-1.dll - os=4.0 img=1.0 sys=4.0
"cygmagic-1.dll" v0.0 ts=2017-05-03 04:09
173k 2016/10/10 C:\cygwin\bin\cygman-2-7-5.dll - os=4.0 img=1.0 sys=4.0
"cygman-2-7-5.dll" v0.0 ts=2016-10-10 22:07
21k 2016/10/10 C:\cygwin\bin\cygmandb-2-7-5.dll - os=4.0 img=1.0 sys=4.0
"cygmandb-2-7-5.dll" v0.0 ts=2016-10-10 22:08
30k 2017/06/18 C:\cygwin\bin\cygmenuw-10.dll - os=4.0 img=1.0 sys=4.0
"cygmenuw-10.dll" v0.0 ts=2017-06-18 18:48
98k 2015/03/01 C:\cygwin\bin\cygmpc-3.dll - os=4.0 img=1.0 sys=4.0
"cygmpc-3.dll" v0.0 ts=2015-03-01 20:24
374k 2017/04/08 C:\cygwin\bin\cygmpfr-4.dll - os=4.0 img=1.0 sys=4.0
"cygmpfr-4.dll" v0.0 ts=2017-04-08 12:07
56k 2017/06/18 C:\cygwin\bin\cygncurses++w-10.dll - os=4.0 img=1.0 sys=4.0
"cygncurses++w-10.dll" v0.0 ts=2017-06-18 18:53
316k 2017/06/18 C:\cygwin\bin\cygncursesw-10.dll - os=4.0 img=1.0 sys=4.0
"cygncursesw-10.dll" v0.0 ts=2017-06-18 18:47
1074k 2017/04/28 C:\cygwin\bin\cygp11-kit-0.dll - os=4.0 img=1.0 sys=4.0
"cygp11-kit-0.dll" v0.0 ts=2017-04-28 05:28
15k 2017/06/18 C:\cygwin\bin\cygpanelw-10.dll - os=4.0 img=1.0 sys=4.0
"cygpanelw-10.dll" v0.0 ts=2017-06-18 18:48
471k 2017/04/24 C:\cygwin\bin\cygpcre-1.dll - os=4.0 img=1.0 sys=4.0
"cygpcre-1.dll" v0.0 ts=2017-04-24 01:00
2162k 2017/01/15 C:\cygwin\bin\cygperl5_22.dll - os=4.0 img=1.0 sys=4.0
"cygperl5_22.dll" v0.0 ts=2017-01-15 12:24
41k 2015/04/09 C:\cygwin\bin\cygpipeline-1.dll - os=4.0 img=1.0 sys=4.0
"cygpipeline-1.dll" v0.0 ts=2015-04-09 20:58
43k 2016/07/13 C:\cygwin\bin\cygpopt-0.dll - os=4.0 img=1.0 sys=4.0
"cygpopt-0.dll" v0.0 ts=2016-07-13 06:17
500k 2016/06/14 C:\cygwin\bin\cygquadmath-0.dll - os=4.0 img=1.0 sys=4.0
"cygquadmath-0.dll" v0.0 ts=2016-06-14 06:50
223k 2017/02/13 C:\cygwin\bin\cygreadline7.dll - os=4.0 img=1.0 sys=4.0
"cygreadline7.dll" v0.0 ts=2017-02-11 22:26
11k 2015/07/17 C:\cygwin\bin\cygsigsegv-2.dll - os=4.0 img=1.0 sys=4.0
"cygsigsegv-2.dll" v0.0 ts=2015-07-17 22:33
98k 2015/03/23 C:\cygwin\bin\cygsmartcols-1.dll - os=4.0 img=1.0 sys=4.0
"cygsmartcols-1.dll" v0.0 ts=2015-03-23 09:55
1021k 2017/04/20 C:\cygwin\bin\cygsqlite3-0.dll - os=4.0 img=1.0 sys=4.0
"cygsqlite3-0.dll" v0.0 ts=2017-04-19 17:32
424k 2017/01/26 C:\cygwin\bin\cygssl-1.0.0.dll - os=4.0 img=1.0 sys=4.0
"cygssl-1.0.0.dll" v0.0 ts=2017-01-26 20:11
13k 2016/06/14 C:\cygwin\bin\cygssp-0.dll - os=4.0 img=1.0 sys=4.0
"cygssp-0.dll" v0.0 ts=2016-06-14 06:42
1439k 2016/06/14 C:\cygwin\bin\cygstdc++-6.dll - os=4.0 img=1.0 sys=4.0
"cygstdc++-6.dll" v0.0 ts=2016-06-14 06:06
69k 2017/05/29 C:\cygwin\bin\cygtasn1-6.dll - os=4.0 img=1.0 sys=4.0
"cygtasn1-6.dll" v0.0 ts=2017-05-29 23:33
56k 2017/06/18 C:\cygwin\bin\cygticw-10.dll - os=4.0 img=1.0 sys=4.0
"cygticw-10.dll" v0.0 ts=2017-06-18 18:47
1570k 2015/10/16 C:\cygwin\bin\cygunistring-2.dll - os=4.0 img=1.0 sys=4.0
"cygunistring-2.dll" v0.0 ts=2015-10-16 21:39
16k 2015/03/23 C:\cygwin\bin\cyguuid-1.dll - os=4.0 img=1.0 sys=4.0
"cyguuid-1.dll" v0.0 ts=2015-03-23 09:55
8k 2016/06/14 C:\cygwin\bin\cygvtv-0.dll - os=4.0 img=1.0 sys=4.0
"cygvtv-0.dll" v0.0 ts=2016-06-14 06:42
8k 2016/06/14 C:\cygwin\bin\cygvtv_stubs-0.dll - os=4.0 img=1.0 sys=4.0
"cygvtv_stubs-0.dll" v0.0 ts=2016-06-14 06:42
1290k 2017/03/15 C:\cygwin\bin\cygxml2-2.dll - os=4.0 img=1.0 sys=4.0
"cygxml2-2.dll" v0.0 ts=2017-03-15 20:21
87k 2017/03/03 C:\cygwin\bin\cygz.dll - os=4.0 img=1.0 sys=4.0
"cygz.dll" v0.0 ts=2017-03-03 21:51
3370k 2017/04/01 C:\cygwin\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0
"cygwin1.dll" v0.0 ts=2017-04-01 19:42
Cygwin DLL version info:
DLL version: 2.8.0
DLL epoch: 19
DLL old termios: 5
DLL malloc env: 28
Cygwin conv: 181
API major: 0
API minor: 309
Shared data: 5
DLL identifier: cygwin1
Mount registry: 3
Cygwin registry name: Cygwin
Installations name: Installations
Cygdrive default prefix:
Build date:
Shared id: cygwin1S5
39k 2016/09/19 C:\cygwin\bin\cygargp-0.dll - os=4.0 img=1.0 sys=4.0
"cygargp-0.dll" v0.0 ts=2016-09-19 02:25
87k 2016/06/14 C:\cygwin\bin\cygatomic-1.dll - os=4.0 img=1.0 sys=4.0
"cygatomic-1.dll" v0.0 ts=2016-06-14 06:44
14k 2012/05/04 C:\cygwin\bin\cygattr-1.dll - os=4.0 img=1.0 sys=4.0
"cygattr-1.dll" v0.0 ts=2012-05-04 12:35
203k 2015/03/23 C:\cygwin\bin\cygblkid-1.dll - os=4.0 img=1.0 sys=4.0
"cygblkid-1.dll" v0.0 ts=2015-03-23 09:55
67k 2017/02/22 C:\cygwin\bin\cygbz2-1.dll - os=4.0 img=1.0 sys=4.0
"cygbz2-1.dll" v0.0 ts=2017-02-22 07:22
28k 2017/05/09 C:\cygwin\bin\cygcord-1.dll - os=4.0 img=1.0 sys=4.0
"cygcord-1.dll" v0.0 ts=2017-05-09 14:06
10k 2016/06/09 C:\cygwin\bin\cygcrypt-0.dll - os=4.0 img=1.0 sys=4.0
"cygcrypt-0.dll" v0.0 ts=2016-06-09 16:02
2012k 2017/01/26 C:\cygwin\bin\cygcrypto-1.0.0.dll - os=4.0 img=1.0 sys=4.0
"cygcrypto-1.0.0.dll" v0.0 ts=2017-01-26 20:11
1284k 2011/11/10 C:\cygwin\bin\cygdb-4.8.dll - os=4.0 img=1.0 sys=4.0
"cygdb-4.8.dll" v0.0 ts=2011-11-10 18:45
1650k 2016/08/22 C:\cygwin\bin\cygdb-5.3.dll - os=4.0 img=1.0 sys=4.0
"cygdb-5.3.dll" v0.0 ts=2016-08-22 12:18
105k 2011/11/10 C:\cygwin\bin\cygdb_cxx-4.8.dll - os=4.0 img=1.0 sys=4.0
"cygdb_cxx-4.8.dll" v0.0 ts=2011-11-10 18:46
134k 2016/08/22 C:\cygwin\bin\cygdb_cxx-5.3.dll - os=4.0 img=1.0 sys=4.0
"cygdb_cxx-5.3.dll" v0.0 ts=2016-08-22 12:18
605k 2016/08/22 C:\cygwin\bin\cygdb_sql-5.3.dll - os=4.0 img=1.0 sys=4.0
"cygdb_sql-5.3.dll" v0.0 ts=2016-08-22 12:18
157k 2016/06/21 C:\cygwin\bin\cygexpat-1.dll - os=4.0 img=1.0 sys=4.0
"cygexpat-1.dll" v0.0 ts=2016-06-21 23:22
32k 2014/10/14 C:\cygwin\bin\cygfam-0.dll - os=4.0 img=1.0 sys=4.0
"cygfam-0.dll" v0.0 ts=2014-10-14 21:21
27k 2015/01/02 C:\cygwin\bin\cygffi-6.dll - os=4.0 img=1.0 sys=4.0
"cygffi-6.dll" v0.0 ts=2015-01-02 01:11
60k 2017/06/18 C:\cygwin\bin\cygformw-10.dll - os=4.0 img=1.0 sys=4.0
"cygformw-10.dll" v0.0 ts=2017-06-18 18:49
126k 2017/05/09 C:\cygwin\bin\cyggc-1.dll - os=4.0 img=1.0 sys=4.0
"cyggc-1.dll" v0.0 ts=2017-05-09 14:06
9k 2017/05/09 C:\cygwin\bin\cyggccpp-1.dll - os=4.0 img=1.0 sys=4.0
"cyggccpp-1.dll" v0.0 ts=2017-05-09 14:06
108k 2016/06/14 C:\cygwin\bin\cyggcc_s-1.dll - os=4.0 img=1.0 sys=4.0
"cyggcc_s-1.dll" v0.0 ts=2016-06-14 05:44
18555k 2016/06/14 C:\cygwin\bin\cyggcj-16.dll - os=4.0 img=1.0 sys=4.0
"cyggcj-16.dll" v0.0 ts=2016-06-14 07:43
13043k 2016/06/14 C:\cygwin\bin\cyggcj-noncore-16.dll - os=4.0 img=1.0 sys=4.0
"cyggcj-noncore-16.dll" v0.0 ts=2016-06-14 07:47
3730k 2016/06/14 C:\cygwin\bin\cyggcj-tools-16.dll - os=4.0 img=1.0 sys=4.0
"cyggcj-tools-16.dll" v0.0 ts=2016-06-14 07:48
44k 2016/10/10 C:\cygwin\bin\cyggdbm-4.dll - os=4.0 img=1.0 sys=4.0
"cyggdbm-4.dll" v0.0 ts=2016-10-10 18:13
14k 2016/10/10 C:\cygwin\bin\cyggdbm_compat-4.dll - os=4.0 img=1.0 sys=4.0
"cyggdbm_compat-4.dll" v0.0 ts=2016-10-10 18:13
14k 2016/06/14 C:\cygwin\bin\cyggij-16.dll - os=4.0 img=1.0 sys=4.0
"cyggij-16.dll" v0.0 ts=2016-06-14 07:48
1520k 2017/03/17 C:\cygwin\bin\cyggio-2.0-0.dll - os=4.0 img=1.0 sys=4.0
"cyggio-2.0-0.dll" v0.0 ts=2017-03-15 16:20
1056k 2017/03/17 C:\cygwin\bin\cygglib-2.0-0.dll - os=4.0 img=1.0 sys=4.0
"cygglib-2.0-0.dll" v0.0 ts=2017-03-15 16:17
16k 2017/03/17 C:\cygwin\bin\cyggmodule-2.0-0.dll - os=4.0 img=1.0 sys=4.0
"cyggmodule-2.0-0.dll" v0.0 ts=2017-03-17 20:25
506k 2017/01/21 C:\cygwin\bin\cyggmp-10.dll - os=4.0 img=1.0 sys=4.0
"cyggmp-10.dll" v0.0 ts=2017-01-21 18:25
318k 2017/03/17 C:\cygwin\bin\cyggobject-2.0-0.dll - os=4.0 img=1.0 sys=4.0
"cyggobject-2.0-0.dll" v0.0 ts=2017-03-15 16:18
113k 2016/06/14 C:\cygwin\bin\cyggomp-1.dll - os=4.0 img=1.0 sys=4.0
"cyggomp-1.dll" v0.0 ts=2016-06-14 05:49
11k 2016/06/14 C:\cygwin\bin\cyggomp-plugin-host_nonshm-1.dll - os=4.0 img=1.0 sys=4.0
"cyggomp-plugin-host_nonshm-1.dll" v0.0 ts=2016-06-14 05:50
9k 2017/03/17 C:\cygwin\bin\cyggthread-2.0-0.dll - os=4.0 img=1.0 sys=4.0
"cyggthread-2.0-0.dll" v0.0 ts=2017-03-15 16:17
820k 2017/04/01 C:\cygwin\bin\cygguile-17.dll - os=4.0 img=1.0 sys=4.0
"cygguile-17.dll" v0.0 ts=2017-04-01 13:52
1327k 2017/04/01 C:\cygwin\bin\cygguile-2.0-22.dll - os=4.0 img=1.0 sys=4.0
"cygguile-2.0-22.dll" v0.0 ts=2017-04-01 13:15
34k 2017/02/13 C:\cygwin\bin\cyghistory7.dll - os=4.0 img=1.0 sys=4.0
"cyghistory7.dll" v0.0 ts=2017-02-11 22:26
1010k 2015/02/20 C:\cygwin\bin\cygiconv-2.dll - os=4.0 img=1.0 sys=4.0
"cygiconv-2.dll" v0.0 ts=2015-02-20 16:52
42k 2016/10/23 C:\cygwin\bin\cygintl-8.dll - os=4.0 img=1.0 sys=4.0
"cygintl-8.dll" v0.0 ts=2016-10-23 07:19
1191k 2015/09/20 C:\cygwin\bin\cygisl-13.dll - os=4.0 img=1.0 sys=4.0
"cygisl-13.dll" v0.0 ts=2015-09-20 12:39
9k 2016/06/14 C:\cygwin\bin\cygjvm.dll - os=4.0 img=1.0 sys=4.0
"cygjvm.dll" v0.0 ts=2016-06-14 07:48
5k 2017/04/01 C:\cygwin\bin\cyglsa.dll - os=4.0 img=1.0 sys=4.0
"cyglsa.dll" v0.0 ts=2017-04-01 19:42
6k 2017/04/01 C:\cygwin\bin\cyglsa64.dll (not x86 dll)
36k 2016/06/28 C:\cygwin\bin\cygltdl-7.dll - os=4.0 img=1.0 sys=4.0
"cygltdl-7.dll" v0.0 ts=2016-06-28 18:57
157k 2017/05/10 C:\cygwin\bin\cyglzma-5.dll - os=4.0 img=1.0 sys=4.0
"cyglzma-5.dll" v0.0 ts=2017-05-10 03:19
133k 2017/05/03 C:\cygwin\bin\cygmagic-1.dll - os=4.0 img=1.0 sys=4.0
"cygmagic-1.dll" v0.0 ts=2017-05-03 04:09
173k 2016/10/10 C:\cygwin\bin\cygman-2-7-5.dll - os=4.0 img=1.0 sys=4.0
"cygman-2-7-5.dll" v0.0 ts=2016-10-10 22:07
21k 2016/10/10 C:\cygwin\bin\cygmandb-2-7-5.dll - os=4.0 img=1.0 sys=4.0
"cygmandb-2-7-5.dll" v0.0 ts=2016-10-10 22:08
30k 2017/06/18 C:\cygwin\bin\cygmenuw-10.dll - os=4.0 img=1.0 sys=4.0
"cygmenuw-10.dll" v0.0 ts=2017-06-18 18:48
98k 2015/03/01 C:\cygwin\bin\cygmpc-3.dll - os=4.0 img=1.0 sys=4.0
"cygmpc-3.dll" v0.0 ts=2015-03-01 20:24
374k 2017/04/08 C:\cygwin\bin\cygmpfr-4.dll - os=4.0 img=1.0 sys=4.0
"cygmpfr-4.dll" v0.0 ts=2017-04-08 12:07
56k 2017/06/18 C:\cygwin\bin\cygncurses++w-10.dll - os=4.0 img=1.0 sys=4.0
"cygncurses++w-10.dll" v0.0 ts=2017-06-18 18:53
316k 2017/06/18 C:\cygwin\bin\cygncursesw-10.dll - os=4.0 img=1.0 sys=4.0
"cygncursesw-10.dll" v0.0 ts=2017-06-18 18:47
1074k 2017/04/28 C:\cygwin\bin\cygp11-kit-0.dll - os=4.0 img=1.0 sys=4.0
"cygp11-kit-0.dll" v0.0 ts=2017-04-28 05:28
15k 2017/06/18 C:\cygwin\bin\cygpanelw-10.dll - os=4.0 img=1.0 sys=4.0
"cygpanelw-10.dll" v0.0 ts=2017-06-18 18:48
471k 2017/04/24 C:\cygwin\bin\cygpcre-1.dll - os=4.0 img=1.0 sys=4.0
"cygpcre-1.dll" v0.0 ts=2017-04-24 01:00
2162k 2017/01/15 C:\cygwin\bin\cygperl5_22.dll - os=4.0 img=1.0 sys=4.0
"cygperl5_22.dll" v0.0 ts=2017-01-15 12:24
41k 2015/04/09 C:\cygwin\bin\cygpipeline-1.dll - os=4.0 img=1.0 sys=4.0
"cygpipeline-1.dll" v0.0 ts=2015-04-09 20:58
43k 2016/07/13 C:\cygwin\bin\cygpopt-0.dll - os=4.0 img=1.0 sys=4.0
"cygpopt-0.dll" v0.0 ts=2016-07-13 06:17
500k 2016/06/14 C:\cygwin\bin\cygquadmath-0.dll - os=4.0 img=1.0 sys=4.0
"cygquadmath-0.dll" v0.0 ts=2016-06-14 06:50
223k 2017/02/13 C:\cygwin\bin\cygreadline7.dll - os=4.0 img=1.0 sys=4.0
"cygreadline7.dll" v0.0 ts=2017-02-11 22:26
11k 2015/07/17 C:\cygwin\bin\cygsigsegv-2.dll - os=4.0 img=1.0 sys=4.0
"cygsigsegv-2.dll" v0.0 ts=2015-07-17 22:33
98k 2015/03/23 C:\cygwin\bin\cygsmartcols-1.dll - os=4.0 img=1.0 sys=4.0
"cygsmartcols-1.dll" v0.0 ts=2015-03-23 09:55
1021k 2017/04/20 C:\cygwin\bin\cygsqlite3-0.dll - os=4.0 img=1.0 sys=4.0
"cygsqlite3-0.dll" v0.0 ts=2017-04-19 17:32
424k 2017/01/26 C:\cygwin\bin\cygssl-1.0.0.dll - os=4.0 img=1.0 sys=4.0
"cygssl-1.0.0.dll" v0.0 ts=2017-01-26 20:11
13k 2016/06/14 C:\cygwin\bin\cygssp-0.dll - os=4.0 img=1.0 sys=4.0
"cygssp-0.dll" v0.0 ts=2016-06-14 06:42
1439k 2016/06/14 C:\cygwin\bin\cygstdc++-6.dll - os=4.0 img=1.0 sys=4.0
"cygstdc++-6.dll" v0.0 ts=2016-06-14 06:06
69k 2017/05/29 C:\cygwin\bin\cygtasn1-6.dll - os=4.0 img=1.0 sys=4.0
"cygtasn1-6.dll" v0.0 ts=2017-05-29 23:33
56k 2017/06/18 C:\cygwin\bin\cygticw-10.dll - os=4.0 img=1.0 sys=4.0
"cygticw-10.dll" v0.0 ts=2017-06-18 18:47
1570k 2015/10/16 C:\cygwin\bin\cygunistring-2.dll - os=4.0 img=1.0 sys=4.0
"cygunistring-2.dll" v0.0 ts=2015-10-16 21:39
16k 2015/03/23 C:\cygwin\bin\cyguuid-1.dll - os=4.0 img=1.0 sys=4.0
"cyguuid-1.dll" v0.0 ts=2015-03-23 09:55
8k 2016/06/14 C:\cygwin\bin\cygvtv-0.dll - os=4.0 img=1.0 sys=4.0
"cygvtv-0.dll" v0.0 ts=2016-06-14 06:42
8k 2016/06/14 C:\cygwin\bin\cygvtv_stubs-0.dll - os=4.0 img=1.0 sys=4.0
"cygvtv_stubs-0.dll" v0.0 ts=2016-06-14 06:42
1290k 2017/03/15 C:\cygwin\bin\cygxml2-2.dll - os=4.0 img=1.0 sys=4.0
"cygxml2-2.dll" v0.0 ts=2017-03-15 20:21
87k 2017/03/03 C:\cygwin\bin\cygz.dll - os=4.0 img=1.0 sys=4.0
"cygz.dll" v0.0 ts=2017-03-03 21:51
3370k 2017/04/01 C:\cygwin\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0
"cygwin1.dll" v0.0 ts=2017-04-01 19:42
Cygwin DLL version info:
DLL version: 2.8.0
DLL epoch: 19
DLL old termios: 5
DLL malloc env: 28
Cygwin conv: 181
API major: 0
API minor: 309
Shared data: 5
DLL identifier: cygwin1
Mount registry: 3
Cygwin registry name: Cygwin
Installations name: Installations
Cygdrive default prefix:
Build date:
Shared id: cygwin1S5
Can't find the cygrunsrv utility, skipping services check.
Cygwin Package Information
Last downloaded files to: C:\Users\User\Desktop
Last downloaded files from: http://cygwin.mirror.uk.sargasso.net/
Package Version Status
_autorebase 001005-1 OK
alternatives 1.3.30c-10 OK
base-cygwin 3.8-1 OK
base-files 4.2-4 OK
bash 4.4.12-3 OK
binutils 2.25-4 OK
bzip2 1.0.6-3 OK
ca-certificates 2.14-1 OK
coreutils 8.26-2 OK
cygutils 1.4.15-2 OK
cygwin 2.8.0-1 OK
cygwin-devel 2.8.0-1 OK
dash 0.5.9.1-1 OK
desktop-file-utils 0.23-1 OK
diffutils 3.5-2 OK
editrights 1.03-1 OK
file 5.30-1 OK
findutils 4.6.0-1 OK
gamin 0.1.10-15 OK
gawk 4.1.4-3 OK
gcc-core 5.4.0-1 OK
gcc-g++ 5.4.0-1 OK
gcc-java 5.4.0-1 OK
gdb 7.10.1-1 OK
getent 2.18.90-4 OK
grep 3.0-2 OK
groff 1.22.3-1 OK
gsettings-desktop-schemas 3.22.0-1 OK
gzip 1.8-1 OK
hostname 3.13-1 OK
info 6.1-2 OK
ipc-utils 1.0-1 OK
less 487-1 OK
libargp 20110921-3 OK
libatomic1 5.4.0-1 OK
libattr1 2.4.46-1 OK
libblkid1 2.25.2-2 OK
libbz2_1 1.0.6-3 OK
libcrypt0 1.4-1 OK
libdb4.8 4.8.30-1 OK
libdb5.3 5.3.28-1 OK
libexpat1 2.2.0-0 OK
libfam0 0.1.10-15 OK
libffi6 3.2.1-1 OK
libgc1 7.6.0-1 OK
libgcc1 5.4.0-1 OK
libgcj-common 5.4.0-1 OK
libgcj16 5.4.0-1 OK
libgdbm4 1.12-1 OK
libglib2.0_0 2.50.3-1 OK
libgmp10 6.1.2-1 OK
libgomp1 5.4.0-1 OK
libguile17 1.8.8-3 OK
libguile2.0_22 2.0.14-1 OK
libiconv 1.14-3 OK
libiconv2 1.14-3 OK
libintl-devel 0.19.8.1-2 OK
libintl8 0.19.8.1-2 OK
libisl13 0.14.1-1 OK
libltdl7 2.4.6-4 OK
liblzma5 5.2.3-1 OK
libmpc3 1.0.3-1 OK
libmpfr4 3.1.5-1p2 OK
libncursesw10 6.0-11.20170617 OK
libopenssl100 1.0.2k-1 OK
libp11-kit0 0.23.5-1 OK
libpcre1 8.40-3 OK
libpipeline1 1.4.0-1 OK
libpopt-common 1.16-2 OK
libpopt0 1.16-2 OK
libquadmath0 5.4.0-1 OK
libreadline7 7.0.3-3 OK
libsigsegv2 2.10-2 OK
libsmartcols1 2.25.2-2 OK
libsqlite3_0 3.18.0-1 OK
libssp0 5.4.0-1 OK
libstdc++6 5.4.0-1 OK
libtasn1_6 4.12-1 OK
libunistring2 0.9.6-1 OK
libuuid-devel 2.25.2-2 OK
libuuid1 2.25.2-2 OK
libvtv0 5.4.0-1 OK
libxml2 2.9.4-2 OK
login 1.11-1 OK
make 4.2.1-2 OK
man-db 2.7.5-2 OK
mintty 2.7.7-0 OK
ncurses 6.0-11.20170617 OK
openssl 1.0.2k-1 OK
p11-kit 0.23.5-1 OK
p11-kit-trust 0.23.5-1 OK
patch 2.7.4-1 OK
patchutils 0.3.4-1 OK
perl 5.22.3-1 OK
perl_autorebase 5.22.3-1 OK
perl_base 5.22.3-1 OK
pkg-config 0.29.1-1 OK
Empty package python
python 2.7.13-1 OK
python2 2.7.13-1 OK
rebase 4.4.2-1 OK
run 1.3.4-2 OK
sed 4.4-1 OK
shared-mime-info 1.7-1 OK
tar 1.29-1 OK
terminfo 6.0-11.20170617 OK
tzcode 2017a-1 OK
tzdata 2017b-1 OK
util-linux 2.25.2-2 OK
vim-minimal 8.0.0647-1 OK
w32api-headers 5.0.2-1 OK
w32api-runtime 5.0.2-1 OK
which 2.20-2 OK
windows-default-manifest 6.4-1 OK
xz 5.2.3-1 OK
zlib-devel 1.2.11-1 OK
zlib0 1.2.11-1 OK
Use -h to see help about each section
[-- Attachment #3: hello.strace.out --]
[-- Type: application/octet-stream, Size: 3602 bytes --]
--- Process 2912 created
--- Process 2912 loaded C:\Windows\SysWOW64\ntdll.dll at 77720000
--- Process 2912 unloaded DLL at 77420000
--- Process 2912 unloaded DLL at 768b0000
--- Process 2912 unloaded DLL at 77420000
--- Process 2912 unloaded DLL at 77320000
--- Process 2912 loaded C:\Windows\SysWOW64\kernel32.dll at 768b0000
--- Process 2912 loaded C:\Windows\SysWOW64\KernelBase.dll at 77230000
--- Process 2912 loaded C:\cygwin\bin\cygwin1.dll at 61000000
1 1 [main] hello (2912) **********************************************
138 139 [main] hello (2912) Program name: C:\cygwin\home\User\c_dir\hello.exe (windows pid 2912)
49 188 [main] hello (2912) OS version: Windows NT-6.1
34 222 [main] hello (2912) **********************************************
91 313 [main] hello (2912) sigprocmask: 0 = sigprocmask (0, 0x0, 0x612B462C)
651 964 [main] hello 2912 open_shared: name shared.5, n 5, shared 0x60FF0000 (wanted 0x60FF0000), h 0x84, *m 6
34 998 [main] hello 2912 user_heap_info::init: heap base 0x80000000, heap top 0x80000000, heap size 0x18000000 (402653184)
30 1028 [main] hello 2912 open_shared: name S-1-5-21-3651929431-2828919770-727385248-1000.1, n 1, shared 0x60FE0000 (wanted 0x60FE0000), h 0x80, *m 6
18 1046 [main] hello 2912 user_info::create: opening user shared for 'S-1-5-21-3651929431-2828919770-727385248-1000' at 0x60FE0000
16 1062 [main] hello 2912 user_info::create: user shared version AB1FCCE8
32 1094 [main] hello 2912 fhandler_pipe::create: name \\.\pipe\cygwin-c5e39b7a9d22bafb-2912-sigwait, size 5412, mode PIPE_TYPE_MESSAGE
39 1133 [main] hello 2912 fhandler_pipe::create: pipe read handle 0x98
17 1150 [main] hello 2912 fhandler_pipe::create: CreateFile: name \\.\pipe\cygwin-c5e39b7a9d22bafb-2912-sigwait
32 1182 [main] hello 2912 fhandler_pipe::create: pipe write handle 0x9C
20 1202 [main] hello 2912 dll_crt0_0: finished dll_crt0_0 initialization
--- Process 2912 loaded C:\Windows\SysWOW64\guard32.dll at 73400000
--- Process 2912 loaded C:\Windows\SysWOW64\user32.dll at 763c0000
--- Process 2912 loaded C:\Windows\SysWOW64\gdi32.dll at 77290000
--- Process 2912 loaded C:\Windows\SysWOW64\lpk.dll at 769c0000
--- Process 2912 loaded C:\Windows\SysWOW64\usp10.dll at 77190000
--- Process 2912 loaded C:\Windows\SysWOW64\msvcrt.dll at 76f20000
--- Process 2912 loaded C:\Windows\SysWOW64\advapi32.dll at 76540000
--- Process 2912 loaded C:\Windows\SysWOW64\sechost.dll at 76610000
--- Process 2912 loaded C:\Windows\SysWOW64\rpcrt4.dll at 750b0000
--- Process 2912 loaded C:\Windows\SysWOW64\sspicli.dll at 74fc0000
--- Process 2912 loaded C:\Windows\SysWOW64\cryptbase.dll at 74fb0000
--- Process 2912 loaded C:\Windows\SysWOW64\imm32.dll at 761e0000
--- Process 2912 loaded C:\Windows\SysWOW64\msctf.dll at 753b0000
--- Process 2912 loaded C:\Windows\SysWOW64\api-ms-win-core-synch-l1-2-0.dll at 733f0000
--- Process 2912 loaded C:\Windows\SysWOW64\version.dll at 733e0000
--- Process 2912 loaded C:\Windows\SysWOW64\ole32.dll at 76240000
--- Process 2912 loaded C:\Windows\SysWOW64\shlwapi.dll at 77130000
--- Process 2912 loaded C:\Windows\SysWOW64\fltLib.dll at 733d0000
--- Process 2912 loaded C:\Windows\SysWOW64\cmdvrt32.dll at 6f4b0000
--- Process 2912 loaded C:\Windows\SysWOW64\advapi32.dll at 01d20000
--- Process 2912 unloaded DLL at 01d20000
--- Process 2912 loaded C:\Windows\SysWOW64\sechost.dll at 01d20000
--- Process 2912 unloaded DLL at 01d20000
--- Process 2912, exception c0000096 at 0028edd1
--- Process 2912 exited with status 0xc0000096
[-- Attachment #4: Type: text/plain, Size: 219 bytes --]
--
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
^ permalink raw reply [flat|nested] 24+ messages in thread* Re: Compiled programs fail to run from Cygwin Terminal, but work from windows cmd
2017-06-21 21:10 Compiled programs fail to run from Cygwin Terminal, but work from windows cmd Wouter van Doorn
@ 2017-06-21 21:49 ` René Berber
2017-06-22 13:13 ` Wouter van Doorn
2017-06-25 8:33 ` Achim Gratz
2017-06-26 19:01 ` Wouter van Doorn
2 siblings, 1 reply; 24+ messages in thread
From: René Berber @ 2017-06-21 21:49 UTC (permalink / raw)
To: cygwin
On 6/21/2017 4:10 PM, Wouter van Doorn wrote:
> Having installed Cygwin with no errors I could see, I went on to
> compile and run "hello world" - as you do. I could make it go from a
> windows command prompt after modifying the system path to include
> cygwin\bin, so - so far so good.
>
> From the cygwin terminal, however, the same executable refuses to play
> ball. No text is shown; the command prompt returns instantly.
[snip]
It could be the program itself, i.e. not coded for a Posix environment,
or it could be your PATH which should include /usr/bin (as shown, not as
a Windows path C:\...)
Easiest way to figure it out is by running:
$ ldd hello (or whatever the name of your executable is)
(sample output)
ntdll.dll => /cygdrive/c/WINDOWS/SYSTEM32/ntdll.dll (0x7ffaf6600000)
??? => ??? (0x77790000)
wow64.dll => /cygdrive/c/WINDOWS/System32/wow64.dll (0x5aa40000)
wow64win.dll => /cygdrive/c/WINDOWS/System32/wow64win.dll
(0x5aaa0000)
In this case the missing cygwin1.dll doesn't even show its name, it
happens to be the 32-bit version, because I ran ldd from a 64-bit Cygwin
on a 32-bit Cygwin program, my PATH doesn't include the cygwin 32-bit
binary directory.
And if that doesn't show the missing libraries, then even
$ file hello
could show a clue, like "PE32+ executable (GUI) x86-64 (stripped to
external PDB), for MS Windows" which is a GUI program compiled with
MinGW, i.e. doesn't depend on Cygwin. Cygwin is not mentioned in the
output of file, even a Cygwin console program shows something like "PE32
executable (console) Intel 80386, for MS Windows" or "PE32+ executable
(console) x86-64, for MS Windows".
Hope this helps.
--
R. Berber
--
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
^ permalink raw reply [flat|nested] 24+ messages in thread* Re: Compiled programs fail to run from Cygwin Terminal, but work from windows cmd
2017-06-21 21:49 ` René Berber
@ 2017-06-22 13:13 ` Wouter van Doorn
2017-06-22 13:57 ` cyg Simple
` (2 more replies)
0 siblings, 3 replies; 24+ messages in thread
From: Wouter van Doorn @ 2017-06-22 13:13 UTC (permalink / raw)
To: cygwin
Hi René,
Thanks for your attempts at having me dig deeper. So far, I am not
striking lucky. Here's the various outputs, that don't say anything
obvious to me:
User-PC-> echo $PATH
/home/User/exe.CYGWIN:/home/User/bin:/usr/local/bin:/usr/bin:/cygdrive/c/ProgramData/Oracle/Java/javapath:/cygdrive/c/Program
Files/Dell/DW WLAN
Card:/cygdrive/c/Windows/system32:/cygdrive/c/Windows:/cygdrive/c/Windows/System32/Wbem:/cygdrive/c/Windows/System32/WindowsPowerShell/v1.0:/cygdrive/c/Program
Files/WIDCOMM/Bluetooth Software:/cygdrive/c/Program
Files/WIDCOMM/Bluetooth Software/syswow64:/cygdrive/c/Program
Files/Git/cmd:/usr/bin:.:/cygrive/c/cygwin/bin:/cygdrive/c/cygwin/bin
===>so yes, /usr/bin is there.
User-PC-> ldd hello.exe
ntdll.dll => /cygdrive/c/Windows/SysWOW64/ntdll.dll (0x77720000)
kernel32.dll => /cygdrive/c/Windows/syswow64/kernel32.dll (0x768b0000)
KERNELBASE.dll => /cygdrive/c/Windows/syswow64/KERNELBASE.dll
(0x77230000)
cygwin1.dll => /usr/bin/cygwin1.dll (0x61000000)
===>no missing items
User-PC-> file hello.exe
hello.exe: PE32 executable (console) Intel 80386, for MS Windows
===>nothing here that worries me either.
Any other thoughts?
No doubt overdone, but here's the code:
User-PC-> cat hello.c
#include <stdio.h>
int main(int arg, char **argv) {
printf("Hello, world!\n");
}
and compilation was just by make hello... The simplest thing ever,
you'd say... The only real clue as far as I can see is the exception
in the last line but one of the strace output. But I don't know how to
read that.
STOP PRESS: in gdb, the output IS there:
User-PC-> gdb hello.exe
GNU gdb (GDB) (Cygwin 7.10.1-1) 7.10.1
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-cygwin".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from hello.exe...done.
(gdb) run
Starting program: /home/User/c_dir/hello.exe
[New Thread 6868.0x5b0]
[New Thread 6868.0x18dc]
[New Thread 6868.0x1990]
Hello, world!
[Thread 6868.0x1990 exited with code 0]
[Inferior 1 (process 6868) exited normally]
(gdb)
Which is dandy, but then why, outside of gdb, is there nothing at all?
Still stumped!
Wouter
On 21 June 2017 at 22:48, René Berber <rene.berber@gmail.com> wrote:
> On 6/21/2017 4:10 PM, Wouter van Doorn wrote:
>
>> Having installed Cygwin with no errors I could see, I went on to
>> compile and run "hello world" - as you do. I could make it go from a
>> windows command prompt after modifying the system path to include
>> cygwin\bin, so - so far so good.
>>
>> From the cygwin terminal, however, the same executable refuses to play
>> ball. No text is shown; the command prompt returns instantly.
> [snip]
>
> It could be the program itself, i.e. not coded for a Posix environment,
> or it could be your PATH which should include /usr/bin (as shown, not as
> a Windows path C:\...)
>
> Easiest way to figure it out is by running:
>
> $ ldd hello (or whatever the name of your executable is)
> (sample output)
> ntdll.dll => /cygdrive/c/WINDOWS/SYSTEM32/ntdll.dll (0x7ffaf6600000)
> ??? => ??? (0x77790000)
> wow64.dll => /cygdrive/c/WINDOWS/System32/wow64.dll (0x5aa40000)
> wow64win.dll => /cygdrive/c/WINDOWS/System32/wow64win.dll
> (0x5aaa0000)
>
> In this case the missing cygwin1.dll doesn't even show its name, it
> happens to be the 32-bit version, because I ran ldd from a 64-bit Cygwin
> on a 32-bit Cygwin program, my PATH doesn't include the cygwin 32-bit
> binary directory.
>
> And if that doesn't show the missing libraries, then even
>
> $ file hello
>
> could show a clue, like "PE32+ executable (GUI) x86-64 (stripped to
> external PDB), for MS Windows" which is a GUI program compiled with
> MinGW, i.e. doesn't depend on Cygwin. Cygwin is not mentioned in the
> output of file, even a Cygwin console program shows something like "PE32
> executable (console) Intel 80386, for MS Windows" or "PE32+ executable
> (console) x86-64, for MS Windows".
>
> Hope this helps.
> --
> R. Berber
>
>
> --
> 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
>
--
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
^ permalink raw reply [flat|nested] 24+ messages in thread* Re: Compiled programs fail to run from Cygwin Terminal, but work from windows cmd
2017-06-22 13:13 ` Wouter van Doorn
@ 2017-06-22 13:57 ` cyg Simple
2017-06-22 15:57 ` Wouter van Doorn
2017-06-22 14:09 ` René Berber
2017-06-22 22:33 ` Thomas Wolff
2 siblings, 1 reply; 24+ messages in thread
From: cyg Simple @ 2017-06-22 13:57 UTC (permalink / raw)
To: cygwin
>
> STOP PRESS: in gdb, the output IS there:
> User-PC-> gdb hello.exe
> GNU gdb (GDB) (Cygwin 7.10.1-1) 7.10.1
> Copyright (C) 2015 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law. Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "i686-pc-cygwin".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>.
> Find the GDB manual and other documentation resources online at:
> <http://www.gnu.org/software/gdb/documentation/>.
> For help, type "help".
> Type "apropos word" to search for commands related to "word"...
> Reading symbols from hello.exe...done.
> (gdb) run
> Starting program: /home/User/c_dir/hello.exe
> [New Thread 6868.0x5b0]
> [New Thread 6868.0x18dc]
> [New Thread 6868.0x1990]
> Hello, world!
> [Thread 6868.0x1990 exited with code 0]
> [Inferior 1 (process 6868) exited normally]
> (gdb)
>
> Which is dandy, but then why, outside of gdb, is there nothing at all?
> Still stumped!
Is your prompt overwriting the output of the program?
Try:
$ hello | cat
$ hello | grep ello
etc.
--
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
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Compiled programs fail to run from Cygwin Terminal, but work from windows cmd
2017-06-22 13:57 ` cyg Simple
@ 2017-06-22 15:57 ` Wouter van Doorn
2017-06-26 14:16 ` cyg Simple
0 siblings, 1 reply; 24+ messages in thread
From: Wouter van Doorn @ 2017-06-22 15:57 UTC (permalink / raw)
To: cygwin
Nice thought, but no, that's not it. The standard utilities behave
normally, only the things I compile myself stay schtumm.
On 22 June 2017 at 14:57, cyg Simple <cygsimple@gmail.com> wrote:
>>
>> STOP PRESS: in gdb, the output IS there:
>> User-PC-> gdb hello.exe
>> GNU gdb (GDB) (Cygwin 7.10.1-1) 7.10.1
>> Copyright (C) 2015 Free Software Foundation, Inc.
>> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
>> This is free software: you are free to change and redistribute it.
>> There is NO WARRANTY, to the extent permitted by law. Type "show copying"
>> and "show warranty" for details.
>> This GDB was configured as "i686-pc-cygwin".
>> Type "show configuration" for configuration details.
>> For bug reporting instructions, please see:
>> <http://www.gnu.org/software/gdb/bugs/>.
>> Find the GDB manual and other documentation resources online at:
>> <http://www.gnu.org/software/gdb/documentation/>.
>> For help, type "help".
>> Type "apropos word" to search for commands related to "word"...
>> Reading symbols from hello.exe...done.
>> (gdb) run
>> Starting program: /home/User/c_dir/hello.exe
>> [New Thread 6868.0x5b0]
>> [New Thread 6868.0x18dc]
>> [New Thread 6868.0x1990]
>> Hello, world!
>> [Thread 6868.0x1990 exited with code 0]
>> [Inferior 1 (process 6868) exited normally]
>> (gdb)
>>
>> Which is dandy, but then why, outside of gdb, is there nothing at all?
>> Still stumped!
>
> Is your prompt overwriting the output of the program?
>
> Try:
>
> $ hello | cat
> $ hello | grep ello
>
> etc.
>
> --
> 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
>
--
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
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Compiled programs fail to run from Cygwin Terminal, but work from windows cmd
2017-06-22 15:57 ` Wouter van Doorn
@ 2017-06-26 14:16 ` cyg Simple
2017-06-26 18:51 ` Wouter van Doorn
0 siblings, 1 reply; 24+ messages in thread
From: cyg Simple @ 2017-06-26 14:16 UTC (permalink / raw)
To: cygwin
On 6/22/2017 11:57 AM, Wouter van Doorn wrote:
>>
>> Is your prompt overwriting the output of the program?
>>
>> Try:
>>
>> $ hello | cat
>> $ hello | grep ello
>>
>> etc.
>
> On 22 June 2017 at 14:57, cyg Simple <cygsimple@gmail.com> wrote:
> Nice thought, but no, that's not it. The standard utilities behave
> normally, only the things I compile myself stay schtumm.
>
I've not seen you explain your compile and link process; assuming is a
bad idea. I've not seen any attachments as per the problems link in
every email in this thread. What is the output of uname -a, gcc -v and
ld -v?
--
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
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Compiled programs fail to run from Cygwin Terminal, but work from windows cmd
2017-06-26 14:16 ` cyg Simple
@ 2017-06-26 18:51 ` Wouter van Doorn
0 siblings, 0 replies; 24+ messages in thread
From: Wouter van Doorn @ 2017-06-26 18:51 UTC (permalink / raw)
To: cygwin
Hello again!
Thanks for your continued support.
Answers to your questions will follow, but I do need to say first that
there has been progress, and although the wy of getting there was
extremely vague, things now do work properly. I'll say more in a
general reply later. So the urgency is gone, but I still fail to
understand what happened. I can live with that, though not gladly.
Anyway.
Compiling/linking is done in the most elementary way, via make with no
makefile (so make hello from the source hello.c). Furthermore:
$ uname -a
CYGWIN_NT-6.1-WOW User-PC 2.8.0(0.309/5/3) 2017-04-01 20:42 i686 Cygwin
$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/i686-pc-cygwin/5.4.0/lto-wrapper.exe
Target: i686-pc-cygwin
Configured with:
/cygdrive/i/szsz/tmpp/gcc/gcc-5.4.0-1.i686/src/gcc-5.4.0/configure
--srcdir=/cygdrive/i/szsz/tmpp/gcc/gcc-5.4.0-1.i686/src/gcc-5.4.0
--prefix=/usr --exec-prefix=/usr --localstatedir=/var
--sysconfdir=/etc --docdir=/usr/share/doc/gcc
--htmldir=/usr/share/doc/gcc/html -C --build=i686-pc-cygwin
--host=i686-pc-cygwin --target=i686-pc-cygwin
--without-libiconv-prefix --without-libintl-prefix
--libexecdir=/usr/lib --enable-shared --enable-shared-libgcc
--enable-static --enable-version-specific-runtime-libs
--enable-bootstrap --enable-__cxa_atexit --with-dwarf2
--with-arch=i686 --with-tune=generic --disable-sjlj-exceptions
--enable-languages=ada,c,c++,fortran,java,lto,objc,obj-c++
--enable-graphite --enable-threads=posix --enable-libatomic
--enable-libcilkrts --enable-libgomp --enable-libitm
--enable-libquadmath --enable-libquadmath-support --enable-libssp
--enable-libada --enable-libjava --enable-libgcj-sublibs
--disable-java-awt --disable-symvers
--with-ecj-jar=/usr/share/java/ecj.jar --with-gnu-ld --with-gnu-as
--with-cloog-include=/usr/include/cloog-isl --without-libiconv-prefix
--without-libintl-prefix --with-system-zlib --enable-linker-build-id
--with-default-libstdcxx-abi=gcc4-compatible
Thread model: posix
gcc version 5.4.0 (GCC)
$ ld -v
GNU ld (GNU Binutils) 2.25.2
I am unclear about the attachments you mention - I don't know what was
expected. But the urgency is gone, even if the mystery is not.
Kind regards,
Wouter
--
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
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Compiled programs fail to run from Cygwin Terminal, but work from windows cmd
2017-06-22 13:13 ` Wouter van Doorn
2017-06-22 13:57 ` cyg Simple
@ 2017-06-22 14:09 ` René Berber
2017-06-22 16:01 ` Wouter van Doorn
2017-06-22 22:33 ` Thomas Wolff
2 siblings, 1 reply; 24+ messages in thread
From: René Berber @ 2017-06-22 14:09 UTC (permalink / raw)
To: cygwin
On 6/22/2017 8:13 AM, Wouter van Doorn wrote:
[snip]
> STOP PRESS: in gdb, the output IS there:
> User-PC-> gdb hello.exe
> GNU gdb (GDB) (Cygwin 7.10.1-1) 7.10.1
...
> Reading symbols from hello.exe...done.
> (gdb) run
> Starting program: /home/User/c_dir/hello.exe
> [New Thread 6868.0x5b0]
> [New Thread 6868.0x18dc]
> [New Thread 6868.0x1990]
> Hello, world!
> [Thread 6868.0x1990 exited with code 0]
> [Inferior 1 (process 6868) exited normally]
> (gdb)
>
> Which is dandy, but then why, outside of gdb, is there nothing at all?
What is "outside"?
Are you running this from mintty (recommended) or the Cygwin.bat cmd window?
Which shell? (i.e. echo $SHELL)
--
R. Berber
--
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
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Compiled programs fail to run from Cygwin Terminal, but work from windows cmd
2017-06-22 14:09 ` René Berber
@ 2017-06-22 16:01 ` Wouter van Doorn
2017-06-22 16:19 ` René Berber
` (2 more replies)
0 siblings, 3 replies; 24+ messages in thread
From: Wouter van Doorn @ 2017-06-22 16:01 UTC (permalink / raw)
To: cygwin
With 'outside', I meant a normal run not involving gdb at all. Sorry
if I was unclear.
Yes, it's minty, and it's /bin/bash.
Out of desperation, I have added a sleep for two seconds both before
and after the printf statement. The sleep does not happen either! The
prompt is immediately back, so it's more than just 'no output', it
seems my code never even gets started. Does this shed any new light?
On 22 June 2017 at 15:08, René Berber <rene.berber@gmail.com> wrote:
> On 6/22/2017 8:13 AM, Wouter van Doorn wrote:
>
> [snip]
>> STOP PRESS: in gdb, the output IS there:
>> User-PC-> gdb hello.exe
>> GNU gdb (GDB) (Cygwin 7.10.1-1) 7.10.1
> ...
>> Reading symbols from hello.exe...done.
>> (gdb) run
>> Starting program: /home/User/c_dir/hello.exe
>> [New Thread 6868.0x5b0]
>> [New Thread 6868.0x18dc]
>> [New Thread 6868.0x1990]
>> Hello, world!
>> [Thread 6868.0x1990 exited with code 0]
>> [Inferior 1 (process 6868) exited normally]
>> (gdb)
>>
>> Which is dandy, but then why, outside of gdb, is there nothing at all?
>
> What is "outside"?
>
> Are you running this from mintty (recommended) or the Cygwin.bat cmd window?
>
> Which shell? (i.e. echo $SHELL)
> --
> R. Berber
>
>
> --
> 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
>
--
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
^ permalink raw reply [flat|nested] 24+ messages in thread* Re: Compiled programs fail to run from Cygwin Terminal, but work from windows cmd
2017-06-22 16:01 ` Wouter van Doorn
@ 2017-06-22 16:19 ` René Berber
2017-06-22 19:11 ` Wouter van Doorn
2017-06-22 17:46 ` Soegtrop, Michael
2017-06-23 0:50 ` Andrey Repin
2 siblings, 1 reply; 24+ messages in thread
From: René Berber @ 2017-06-22 16:19 UTC (permalink / raw)
To: cygwin
On 6/22/2017 10:59 AM, Wouter van Doorn wrote:
> With 'outside', I meant a normal run not involving gdb at all. Sorry
> if I was unclear.
>
> Yes, it's minty, and it's /bin/bash.
>
> Out of desperation, I have added a sleep for two seconds both before
> and after the printf statement. The sleep does not happen either! The
> prompt is immediately back, so it's more than just 'no output', it
> seems my code never even gets started. Does this shed any new light?
Then its down to the 'weird' stuff, any anti-virus installed? (maybe
even the name hello.exe could cause an anti-virus to block it).
--
R. Berber
--
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
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Compiled programs fail to run from Cygwin Terminal, but work from windows cmd
2017-06-22 16:19 ` René Berber
@ 2017-06-22 19:11 ` Wouter van Doorn
0 siblings, 0 replies; 24+ messages in thread
From: Wouter van Doorn @ 2017-06-22 19:11 UTC (permalink / raw)
To: cygwin
Well, it's the same antivirus (comodo) that I earlier had a working
system with, and there's also the matter of it running fine under a
windows command prompt.
Thanks for all your suggestions!
On 22 June 2017 at 17:18, René Berber <rene.berber@gmail.com> wrote:
> On 6/22/2017 10:59 AM, Wouter van Doorn wrote:
>
>> With 'outside', I meant a normal run not involving gdb at all. Sorry
>> if I was unclear.
>>
>> Yes, it's minty, and it's /bin/bash.
>>
>> Out of desperation, I have added a sleep for two seconds both before
>> and after the printf statement. The sleep does not happen either! The
>> prompt is immediately back, so it's more than just 'no output', it
>> seems my code never even gets started. Does this shed any new light?
>
> Then its down to the 'weird' stuff, any anti-virus installed? (maybe
> even the name hello.exe could cause an anti-virus to block it).
> --
> R. Berber
>
>
> --
> 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
>
--
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
^ permalink raw reply [flat|nested] 24+ messages in thread
* RE: Compiled programs fail to run from Cygwin Terminal, but work from windows cmd
2017-06-22 16:01 ` Wouter van Doorn
2017-06-22 16:19 ` René Berber
@ 2017-06-22 17:46 ` Soegtrop, Michael
2017-06-23 0:50 ` Andrey Repin
2 siblings, 0 replies; 24+ messages in thread
From: Soegtrop, Michael @ 2017-06-22 17:46 UTC (permalink / raw)
To: Wouter van Doorn, cygwin
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1208 bytes --]
Dear Wouter,
when things get bizarre on Windows, I tend to use Sysinternals/Microsoft ProcMon. It is free and can be downloaded here:
https://technet.microsoft.com/en-us/sysinternals/processmonitor.aspx
ProcMon shows you all Windows system calls with parameters and error results. You should see the CreatProcess call and possibly can see why it fails. Since Cygwin in the end creates a windows process with windows system calls, it should also help for Cygwin. In case your process does start and fails during initialization, you can also see the Windows system calls it does. If there are DLLs missing, you can also see that.
Best regards,
Michael
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Christian Lamprechter
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
\x03B‹KCB”\x1c›Ø›\x19[H\x1c™\^[Ü\x1cΈ\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÜ\x1c›Ø›\x19[\Ëš\x1d^[[\x03B‘TNˆ\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÙ˜\KÃB‘^[ØÝ[Y[\x18]\x1a[ÛŽˆ\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÙ^[ØÜËš\x1d^[[\x03B•[œÝXœØÜšX™H\x1a[™›Îˆ\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÛ[\vÈÝ[œÝXœØÜšX™K\Ú[\^[\x19CBƒB
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Compiled programs fail to run from Cygwin Terminal, but work from windows cmd
2017-06-22 16:01 ` Wouter van Doorn
2017-06-22 16:19 ` René Berber
2017-06-22 17:46 ` Soegtrop, Michael
@ 2017-06-23 0:50 ` Andrey Repin
2017-06-23 19:30 ` Wouter van Doorn
2 siblings, 1 reply; 24+ messages in thread
From: Andrey Repin @ 2017-06-23 0:50 UTC (permalink / raw)
To: Wouter van Doorn, cygwin
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 1709 bytes --]
Greetings, Wouter van Doorn!
> On 22 June 2017 at 15:08, René Berber wrote:
>> On 6/22/2017 8:13 AM, Wouter van Doorn wrote:
>>
>> [snip]
>>> STOP PRESS: in gdb, the output IS there:
>>> User-PC-> gdb hello.exe
>>> GNU gdb (GDB) (Cygwin 7.10.1-1) 7.10.1
>> ...
>>> Reading symbols from hello.exe...done.
>>> (gdb) run
>>> Starting program: /home/User/c_dir/hello.exe
>>> [New Thread 6868.0x5b0]
>>> [New Thread 6868.0x18dc]
>>> [New Thread 6868.0x1990]
>>> Hello, world!
>>> [Thread 6868.0x1990 exited with code 0]
>>> [Inferior 1 (process 6868) exited normally]
>>> (gdb)
>>>
>>> Which is dandy, but then why, outside of gdb, is there nothing at all?
>>
>> What is "outside"?
>>
>> Are you running this from mintty (recommended) or the Cygwin.bat cmd window?
>>
>> Which shell? (i.e. echo $SHELL)
> With 'outside', I meant a normal run not involving gdb at all. Sorry
> if I was unclear.
> Yes, it's minty, and it's /bin/bash.
> Out of desperation, I have added a sleep for two seconds both before
> and after the printf statement. The sleep does not happen either! The
> prompt is immediately back, so it's more than just 'no output', it
> seems my code never even gets started. Does this shed any new light?
Did you try to rebase your program?
P.S.
And did you try to not top-post in this list? Thank you in advance.
--
With best regards,
Andrey Repin
Friday, June 23, 2017 03:48:14
Sorry for my terrible english...\x03B‹KCB”\x1c›Ø›\x19[H\x1c™\^[Ü\x1cΈ\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÜ\x1c›Ø›\x19[\Ëš\x1d^[[\x03B‘TNˆ\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÙ˜\KÃB‘^[ØÝ[Y[\x18]\x1a[ÛŽˆ\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÙ^[ØÜËš\x1d^[[\x03B•[œÝXœØÜšX™H\x1a[™›Îˆ\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÛ[\vÈÝ[œÝXœØÜšX™K\Ú[\^[\x19CBƒB
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Compiled programs fail to run from Cygwin Terminal, but work from windows cmd
2017-06-22 13:13 ` Wouter van Doorn
2017-06-22 13:57 ` cyg Simple
2017-06-22 14:09 ` René Berber
@ 2017-06-22 22:33 ` Thomas Wolff
2017-06-25 6:16 ` Wouter van Doorn
2 siblings, 1 reply; 24+ messages in thread
From: Thomas Wolff @ 2017-06-22 22:33 UTC (permalink / raw)
To: cygwin
Am 22.06.2017 um 15:13 schrieb Wouter van Doorn:
> Hi René,
>
> Thanks for your attempts at having me dig deeper. So far, I am not
> striking lucky. Here's the various outputs, that don't say anything
> obvious to me:
> User-PC-> echo $PATH
> /home/User/exe.CYGWIN:/home/User/bin:/usr/local/bin:/usr/bin:/cygdrive/c/ProgramData/Oracle/Java/javapath:...
Do you have any of make, cc or gcc in /home/Usr/exe.CYGWIN or
/home/User/bin ?
What does `type make` and `type cc` / `type gcc` say?
--
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
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Compiled programs fail to run from Cygwin Terminal, but work from windows cmd
2017-06-22 22:33 ` Thomas Wolff
@ 2017-06-25 6:16 ` Wouter van Doorn
2017-06-25 6:23 ` René Berber
0 siblings, 1 reply; 24+ messages in thread
From: Wouter van Doorn @ 2017-06-25 6:16 UTC (permalink / raw)
To: cygwin
Hello Thomas,
Thanks for looking.
The tools are the original ones, as shown below:
User@User-PC ~/c_dir
$ ./hello.exe
User@User-PC ~/c_dir
$ type make
make is hashed (/usr/bin/make)
User@User-PC ~/c_dir
$ type gcc
gcc is /usr/bin/gcc
User@User-PC ~/c_dir
$ type cc
cc is /usr/bin/cc
If you know of anything more to check, I'll try almost anything, as
this is driving me up the walls!
Kind regards,
Wouter
--
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
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Compiled programs fail to run from Cygwin Terminal, but work from windows cmd
2017-06-25 6:16 ` Wouter van Doorn
@ 2017-06-25 6:23 ` René Berber
2017-06-25 6:32 ` Wouter van Doorn
0 siblings, 1 reply; 24+ messages in thread
From: René Berber @ 2017-06-25 6:23 UTC (permalink / raw)
To: cygwin
On 6/25/2017 1:14 AM, Wouter van Doorn wrote:
> The tools are the original ones, as shown below:
> User@User-PC ~/c_dir
> $ ./hello.exe
>
> User@User-PC ~/c_dir
> $ type make
> make is hashed (/usr/bin/make)
>
> User@User-PC ~/c_dir
> $ type gcc
> gcc is /usr/bin/gcc
Try a simple:
$ gcc -o hello hello.c
$ ./hello
Take out make out of the equation, we don't know what the Makefile does
anyway (we haven't seen it).
--
R. Berber
--
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
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Compiled programs fail to run from Cygwin Terminal, but work from windows cmd
2017-06-25 6:23 ` René Berber
@ 2017-06-25 6:32 ` Wouter van Doorn
2017-06-25 16:04 ` Brian Inglis
0 siblings, 1 reply; 24+ messages in thread
From: Wouter van Doorn @ 2017-06-25 6:32 UTC (permalink / raw)
To: cygwin
Hi René,
There isn't one! The default rule does exactly that (although despite
the -o it creates a hello.exe, but that's fine.
Wouter
I'm convinced that the answer must lie hidden in the two differing
outputs of procmon, elsewhere in this thread. But I lack the knowledge
to go in deeper, and the development environment to correct it if I
didn't...
--
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
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Compiled programs fail to run from Cygwin Terminal, but work from windows cmd
2017-06-25 6:32 ` Wouter van Doorn
@ 2017-06-25 16:04 ` Brian Inglis
0 siblings, 0 replies; 24+ messages in thread
From: Brian Inglis @ 2017-06-25 16:04 UTC (permalink / raw)
To: cygwin
On 2017-06-25 00:31, Wouter van Doorn wrote:
> There isn't one! The default rule does exactly that (although despite
> the -o it creates a hello.exe, but that's fine.
It doesn't seem to be fine - is that not what you're complaining about?
Given your PATH, we don't know which make might be running, which
rules it might be using, and which programs might be producing your
hello.exe which doesn't run, running a simple "gcc -o hello hello.c"
may give you some certainty and possibly success.
In general, your Cygwin profile should prefix your Windows user PATH with
e.g. PATH=$HOME/bin:/usr/local/bin:/usr/bin:/bin:%PATH%
- append /usr/sbin;/sbin; before %PATH% to also run admin utilities.
Also your Windows user PATH should prefix your Windows system Path with utility
paths you installed and use logged on e.g. PATH ->
C:\Cygwin\usr\local\bin;C:\Cygwin\bin;%ProgramFiles%\<utility>;%ProgramFiles%\<other>\bin;...%Path%
Your Windows system Path should be prefixed with utility paths you may want to
run logged out or under other ids e.g. Path -> ...
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
--
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
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Compiled programs fail to run from Cygwin Terminal, but work from windows cmd
2017-06-21 21:10 Compiled programs fail to run from Cygwin Terminal, but work from windows cmd Wouter van Doorn
2017-06-21 21:49 ` René Berber
@ 2017-06-25 8:33 ` Achim Gratz
2017-06-25 8:50 ` Houder
2017-06-26 19:01 ` Wouter van Doorn
2 siblings, 1 reply; 24+ messages in thread
From: Achim Gratz @ 2017-06-25 8:33 UTC (permalink / raw)
To: cygwin
Wouter van Doorn writes:
[…]
Your strace shows that you're getting the following exception on loading
one of the Windows DLL or just after an attempt to do that:
C0000096: STATUS_PRIVILEGED_INSTRUCTION
Executing an instruction not allowed in current machine mode.
You might want to look if Windows' Event Viewer has something more
useful on this error.
Other than that, it appears you have installed Cygwin using a
non-administrator account (which may or may not correlate with your
problem), you are apparently using a program TVexe that might doing
strange things and your PATH is complete bunk. Since you're using a
64bit OS you'd have much less chances of encountering problems using a
64bit Cygwin I'd think.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Waldorf MIDI Implementation & additional documentation:
http://Synth.Stromeko.net/Downloads.html#WaldorfDocs
--
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
^ permalink raw reply [flat|nested] 24+ messages in thread* Re: Compiled programs fail to run from Cygwin Terminal, but work from windows cmd
2017-06-25 8:33 ` Achim Gratz
@ 2017-06-25 8:50 ` Houder
0 siblings, 0 replies; 24+ messages in thread
From: Houder @ 2017-06-25 8:50 UTC (permalink / raw)
To: cygwin
On Sun, 25 Jun 2017 10:33:17, Achim Gratz wrote:
> Wouter van Doorn writes:
> [=E2=80=A6]
>
> Your strace shows that you're getting the following exception on loading
> one of the Windows DLL or just after an attempt to do that:
>
> C0000096: STATUS_PRIVILEGED_INSTRUCTION
> Executing an instruction not allowed in current machine mode.
>
> You might want to look if Windows' Event Viewer has something more
> useful on this error.
>
> Other than that, it appears you have installed Cygwin using a
> non-administrator account (which may or may not correlate with your
> problem), you are apparently using a program TVexe that might doing
> strange things and your PATH is complete bunk. Since you're using a
Achim vraagt je hier beleefd om PATH te beperken tot uitluitend paden,
die Cygwin betreffen ... ;-)
> 64bit OS you'd have much less chances of encountering problems using a
> 64bit Cygwin I'd think.
--
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
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Compiled programs fail to run from Cygwin Terminal, but work from windows cmd
2017-06-21 21:10 Compiled programs fail to run from Cygwin Terminal, but work from windows cmd Wouter van Doorn
2017-06-21 21:49 ` René Berber
2017-06-25 8:33 ` Achim Gratz
@ 2017-06-26 19:01 ` Wouter van Doorn
2017-06-27 7:26 ` Wouter van Doorn
2 siblings, 1 reply; 24+ messages in thread
From: Wouter van Doorn @ 2017-06-26 19:01 UTC (permalink / raw)
To: cygwin
Hello Cygwin-helpers,
Many thanks to all who have responded. It was good not to sit here
alone behind my keyboard tearing my hair out.
I'll outline what has heppened next especially for the benefit of
those readers who find themselves with this same problem. It would be
nasty to leave them in the lurch if I now only said 'thanks - it's
fine now'.
But things have now taken a strange/miraculous turn for the better. It
started with a suggestion from Achim about the general crappiness of
my PATH (fair), with a very specific request concerning the path by
Houder soon after. That was to recompile/link and re-run after setting
the PATH to just /usr/bin and nothing more.
To my relief, the resulting executable worked. Not just under the
command prompt, but also under mintty this time.
From there, it seemed an easy task to find what the path component was
that caused the whole mess, but... it wasn't. Because now that it once
worked as expected, I was NEVER able to get it to go wrong again. I
re-instated the troublesome path, removed and rebuilt the executable,
and it is now still fine. Did the same after a shutdown/restart. No
change - everything is now as it should have been from the start.
So the message to those with the same problem is: try recompiling with
the PATH set to /usr/bin. After that, you may, just like me,
experience some sort of magic that means the fault disappears.
I'd rather know what was wrong, and what really happened to make the
error go away, but I can live with how it is. If developers want me to
run specific tests, I'll be very happy to do so. Otherwise, I'd say we
should consider this closed (but not forgotten).
Thanks again to all who chipped in - it was really apreciated.
Wouter
On 21 June 2017 at 22:10, Wouter van Doorn <wouter@vandoorn.tv> wrote:
> Hi,
>
> Having installed Cygwin with no errors I could see, I went on to
> compile and run "hello world" - as you do. I could make it go from a
> windows command prompt after modifying the system path to include
> cygwin\bin, so - so far so good.
>
> From the cygwin terminal, however, the same executable refuses to play
> ball. No text is shown; the command prompt returns instantly.
>
> I have tried looking in the mailing list archive, and the answer may
> well be there (in which case I apologise). But the searches I have
> tried either returned nothing, or an incredible amount of information
> that was not apparently relevant to my problem.
>
> Maybe the attached strace output tells somebody something; to me its
> only helpful thing is that it shows that the cygwin1.dll is found and
> loaded, which eliminates the most likely potential problem that I
> could see. Dependency Walker only mutters about 64-bit and 32-bit
> libraries being mixed, but as the program runs under the Windows
> command prompt, I am discounting that as a reason for the failure.
>
> All the standard pre-compiled utilities I tried run as expected from
> the cygwin terminal.
>
> I'd be very grateful for a pointer!
> Wouter van Doorn
--
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
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Compiled programs fail to run from Cygwin Terminal, but work from windows cmd
2017-06-26 19:01 ` Wouter van Doorn
@ 2017-06-27 7:26 ` Wouter van Doorn
2017-06-27 8:14 ` Soegtrop, Michael
0 siblings, 1 reply; 24+ messages in thread
From: Wouter van Doorn @ 2017-06-27 7:26 UTC (permalink / raw)
To: cygwin
Ho-hum.
One day on, and it's all reverted. Everything failing again in exactly
the same way as before. It was too good to be true...
I'll have to give up on cygwin, still appreciate the attempts at helping me.
Wouter
--
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
^ permalink raw reply [flat|nested] 24+ messages in thread
* RE: Compiled programs fail to run from Cygwin Terminal, but work from windows cmd
2017-06-27 7:26 ` Wouter van Doorn
@ 2017-06-27 8:14 ` Soegtrop, Michael
0 siblings, 0 replies; 24+ messages in thread
From: Soegtrop, Michael @ 2017-06-27 8:14 UTC (permalink / raw)
To: Wouter van Doorn, cygwin
Dear Wouter,
> One day on, and it's all reverted. Everything failing again in exactly the same way
> as before. It was too good to be true...
You might want to disassemble the good and bad binaries and compare the disassemblies. This should reveal what is going on. You can send me the binaries via private mail (as zip encrypted). Please note that the PATH has not only an influence at build time, but also at run time.
> I'll have to give up on cygwin, still appreciate the attempts at helping me.
You shouldn't. Of cause there is bogus SW which just isn't worth it, but Cygwin definitely doesn't fall into this category.
One more advice: if computers behave erratically and don't have ECC memory, it is worthwhile to run a memory test (use memtest86, burn a boot CD and run it for 1 hour - don't trust in BIOS memory tests). I see broken memory about once or twice a year.
Best regards,
Michael
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Christian Lamprechter
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
--
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
^ permalink raw reply [flat|nested] 24+ messages in thread
end of thread, other threads:[~2017-06-27 8:14 UTC | newest]
Thread overview: 24+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-06-21 21:10 Compiled programs fail to run from Cygwin Terminal, but work from windows cmd Wouter van Doorn
2017-06-21 21:49 ` René Berber
2017-06-22 13:13 ` Wouter van Doorn
2017-06-22 13:57 ` cyg Simple
2017-06-22 15:57 ` Wouter van Doorn
2017-06-26 14:16 ` cyg Simple
2017-06-26 18:51 ` Wouter van Doorn
2017-06-22 14:09 ` René Berber
2017-06-22 16:01 ` Wouter van Doorn
2017-06-22 16:19 ` René Berber
2017-06-22 19:11 ` Wouter van Doorn
2017-06-22 17:46 ` Soegtrop, Michael
2017-06-23 0:50 ` Andrey Repin
2017-06-23 19:30 ` Wouter van Doorn
2017-06-22 22:33 ` Thomas Wolff
2017-06-25 6:16 ` Wouter van Doorn
2017-06-25 6:23 ` René Berber
2017-06-25 6:32 ` Wouter van Doorn
2017-06-25 16:04 ` Brian Inglis
2017-06-25 8:33 ` Achim Gratz
2017-06-25 8:50 ` Houder
2017-06-26 19:01 ` Wouter van Doorn
2017-06-27 7:26 ` Wouter van Doorn
2017-06-27 8:14 ` Soegtrop, Michael
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).