* Bug in gzip's stdout handling
@ 2003-11-14 9:37 Thomas Hammer
2003-11-14 15:28 ` Igor Pechtchanski
2003-11-18 23:03 ` Apache with mod_perl trouble Dmitry A. Pashko
0 siblings, 2 replies; 10+ messages in thread
From: Thomas Hammer @ 2003-11-14 9:37 UTC (permalink / raw)
To: support, cygwin; +Cc: thammer
Hi.
I run the latest version of cygwin, with gzip, on WindowsXP SP1 and have a
problem with gzip. The command
$ cat binaryfile.bin | gzip -c > bin.gz
produces an invalid .gz file:
$ gunzip bin.gz
gunzip: bin.gz: invalid compressed data--crc error
gunzip: bin.gz: invalid compressed data--length error
If I do
gzip binaryfile.bin
everything works as expected - i.e. the resulting .gz file is valid.
If I do this instead:
cat binaryfile.bin > acopy.bin
The two .bin files are identical.
My gzip version:
$ gzip --version
gzip 1.3.5
(2002-09-30)
Copyright 2002 Free Software Foundation
Copyright 1992-1993 Jean-loup Gailly
This program comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of this program
under the terms of the GNU General Public License.
For more information about these matters, see the file named COPYING.
Compilation options:
DIRENT UTIME STDC_HEADERS HAVE_UNISTD_H HAVE_MEMORY_H HAVE_STRING_H
HAVE_LSTAT ASMV
Written by Jean-loup Gailly.
My conclusion is that gzip's handling of stdout is broken in some way.
The reason I report this problem, instead of just avoiding it by not using
the -c option for gzip, is that I discovered the problem while running make
dist on a Makefile.in created by automake. And it's automake that creates
the gzip command line. I'll send a patch to the automake people and ask them
to fix this - but since it's really gzip that is broken, I think it should
be fixed here too.
I think you could fix this by setting the mode for the filehandle for stdout
to O_BINARY, i.e. something like this:
#if defined (_WIN32)
setmode(FileHandle, O_BINARY); /* Make sure it is in binary mode.
*/
#endif
It would be nice if you could look into it.
Best Regards,
Thomas Hammer
hammer@sim.no
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Bug in gzip's stdout handling
2003-11-14 9:37 Bug in gzip's stdout handling Thomas Hammer
@ 2003-11-14 15:28 ` Igor Pechtchanski
2003-11-14 15:52 ` Thomas Hammer
2003-11-18 23:03 ` Apache with mod_perl trouble Dmitry A. Pashko
1 sibling, 1 reply; 10+ messages in thread
From: Igor Pechtchanski @ 2003-11-14 15:28 UTC (permalink / raw)
To: Thomas Hammer; +Cc: support, cygwin
On Fri, 14 Nov 2003, Thomas Hammer wrote:
> Hi.
>
> I run the latest version of cygwin, with gzip, on WindowsXP SP1 and have a
> problem with gzip.
Please see <http://cygwin.com/problems.html> for guidelines on how to
report Cygwin problems.
> The command
>
> $ cat binaryfile.bin | gzip -c > bin.gz
>
> produces an invalid .gz file:
>
> $ gunzip bin.gz
> gunzip: bin.gz: invalid compressed data--crc error
> gunzip: bin.gz: invalid compressed data--length error
>
> If I do
>
> gzip binaryfile.bin
>
> everything works as expected - i.e. the resulting .gz file is valid.
>
> If I do this instead:
>
> cat binaryfile.bin > acopy.bin
>
> The two .bin files are identical.
>
> My gzip version:
>
> $ gzip --version
> gzip 1.3.5
> (2002-09-30)
> Copyright 2002 Free Software Foundation
> Copyright 1992-1993 Jean-loup Gailly
> This program comes with ABSOLUTELY NO WARRANTY.
> You may redistribute copies of this program
> under the terms of the GNU General Public License.
> For more information about these matters, see the file named COPYING.
> Compilation options:
> DIRENT UTIME STDC_HEADERS HAVE_UNISTD_H HAVE_MEMORY_H HAVE_STRING_H HAVE_LSTAT ASMV
> Written by Jean-loup Gailly.
>
> My conclusion is that gzip's handling of stdout is broken in some way.
I bet you have a text mount. Please *attach* the output of "cygcheck
-svr", as per <http://cygwin.com/problems.html> - this will confirm the
guess.
> The reason I report this problem, instead of just avoiding it by not using
> the -c option for gzip, is that I discovered the problem while running make
> dist on a Makefile.in created by automake. And it's automake that creates
> the gzip command line. I'll send a patch to the automake people and ask them
> to fix this - but since it's really gzip that is broken, I think it should
> be fixed here too.
>
> I think you could fix this by setting the mode for the filehandle for stdout
> to O_BINARY, i.e. something like this:
>
> #if defined (_WIN32)
> setmode(FileHandle, O_BINARY); /* Make sure it is in binary mode. */
> #endif
FYI, Cygwin doesn't define _WIN32. Besides, the above is not a proper
patch.
Igor
> It would be nice if you could look into it.
>
> Best Regards,
> Thomas Hammer
> hammer@sim.no
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ pechtcha@cs.nyu.edu
ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster." -- Patrick Naughton
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: Bug in gzip's stdout handling
2003-11-14 15:28 ` Igor Pechtchanski
@ 2003-11-14 15:52 ` Thomas Hammer
2003-11-14 16:22 ` Igor Pechtchanski
0 siblings, 1 reply; 10+ messages in thread
From: Thomas Hammer @ 2003-11-14 15:52 UTC (permalink / raw)
To: cygwin; +Cc: support, thammer
[-- Attachment #1: Type: text/plain, Size: 1130 bytes --]
> -----Original Message-----
> From: Igor Pechtchanski [mailto:pechtcha@cs.nyu.edu]
> Sent: 14. november 2003 16:28
> To: Thomas Hammer
> Cc: support@gzip.org; cygwin@cygwin.com
> Subject: Re: Bug in gzip's stdout handling
>
Hi Igor.
Thanks for responding so promptly :).
<...>
>
> I bet you have a text mount. Please *attach* the output of "cygcheck
> -svr", as per <http://cygwin.com/problems.html> - this will confirm the
> guess.
cygcheck.out attached.
I didn't find anything about any drives being mounted as text, though.
Two small bits of info that might or might not have some value:
1) I believe this has worked earlier (i.e. 6 months ago) for a colleague of
mine, running a recent version of cygwin. Which means that something could
have been broken in cygwin after that, or (more likely) that something for
some reason is configured differently on my system.
2) When I installed cygwin, I was asked if I wanted the tools to support
Unix-style newlines or DOS-style newlines. I answered "DOS-style". I did
reinstall cygwin, specifying "Unix-style" newlines this time, and had the
same problem though.
.Thomas
[-- Attachment #2: cygcheck.out --]
[-- Type: application/octet-stream, Size: 26421 bytes --]
Cygwin Win95/NT Configuration Diagnostics
Current System Time: Fri Nov 14 16:41:14 2003
Windows XP Professional Ver 5.1 Build 2600 Service Pack 1
Path: c:\PROGRA~1\MICROS~2\Common\msdev98\BIN
c:\PROGRA~1\MICROS~2\VC98\BIN
c:\PROGRA~1\MICROS~2\Common\TOOLS\WINNT
c:\PROGRA~1\MICROS~2\Common\TOOLS
c:\programs\tools
C:\cygwin\bin
c:\WINDOWS\system32
c:\WINDOWS
c:\WINDOWS\System32\Wbem
c:\programs\putty
c:\sdk\NSIS
c:\sdk\apache-ant-1.5.4\bin
c:\sdk\j2sdk_nb\j2sdk1.4.2\bin
c:\temp\path
c:\Qt\3.2.0\bin
c:\sdk\qt\qt320debug\bin
c:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE\
c:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\Bin
c:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Tools\
c:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Tools\bin\prerelease
c:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Tools\bin
bin
c:\users\thammer\code\checkout\hammersource\misc
Output from C:\cygwin\bin\id.exe (nontsec)
UID: 1003(thammer) GID: 513(None)
513(None)
Output from C:\cygwin\bin\id.exe (ntsec)
UID: 1003(thammer) GID: 513(None)
513(None) 544(Administrators)
545(Users) 1006(Debugger Users)
SysDir: C:\WINDOWS\System32
WinDir: C:\WINDOWS
HOME = `c:\users\thammer'
MAKE_MODE = `unix'
PWD = `/cygdrive/c/users/thammer/code/config/simagedist'
USER = `thammer'
ALLUSERSPROFILE = `C:\Documents and Settings\All Users'
APPDATA = `C:\Documents and Settings\thammer\Application Data'
BLACKBOX_VC = `vc6'
CODE_CHECKOUT_U = `/cygdrive/c/users/thammer/code/checkout'
CODE_CHECKOUT_W = `c:\users\thammer\code\checkout'
CODE_CONFIG_U = `/cygdrive/c/users/thammer/code/config_vc6'
CODE_CONFIG_W = `c:\users\thammer\code\config_vc6'
CODE_DIR_U = `/cygdrive/c/users/thammer/code'
CODE_DIR_W = `c:\users\thammer\code'
CODE_INSTALL_U = `/cygdrive/c/users/thammer/code/install_vc6'
CODE_INSTALL_W = `c:\users\thammer\code\install_vc6'
COIN3DDIR = `c:\users\thammer\code\install_vc6'
COIN_SHOW_FPS_COUNTER = `1'
COMMONPATH = `c:\sdk\cl_openal\bin;C:\PROGRA~1\MICROS~2\Common\msdev98\BIN;C:\PROGRA~1\MICROS~2\VC98\BIN;C:\PROGRA~1\MICROS~2\Common\TOOLS\WINNT;C:\PROGRA~1\MICROS~2\Common\TOOLS;c:\programs\tools;c:\cygwin\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\programs\putty;C:\sdk\NSIS;C:\sdk\apache-ant-1.5.4\bin;C:\sdk\j2sdk_nb\j2sdk1.4.2\bin;C:\temp\path;C:\Qt\3.2.0\bin;C:\sdk\qt\qt320debug\bin;C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE\;C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\Bin;C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Tools\;C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Tools\bin\prerelease;C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Tools\bin;bin;C:\users\thammer\code\checkout\hammersource\misc;c:\users\thammer\code\install_vc6\bin;c:\sdk\pthreads\lib;c:\sdk\oggvorbis-win32sdk-1.0\bin;C:\programs\tmake-1.7\bin;c:\users\thammer\code\checkout\qwt;c:\sdk\xerces-c1_6_0-win32\bin;c:\sdk\libsndfile-1.0.1;c:\sdk\coldet-1.1\bin;/bin'
COMMONPROGRAMFILES = `C:\Program Files\Common Files'
COMPUTERNAME = `BLACKBOX'
COMSPEC = `C:\WINDOWS\system32\cmd.exe'
CVSROOT = `thammer@trh.sim.no:/mnt/sim1/cvsroot'
CVS_RSH = `c:\programs\tools\ssh.exe'
DEBUGPATH = `c:\sdk\qt\qt320-vc6-debug\bin'
EXPODIR = `c:\users\thammer\code\checkout\expo'
FRAMEWORKDIR = `C:\WINDOWS\Microsoft.NET\Framework\'
GUILE_LOAD_PATH = `c:\users\thammer\code\checkout\guile156-win'
HAMMERSOURCEDIR = `c:\users\thammer\code\checkout\hammersource'
HLIBDIR = `c:\users\thammer\code\checkout\hlib'
HOMEDRIVE = `C:'
HOMEPATH = `\Documents and Settings\thammer'
HOSTNAME = `usage: c:\programs\tools\hostname.exe [<ipaddress> or <name>]'
INCLUDE = `C:\PROGRA~1\MICROS~2\VC98\ATL\INCLUDE;C:\PROGRA~1\MICROS~2\VC98\INCLUDE;C:\PROGRA~1\MICROS~2\VC98\MFC\INCLUDE;C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\ATLMFC\INCLUDE;C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\Include;C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\PlatformSDK\include\prerelease;C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\PlatformSDK\include;include;C:\Program Files\Microsoft Visual Studio .NET 2003\SDK\v1.1\include\'
INFOPATH = `/usr/local/info:/usr/info:/usr/share/info:/usr/autotool/devel/info:/usr/autotool/stable/info:'
JAVA_HOME = `C:\sdk\j2sdk_nb\j2sdk1.4.2'
JSDIR = `c:\sdk\js-1.5rc4\src'
LIB = `C:\PROGRA~1\MICROS~2\VC98\LIB;C:\PROGRA~1\MICROS~2\VC98\MFC\LIB;C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\ATLMFC\LIB;C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\LIB;C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\PlatformSDK\lib\prerelease;C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\PlatformSDK\lib;lib;C:\Program Files\Microsoft Visual Studio .NET 2003\SDK\v1.1\Lib\'
LOGONSERVER = `\\BLACKBOX'
MANPATH = `/usr/local/man:/usr/man:/usr/share/man:/usr/autotool/devel/man::/usr/ssl/man'
MSDEVDIR = `C:\PROGRA~1\MICROS~2\Common\msdev98'
MSVCDIR = `C:\PROGRA~1\MICROS~2\VC98'
NUMBER_OF_PROCESSORS = `1'
OIVHOME = `C:\sdk\oiv4.0'
OS = `Windows_NT'
OSC2DIR = `c:\users\thammer\code\checkout\hammersource\osc2'
PATHEXT = `.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH'
PROCESSOR_ARCHITECTURE = `x86'
PROCESSOR_IDENTIFIER = `x86 Family 15 Model 2 Stepping 4, GenuineIntel'
PROCESSOR_LEVEL = `15'
PROCESSOR_REVISION = `0204'
PROGRAMFILES = `C:\Program Files'
PROGRAMS_DOXYGEN_U = `/cygdrive/c/programs/doxygen-1.2.8.1/bin'
PROGRAMS_TMAKE_W = `C:\programs\tmake-1.7'
PROMPT = `$P$G'
PS1 = `\[\033]0;\w\007
\033[32m\]\u@\h \[\033[33m\w\033[0m\]
$ '
QMAKESPEC = `win32-msvc.net'
QTDIR = `C:\sdk\qt\qt320debug'
RELEASEPATH = `c:\sdk\qt\qt320-vc6-release\bin'
RELEASESTATICPATH = `\bin'
SDK_COLDET_U = `/cygdrive/c/sdk/coldet-1.1'
SDK_COLDET_W = `c:\sdk\coldet-1.1'
SDK_DIR_U = `/cygdrive/c/sdk'
SDK_DIR_W = `c:\sdk'
SDK_GLUT_W = `c:\sdk\glut-3.7.6'
SDK_GUILE_U = `/cygdrive/c/users/thammer/code/checkout/guile156-win'
SDK_GUILE_W = `c:\users\thammer\code\checkout\guile156-win'
SDK_JPEG_MD_U = `/cygdrive/c/sdk/jpeg-6b/md'
SDK_JPEG_MD_W = `c:\sdk\jpeg-6b\md'
SDK_JPEG_U = `/cygdrive/c/sdk/jpeg-6b'
SDK_JPEG_W = `c:\sdk\jpeg-6b'
SDK_LIBSNDFILE_U = `/cygdrive/c/sdk/libsndfile-1.0.1'
SDK_LIBSNDFILE_W = `c:\sdk\libsndfile-1.0.1'
SDK_OGGVORBIS_U = `/cygdrive/c/sdk/oggvorbis-win32sdk-1.0'
SDK_OGGVORBIS_W = `c:\sdk\oggvorbis-win32sdk-1.0'
SDK_OPENAL_U = `/cygdrive/c/sdk/cl_openal'
SDK_OPENAL_W = `c:\sdk\cl_openal'
SDK_PLATFORMSDK_W = `c:\sdk\Microsoft SDK'
SDK_PNG_MD_U = `/cygdrive/c/sdk/lpng109/md'
SDK_PNG_MD_W = `c:\sdk\lpng109\md'
SDK_PNG_U = `/cygdrive/c/sdk/lpng109'
SDK_PNG_W = `c:\sdk\lpng109'
SDK_PTHREAD_U = `/cygdrive/c/sdk/pthreads'
SDK_PTHREAD_W = `c:\sdk\pthreads'
SDK_QT_BASE_U = `/cygdrive/c/sdk/qt'
SDK_QT_BASE_W = `c:\sdk\qt'
SDK_QT_DEBUG_U = `/cygdrive/c/sdk/qt/qt320-vc6-debug'
SDK_QT_DEBUG_W = `c:\sdk\qt\qt320-vc6-debug'
SDK_QT_RELEASE_U = `/cygdrive/c/sdk/qt/qt320-vc6-release'
SDK_QT_RELEASE_W = `c:\sdk\qt\qt320-vc6-release'
SDK_QWT_U = `/cygdrive/c/users/thammer/code/checkout/qwt'
SDK_QWT_W = `c:\users\thammer\code\checkout\qwt'
SDK_TIFF_MD_U = `/cygdrive/c/sdk/tiff-v3.5.6-beta/md/libtiff'
SDK_TIFF_MD_W = `c:\sdk\tiff-v3.5.6-beta\md\libtiff'
SDK_TIFF_U = `/cygdrive/c/sdk/tiff-v3.5.6-beta/libtiff'
SDK_TIFF_W = `c:\sdk\tiff-v3.5.6-beta\libtiff'
SDK_ZLIB_MD_U = `/cygdrive/c/sdk/zlib/md'
SDK_ZLIB_MD_W = `c:\sdk\zlib\md'
SDK_ZLIB_U = `/cygdrive/c/sdk/zlib'
SDK_ZLIB_W = `c:\sdk\zlib'
SESSIONNAME = `Console'
SHLVL = `1'
SIMBASE = `c:\users\thammer\code\checkout'
SYSTEMDRIVE = `C:'
SYSTEMROOT = `C:\WINDOWS'
TEMP = `c:\DOCUME~1\thammer\LOCALS~1\Temp'
TERM = `cygwin'
TMAKEPATH = `C:\programs\tmake-1.7\lib\win32-msvc'
TMP = `c:\DOCUME~1\thammer\LOCALS~1\Temp'
USERDOMAIN = `BLACKBOX'
USERNAME = `thammer'
USERPROFILE = `C:\Documents and Settings\thammer'
VCINSTALLDIR = `C:\Program Files\Microsoft Visual Studio .NET 2003\'
VS71COMNTOOLS = `C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Tools\'
VSCOMNTOOLS = `C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Tools\'
VSINSTALLDIR = `C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE\'
WINDIR = `C:\WINDOWS'
WXWIN = `c:\sdk\wxMSW-2.3.2'
XERCESDIR = `c:\sdk\xerces-c1_6_0-win32'
_ = `/usr/bin/cygcheck'
HKEY_CURRENT_USER\Software\Cygnus Solutions
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\Program Options
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2
(default) = `/cygdrive'
cygdrive flags = 0x00000022
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/
(default) = `C:\cygwin'
flags = 0x0000000a
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/bin
(default) = `C:\cygwin/bin'
flags = 0x0000000a
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/lib
(default) = `C:\cygwin/lib'
flags = 0x0000000a
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\Program Options
a: fd N/A N/A
c: hd NTFS 57231Mb 47% CP CS UN PA FC
d: cd N/A N/A
o: net NTFS 38115Mb 85% CP CS UN PA FC
s: net NTFS 76308Mb 70% CP CS UN PA FC
C:\cygwin / system binmode
C:\cygwin/bin /usr/bin system binmode
C:\cygwin/lib /usr/lib system binmode
. /cygdrive system binmode,cygdrive
Found: C:\cygwin\bin\awk.exe
Found: C:\cygwin\bin\bash.exe
Found: C:\cygwin\bin\cat.exe
Found: C:\cygwin\bin\cp.exe
Found: C:\cygwin\bin\cpp.exe
Found: C:\cygwin\bin\find.exe
Found: C:\cygwin\bin\gcc.exe
Found: C:\cygwin\bin\gdb.exe
Found: C:\cygwin\bin\grep.exe
Found: C:\cygwin\bin\ld.exe
Found: C:\cygwin\bin\ls.exe
Found: C:\cygwin\bin\make.exe
Found: C:\cygwin\bin\mv.exe
Found: C:\cygwin\bin\rm.exe
Found: C:\cygwin\bin\sed.exe
Found: C:\cygwin\bin\sh.exe
Found: C:\cygwin\bin\tar.exe
61k 2003/08/09 C:\cygwin\bin\cygbz2-1.dll - os=4.0 img=1.0 sys=4.0
"cygbz2-1.dll" v0.0 ts=2003/8/9 8:35
14k 2003/08/10 C:\cygwin\bin\cygcharset-1.dll - os=4.0 img=1.0 sys=4.0
"cygcharset-1.dll" v0.0 ts=2003/8/10 22:57
7k 2003/10/19 C:\cygwin\bin\cygcrypt-0.dll - os=4.0 img=1.0 sys=4.0
"cygcrypt-0.dll" v0.0 ts=2003/10/19 9:57
842k 2003/09/30 C:\cygwin\bin\cygcrypto-0.9.7.dll - os=4.0 img=1.0 sys=4.0
"cygcrypto-0.9.7.dll" v0.0 ts=2003/9/30 18:49
645k 2003/04/11 C:\cygwin\bin\cygcrypto.dll - os=4.0 img=1.0 sys=4.0
"cygcrypto.dll" v0.0 ts=2003/4/11 12:37
551k 2003/04/02 C:\cygwin\bin\cygcurl-2.dll - os=4.0 img=1.0 sys=4.0
"cygcurl-2.dll" v0.0 ts=2003/4/2 23:09
22k 2003/10/17 C:\cygwin\bin\cygcygipc-2.dll - os=4.0 img=1.0 sys=4.0
"cygcygipc-2.dll" v0.0 ts=2003/10/17 7:24
380k 2002/07/24 C:\cygwin\bin\cygdb-3.1.dll - os=4.0 img=1.0 sys=4.0
"cygdb-3.1.dll" v0.0 ts=2002/7/24 18:24
487k 2002/07/24 C:\cygwin\bin\cygdb_cxx-3.1.dll - os=4.0 img=1.0 sys=4.0
"cygdb_cxx-3.1.dll" v0.0 ts=2002/7/24 18:25
132k 2003/07/12 C:\cygwin\bin\cygexpat-0.dll - os=4.0 img=1.0 sys=4.0
"cygexpat-0.dll" v0.0 ts=2003/7/12 13:33
64k 2003/09/23 C:\cygwin\bin\cygexslt-0.dll - os=4.0 img=1.0 sys=4.0
"cygexslt-0.dll" v0.0 ts=2003/9/23 21:13
45k 2001/04/25 C:\cygwin\bin\cygform5.dll - os=4.0 img=1.0 sys=4.0
"cygform5.dll" v0.0 ts=2001/4/25 7:28
35k 2002/01/09 C:\cygwin\bin\cygform6.dll - os=4.0 img=1.0 sys=4.0
"cygform6.dll" v0.0 ts=2002/1/9 7:03
48k 2003/08/09 C:\cygwin\bin\cygform7.dll - os=4.0 img=1.0 sys=4.0
"cygform7.dll" v0.0 ts=2003/8/9 11:25
28k 2003/07/20 C:\cygwin\bin\cyggdbm-3.dll - os=4.0 img=1.0 sys=4.0
"cyggdbm-3.dll" v0.0 ts=2003/7/20 9:58
30k 2003/08/11 C:\cygwin\bin\cyggdbm-4.dll - os=4.0 img=1.0 sys=4.0
"cyggdbm-4.dll" v0.0 ts=2003/8/11 4:12
19k 2003/03/22 C:\cygwin\bin\cyggdbm.dll - os=4.0 img=1.0 sys=4.0
"cyggdbm.dll" v0.0 ts=2002/2/20 4:05
15k 2003/07/20 C:\cygwin\bin\cyggdbm_compat-3.dll - os=4.0 img=1.0 sys=4.0
"cyggdbm_compat-3.dll" v0.0 ts=2003/7/20 10:00
15k 2003/08/11 C:\cygwin\bin\cyggdbm_compat-4.dll - os=4.0 img=1.0 sys=4.0
"cyggdbm_compat-4.dll" v0.0 ts=2003/8/11 4:13
69k 2003/08/10 C:\cygwin\bin\cyggettextlib-0-12-1.dll - os=4.0 img=1.0 sys=4.0
"cyggettextlib-0-12-1.dll" v0.0 ts=2003/8/11 0:10
12k 2003/08/10 C:\cygwin\bin\cyggettextpo-0.dll - os=4.0 img=1.0 sys=4.0
"cyggettextpo-0.dll" v0.0 ts=2003/8/11 0:11
134k 2003/08/10 C:\cygwin\bin\cyggettextsrc-0-12-1.dll - os=4.0 img=1.0 sys=4.0
"cyggettextsrc-0-12-1.dll" v0.0 ts=2003/8/11 0:10
489k 2003/08/09 C:\cygwin\bin\cygguile-12.dll - os=4.0 img=1.0 sys=4.0
"cygguile-12.dll" v0.0 ts=2003/8/9 16:17
489k 2003/07/28 C:\cygwin\bin\cygguile-12abi13.dll - os=4.0 img=1.0 sys=4.0
"cygguile-12abi13.dll" v0.0 ts=2003/7/28 20:18
24k 2003/08/09 C:\cygwin\bin\cygguile-ltdl-1.dll - os=4.0 img=1.0 sys=4.0
"cygguile-ltdl-1.dll" v0.0 ts=2003/8/9 16:16
24k 2003/07/28 C:\cygwin\bin\cygguile-ltdl-1abi13.dll - os=4.0 img=1.0 sys=4.0
"cygguile-ltdl-1abi13.dll" v0.0 ts=2003/7/28 19:48
62k 2003/08/09 C:\cygwin\bin\cygguile-srfi-srfi-13-14-v-1-1.dll - os=4.0 img=1.0 sys=4.0
"cygguile-srfi-srfi-13-14-v-1-1.dll" v0.0 ts=2003/8/9 16:17
62k 2003/07/28 C:\cygwin\bin\cygguile-srfi-srfi-13-14-v-1-1abi13.dll - os=4.0 img=1.0 sys=4.0
"cygguile-srfi-srfi-13-14-v-1-1abi13.dll" v0.0 ts=2003/7/28 20:18
23k 2003/08/09 C:\cygwin\bin\cygguile-srfi-srfi-4-v-1-1.dll - os=4.0 img=1.0 sys=4.0
"cygguile-srfi-srfi-4-v-1-1.dll" v0.0 ts=2003/8/9 16:17
23k 2003/07/28 C:\cygwin\bin\cygguile-srfi-srfi-4-v-1-1abi13.dll - os=4.0 img=1.0 sys=4.0
"cygguile-srfi-srfi-4-v-1-1abi13.dll" v0.0 ts=2003/7/28 20:18
11k 2003/08/09 C:\cygwin\bin\cygguilereadline-v-12-12.dll - os=4.0 img=1.0 sys=4.0
"cygguilereadline-v-12-12.dll" v0.0 ts=2003/8/9 16:17
11k 2003/07/28 C:\cygwin\bin\cygguilereadline-v-12-12abi13.dll - os=4.0 img=1.0 sys=4.0
"cygguilereadline-v-12-12abi13.dll" v0.0 ts=2003/7/28 20:18
17k 2001/06/28 C:\cygwin\bin\cyghistory4.dll - os=4.0 img=1.0 sys=4.0
"cyghistory4.dll" v0.0 ts=2001/1/7 5:34
29k 2003/08/10 C:\cygwin\bin\cyghistory5.dll - os=4.0 img=1.0 sys=4.0
"cyghistory5.dll" v0.0 ts=2003/8/11 1:16
958k 2003/08/10 C:\cygwin\bin\cygiconv-2.dll - os=4.0 img=1.0 sys=4.0
"cygiconv-2.dll" v0.0 ts=2003/8/10 22:57
22k 2001/12/13 C:\cygwin\bin\cygintl-1.dll - os=4.0 img=1.0 sys=4.0
"cygintl-1.dll" v0.0 ts=2001/12/13 10:28
37k 2003/08/10 C:\cygwin\bin\cygintl-2.dll - os=4.0 img=1.0 sys=4.0
"cygintl-2.dll" v0.0 ts=2003/8/10 23:50
12k 2003/02/17 C:\cygwin\bin\cygioperm-0.dll - os=4.0 img=1.0 sys=4.0
"cygioperm-0.dll" v0.0 ts=2003/2/17 20:58
60k 2003/09/17 C:\cygwin\bin\cygkpathsea-3.dll - os=4.0 img=1.0 sys=4.0
"cygkpathsea-3.dll" v0.0 ts=2003/9/17 18:37
60k 2003/07/27 C:\cygwin\bin\cygkpathsea-3abi13.dll - os=4.0 img=1.0 sys=4.0
"cygkpathsea-3abi13.dll" v0.0 ts=2003/7/27 22:23
32k 2003/08/18 C:\cygwin\bin\cygltdl-3.dll - os=4.0 img=1.0 sys=4.0
"cygltdl-3.dll" v0.0 ts=2003/8/18 7:35
26k 2001/04/25 C:\cygwin\bin\cygmenu5.dll - os=4.0 img=1.0 sys=4.0
"cygmenu5.dll" v0.0 ts=2001/4/25 7:27
20k 2002/01/09 C:\cygwin\bin\cygmenu6.dll - os=4.0 img=1.0 sys=4.0
"cygmenu6.dll" v0.0 ts=2002/1/9 7:03
29k 2003/08/09 C:\cygwin\bin\cygmenu7.dll - os=4.0 img=1.0 sys=4.0
"cygmenu7.dll" v0.0 ts=2003/8/9 11:25
156k 2001/04/25 C:\cygwin\bin\cygncurses++5.dll - os=4.0 img=1.0 sys=4.0
"cygncurses++5.dll" v0.0 ts=2001/4/25 7:29
175k 2002/01/09 C:\cygwin\bin\cygncurses++6.dll - os=4.0 img=1.0 sys=4.0
"cygncurses++6.dll" v0.0 ts=2002/1/9 7:03
226k 2001/04/25 C:\cygwin\bin\cygncurses5.dll - os=4.0 img=1.0 sys=4.0
"cygncurses5.dll" v0.0 ts=2001/4/25 7:17
202k 2002/01/09 C:\cygwin\bin\cygncurses6.dll - os=4.0 img=1.0 sys=4.0
"cygncurses6.dll" v0.0 ts=2002/1/9 7:03
224k 2003/08/09 C:\cygwin\bin\cygncurses7.dll - os=4.0 img=1.0 sys=4.0
"cygncurses7.dll" v0.0 ts=2003/8/9 11:24
15k 2001/04/25 C:\cygwin\bin\cygpanel5.dll - os=4.0 img=1.0 sys=4.0
"cygpanel5.dll" v0.0 ts=2001/4/25 7:27
12k 2002/01/09 C:\cygwin\bin\cygpanel6.dll - os=4.0 img=1.0 sys=4.0
"cygpanel6.dll" v0.0 ts=2002/1/9 7:03
19k 2003/08/09 C:\cygwin\bin\cygpanel7.dll - os=4.0 img=1.0 sys=4.0
"cygpanel7.dll" v0.0 ts=2003/8/9 11:24
67k 2003/09/10 C:\cygwin\bin\cygpcre-0.dll - os=4.0 img=1.0 sys=4.0
"cygpcre-0.dll" v0.0 ts=2003/9/10 16:25
63k 2003/04/11 C:\cygwin\bin\cygpcre.dll - os=4.0 img=1.0 sys=4.0
"cygpcre.dll" v0.0 ts=2003/4/11 10:31
15k 2003/09/10 C:\cygwin\bin\cygpcreposix-0.dll - os=4.0 img=1.0 sys=4.0
"cygpcreposix-0.dll" v0.0 ts=2003/9/10 16:25
61k 2003/04/11 C:\cygwin\bin\cygpcreposix.dll - os=4.0 img=1.0 sys=4.0
"cygpcreposix.dll" v0.0 ts=2003/4/11 10:31
1100k 2003/08/29 C:\cygwin\bin\cygperl5_8_0.dll - os=4.0 img=1.0 sys=4.0
"cygperl5_8_0.dll" v0.0 ts=2003/8/29 12:20
173k 2003/08/10 C:\cygwin\bin\cygpng12.dll - os=4.0 img=1.0 sys=4.0
"cygpng12.dll" v0.0 ts=2003/8/11 0:35
22k 2002/06/09 C:\cygwin\bin\cygpopt-0.dll - os=4.0 img=1.0 sys=4.0
"cygpopt-0.dll" v0.0 ts=2002/6/9 7:45
108k 2001/06/28 C:\cygwin\bin\cygreadline4.dll - os=4.0 img=1.0 sys=4.0
"cygreadline4.dll" v0.0 ts=2001/1/7 5:34
148k 2003/08/10 C:\cygwin\bin\cygreadline5.dll - os=4.0 img=1.0 sys=4.0
"cygreadline5.dll" v0.0 ts=2003/8/11 1:16
682k 2003/10/11 C:\cygwin\bin\cygruby18.dll - os=4.0 img=1.0 sys=4.0
"cygruby18.dll" v0.0 ts=2003/10/11 13:41
171k 2003/09/30 C:\cygwin\bin\cygssl-0.9.7.dll - os=4.0 img=1.0 sys=4.0
"cygssl-0.9.7.dll" v0.0 ts=2003/9/30 18:49
165k 2003/04/11 C:\cygwin\bin\cygssl.dll - os=4.0 img=1.0 sys=4.0
"cygssl.dll" v0.0 ts=2003/4/11 12:37
1074k 2003/09/23 C:\cygwin\bin\cygxml2-2.dll - os=4.0 img=1.0 sys=4.0
"cygxml2-2.dll" v0.0 ts=2003/9/23 19:52
196k 2003/09/23 C:\cygwin\bin\cygxslt-1.dll - os=4.0 img=1.0 sys=4.0
"cygxslt-1.dll" v0.0 ts=2003/9/23 20:58
7k 2003/09/23 C:\cygwin\bin\cygxsltbreakpoint-1.dll - os=4.0 img=1.0 sys=4.0
"cygxsltbreakpoint-1.dll" v0.0 ts=2003/9/23 21:06
60k 2003/08/09 C:\cygwin\bin\cygz.dll - os=4.0 img=1.0 sys=4.0
"cygz.dll" v0.0 ts=2003/8/9 8:28
949k 2003/09/20 C:\cygwin\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0
"cygwin1.dll" v0.0 ts=2003/9/20 22:31
Cygwin DLL version info:
DLL version: 1.5.5
DLL epoch: 19
DLL bad signal mask: 19005
DLL old termios: 5
DLL malloc env: 28
API major: 0
API minor: 94
Shared data: 3
DLL identifier: cygwin1
Mount registry: 2
Cygnus registry name: Cygnus Solutions
Cygwin registry name: Cygwin
Program options name: Program Options
Cygwin mount registry name: mounts v2
Cygdrive flags: cygdrive flags
Cygdrive prefix: cygdrive prefix
Cygdrive default prefix:
Build date: Sat Sep 20 16:31:15 EDT 2003
CVS tag: cr-0x9b
Shared id: cygwin1S3
Cygwin Package Information
Last downloaded files to: C:\temp\cygwin
Last downloaded files from: ftp://ftp-stud.fht-esslingen.de/pub/Mirrors/sources.redhat.com/cygwin
Package Version
_update-info-dir 00221-1
ash 20031007-1
astyle 1.15.3-3
autoconf 2.57a-1
autoconf-devel 2.57-2
autoconf-stable 2.13-5
automake 1.7.5a-1
automake-devel 1.7.6-2
automake-stable 1.4p5-6
base-files 2.6-1
base-passwd 1.1-1
bash 2.05b-16
binutils 20030901-1
bison 20030307-1
byacc 1.9-1
bzip2 1.0.2-5
c-client 2002e-3
ccache 2.2-1
ccdoc 0.8.39-1
clisp 2.31-2
cmake 1.8.1-1
cocom 0.995-1
compface 1.4-5
crypt 1.1-1
ctags 5.5-4
curl 7.10.4-1
curl-devel 7.10.4-1
cvs 1.11.6-3
cygipc 2.02-1
cygwin 1.5.5-1
dejagnu 20021217-2
diffutils 2.8.4-1
doxygen 1.2.18-1
dpkg 1.10.4-2
editrights 1.01-1
ELFIO 1.0.0-1
expat 1.95.6-2
expect 20030128-1
file 4.03-2
fileutils 4.1-2
findutils 4.1.7-4
flex 2.5.4a-3
gawk 3.1.3-3
gcc 3.3.1-2
gcc-mingw 20030911-3
gcc2 2.95.3-10
gdb 20030919-1
gdbm 1.8.3-7
gettext 0.12.1-3
gettext-devel 0.12.1-3
gperf 2.7.2-1
grep 2.5-1
groff 1.18.1-2
guile 1.6.4-12
guile-devel 1.6.4-12
gzip 1.3.5-1
indent 2.2.8-1
ioperm 0.4-1
less 381-1
lftp 2.6.6-1
libbz2_1 1.0.2-5
libcharset1 1.9.1-3
libdb3.1 3.1.17-2
libgdbm 1.8.0-5
libgdbm-devel 1.8.3-7
libgdbm3 1.8.3-3
libgdbm4 1.8.3-7
libgettextpo0 0.12.1-3
libguile12 1.6.4-12
libguile12abi13 1.6.4-2
libiconv 1.9.1-3
libiconv2 1.9.1-3
libintl1 0.10.40-1
libintl2 0.12.1-3
libkpathsea3 2.0.2-13
libkpathsea3abi13 2.0.2-2
libltdl3 1.5-3
libncurses-devel 5.3-4
libncurses5 5.2-1
libncurses6 5.2-8
libncurses7 5.3-4
libpcre 4.1-1
libpcre0 4.4-2
libpng12 1.2.5-4
libpopt0 1.6.4-4
libreadline4 4.1-2
libreadline5 4.3-5
libtool 1.5a-1
libtool-devel 1.5-3
libtool-stable 1.4.3-2
libxml2 2.5.11-1
libxslt 1.0.33-1
login 1.9-7
lynx 2.8.4-7
m4 1.4-1
make 3.80-1
man 1.5j-2
mingw-runtime 3.2-1
mktemp 1.5-3
nasm 0.98.38-1
ncftp 3.1.4-1
ncurses 5.3-4
openssh 3.7.1p2-1
openssl 0.9.7c-1
openssl-devel 0.9.7c-1
openssl096 0.9.6j-1
patch 2.5.8-8
patchutils 0.2.22-2
pcre 4.4-2
pcre-devel 4.4-2
pcre-doc 4.4-2
perl 5.8.0-5
pkgconfig 0.15.0-4
rcs 5.7-3
readline 4.3-5
ruby 1.8.0-2
sed 4.0.7-3
sh-utils 2.0.15-4
splint 3.1.1-1
stunnel 4.04-3
SWI-Prolog 5.2.6-1
swig 1.3.19-1
tar 1.13.25-3
tcltk 20030901-1
termcap 20021106-2
terminfo 5.3_20030726-1
tetex-devel 2.0.2-13
texinfo 4.2-4
textutils 2.0.21-1
unzip 5.50-5
uw-imap 2002e-3
w32api 2.4-1
wget 1.8.2-2
which 1.5-2
xerces-c-devel 2.3.0-4
zip 2.3-5
zlib 1.1.4-4
Use -h to see help about each section
[-- Attachment #3: Type: text/plain, Size: 218 bytes --]
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: Bug in gzip's stdout handling
2003-11-14 15:52 ` Thomas Hammer
@ 2003-11-14 16:22 ` Igor Pechtchanski
0 siblings, 0 replies; 10+ messages in thread
From: Igor Pechtchanski @ 2003-11-14 16:22 UTC (permalink / raw)
To: Thomas Hammer; +Cc: cygwin
I've removed <support at gzip dot org> from this discussion. So far this
is Cygwin-related, and you can update them later on the results if it
turns out to be a generic gzip issue.
On Fri, 14 Nov 2003, Thomas Hammer wrote:
> > -----Original Message-----
> > From: Igor Pechtchanski [mailto:pechtcha@cs.nyu.edu]
> > Sent: 14. november 2003 16:28
> > To: Thomas Hammer
> > Cc: support@gzip.org; cygwin@cygwin.com
> > Subject: Re: Bug in gzip's stdout handling
> >
>
> Hi Igor.
>
> Thanks for responding so promptly :).
>
> <...>
>
> >
> > I bet you have a text mount. Please *attach* the output of "cygcheck
> > -svr", as per <http://cygwin.com/problems.html> - this will confirm the
> > guess.
>
> cygcheck.out attached.
>
> I didn't find anything about any drives being mounted as text, though.
>
> Two small bits of info that might or might not have some value:
>
> 1) I believe this has worked earlier (i.e. 6 months ago) for a colleague of
> mine, running a recent version of cygwin. Which means that something could
> have been broken in cygwin after that, or (more likely) that something for
> some reason is configured differently on my system.
>
> 2) When I installed cygwin, I was asked if I wanted the tools to support
> Unix-style newlines or DOS-style newlines. I answered "DOS-style". I did
> reinstall cygwin, specifying "Unix-style" newlines this time, and had the
> same problem though.
>
> .Thomas
(2) shows that you used to have text mounts. Your cygcheck.out shows
binary mounts, so that's probably not the problem.
Please try the following: "sed '' binaryfile.bin > acopy.bin" and compare
the files. Also "echo | sed '' > test.out; od -c test.out" and "perl -e
'print q{ }x2560' | gzip -c > test.gz; od -c test.gz".
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ pechtcha@cs.nyu.edu
ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster." -- Patrick Naughton
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
^ permalink raw reply [flat|nested] 10+ messages in thread
* Apache with mod_perl trouble
2003-11-14 9:37 Bug in gzip's stdout handling Thomas Hammer
2003-11-14 15:28 ` Igor Pechtchanski
@ 2003-11-18 23:03 ` Dmitry A. Pashko
2003-11-19 10:27 ` Patrick Eisenacher
1 sibling, 1 reply; 10+ messages in thread
From: Dmitry A. Pashko @ 2003-11-18 23:03 UTC (permalink / raw)
To: cygwin
Hi!
Has somebody a positive experience of use of a Apache+mod_perl 1.3.28 or
1.3.29 with perl 5.8.2-1?
All perfectly worked for me with perl 5.8.0. However after updating perl
to version 5.8.2 the server has ceased to start. I rebuild a Apache, but
have changed nothing it.
In Event Log thus the following message is written:
httpd-perl : PID 45680 : starting service `httpd-perl' failed:
execv: 128, Transport endpoint is not connected.
Under a debugger I have detected, that at initialization perl there is a
SEGFAULT near perl_construct() (mod_perl.c, perl_startup function).
Any idea to resolve thes fault?
Dmitry Pashko
dmitry@pashko.ru
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Apache with mod_perl trouble
2003-11-18 23:03 ` Apache with mod_perl trouble Dmitry A. Pashko
@ 2003-11-19 10:27 ` Patrick Eisenacher
2003-11-19 11:06 ` Dmitry A. Pashko
0 siblings, 1 reply; 10+ messages in thread
From: Patrick Eisenacher @ 2003-11-19 10:27 UTC (permalink / raw)
To: Dmitry A. Pashko; +Cc: cygwin
Hi Dmitry,
I experienced similar problems with exim and perl v5.8.2-1, see
http://cygwin.com/ml/cygwin/2003-11/msg00434.html. As soon as exim tries
to start the perl interpreter, it crashs. I had to downgrade to perl
v5.8.0-3 again. Perl v5.8.2-1 seems to be broken.
Patrick
Dmitry A. Pashko schrieb:
> Hi!
>
> Has somebody a positive experience of use of a Apache+mod_perl 1.3.28 or
> 1.3.29 with perl 5.8.2-1?
> All perfectly worked for me with perl 5.8.0. However after updating perl
> to version 5.8.2 the server has ceased to start. I rebuild a Apache, but
> have changed nothing it.
>
> In Event Log thus the following message is written:
> httpd-perl : PID 45680 : starting service `httpd-perl' failed:
> execv: 128, Transport endpoint is not connected.
>
> Under a debugger I have detected, that at initialization perl there is a
> SEGFAULT near perl_construct() (mod_perl.c, perl_startup function).
>
> Any idea to resolve thes fault?
>
> Dmitry Pashko
> dmitry@pashko.ru
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: Apache with mod_perl trouble
2003-11-19 10:27 ` Patrick Eisenacher
@ 2003-11-19 11:06 ` Dmitry A. Pashko
2003-12-10 23:31 ` dominix
0 siblings, 1 reply; 10+ messages in thread
From: Dmitry A. Pashko @ 2003-11-19 11:06 UTC (permalink / raw)
To: 'Patrick Eisenacher'; +Cc: cygwin
Hi Patrick,
Your hypothesis is close to true. I have returned to version 5.8.0-5
too.
There is a question to Gerrit P. Haase.
Is the given problem refers to version 5.8.2 in general? Or it concerns
only Cygwin perl build?
Dmitry Pashko
dmitry@pashko.ru
| -----Original Message-----
| From: Patrick Eisenacher [mailto:eisenacher@fillmore-labs.com]
| Sent: Wednesday, November 19, 2003 1:28 PM
| To: Dmitry A. Pashko
| Cc: cygwin@cygwin.com
| Subject: Re: Apache with mod_perl trouble
|
|
| Hi Dmitry,
|
| I experienced similar problems with exim and perl v5.8.2-1, see
| http://cygwin.com/ml/cygwin/2003-11/msg00434.html. As soon as
| exim tries
| to start the perl interpreter, it crashs. I had to downgrade to perl
| v5.8.0-3 again. Perl v5.8.2-1 seems to be broken.
|
|
| Patrick
|
| Dmitry A. Pashko schrieb:
|
| > Hi!
| >
| > Has somebody a positive experience of use of a
| Apache+mod_perl 1.3.28 or
| > 1.3.29 with perl 5.8.2-1?
| > All perfectly worked for me with perl 5.8.0. However after
| updating perl
| > to version 5.8.2 the server has ceased to start. I rebuild
| a Apache, but
| > have changed nothing it.
| >
| > In Event Log thus the following message is written:
| > httpd-perl : PID 45680 : starting service `httpd-perl' failed:
| > execv: 128, Transport endpoint is not connected.
| >
| > Under a debugger I have detected, that at initialization
| perl there is a
| > SEGFAULT near perl_construct() (mod_perl.c, perl_startup function).
| >
| > Any idea to resolve thes fault?
| >
| > Dmitry Pashko
| > dmitry@pashko.ru
|
|
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Apache with mod_perl trouble
2003-11-19 11:06 ` Dmitry A. Pashko
@ 2003-12-10 23:31 ` dominix
0 siblings, 0 replies; 10+ messages in thread
From: dominix @ 2003-12-10 23:31 UTC (permalink / raw)
To: cygwin
Dmitry A. Pashko wrote:
> Hi Patrick,
>
> Your hypothesis is close to true. I have returned to version 5.8.0-5
> too.
>
I'm in the same troubles, where are the packages to downgrade to 5.8.0 ?
BTW did someone try with a perl-5.8.2 WITHOUT ithread (or with differents
compile options ? )
regards
--
dominix
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: Bug in gzip's stdout handling
2003-11-17 22:19 Bug in gzip's stdout handling Thomas Hammer
@ 2003-11-18 18:51 ` Igor Pechtchanski
0 siblings, 0 replies; 10+ messages in thread
From: Igor Pechtchanski @ 2003-11-18 18:51 UTC (permalink / raw)
To: Thomas Hammer; +Cc: cygwin
On Mon, 17 Nov 2003, Thomas Hammer wrote:
> > -----Original Message-----
> > From: Igor Pechtchanski [mailto:pechtcha@cs.nyu.edu]
> > Sent: 14. november 2003 17:22
> > To: Thomas Hammer
> > Cc: cygwin@cygwin.com
> > Subject: RE: Bug in gzip's stdout handling
> >
> <...>
>
> Hi Igor,
>
> This turned out to be a very long mail, so here's the summary:
> - I figured it out. I had forgotten to delete the original mount table from
> the registry before reinstalling cygwin. All my drives were still mounted in
> textmode, and that's why cat and redirection failed.
> - I don't know why mount and cygcheck -svr gives different reports regarding
> mount mode.
> - I have one question it would be nice if you answered. It's at the end of
> the email.
>
> And here's the rest of the email:
>
> >
> > (2) shows that you used to have text mounts. Your cygcheck.out shows
> > binary mounts, so that's probably not the problem.
>
> I forgot to mention that I reverted to my original version of cygwin (with
> DOS-style newlines) when I discovered that using UNIX-style newlines didn't
> fix the problem.
>
> I did the following:
>
> 1) Renamed c:\cygwin to c:\cygwin_old
> 2) Reinstalled cygwin, specifying UNIX-style newlines when asked
> 3) Test if "cat file.bin | gzip -c > filecopy.gz" produced a valig gz-file.
> It didn't
> 4) Deleted c:\cygwin and renamed c:\cygwin_old to c:\cygwin
>
> I did not delete the registry keys or the local cygwin package directory. I
> don't know is this matters or not.
>
> I didn't know about text vs binary mounts until you mentioned it, and did
> some reading up. One weird thing I came accross is that if I run mount, the
> information seems to conflict with the information from cygcheck -svr.
>
> $ mount
> C:\cygwin\bin on /usr/bin type system (textmode)
> C:\cygwin\lib on /usr/lib type system (textmode)
> C:\cygwin on / type system (textmode)
> c: on /cygdrive/c type user (textmode,noumount)
> s: on /cygdrive/s type user (textmode,noumount)
>
> The relevant lines from cygcheck -svr:
>
> a: fd N/A N/A
> c: hd NTFS 57231Mb 47% CP CS UN PA FC
> d: cd N/A N/A
> o: net N/A N/A
> s: net NTFS 76308Mb 76% CP CS UN PA FC
>
> C:\cygwin / system binmode
> C:\cygwin/bin /usr/bin system binmode
> C:\cygwin/lib /usr/lib system binmode
> . /cygdrive system binmode,cygdrive
>
>
> It looks to me as if mount claims all mounts are text mounts (which would
> explain my problems, I guess). Whereas cygcheck -svr claims all my mounts
> are binmode.
>
> I'm beginning to wonder if I did something wrong when reinstalling cygwin
> and specifying binary mode. I'm giving it another try now.
>
> 1) Renamed c:\cygwin to c:\cygwin_old
> 2) Renamed the HKCU\Software\Cygnus Solutions registry key
> 3) Renamed the local cygwin package dir.
> 4) Reinstalled cygwin, specifying UNIX-style newlines when asked
> 5) Test if "cat file.bin | gzip -c > filecopy.gz" produced a valig gz-file.
>
> It didn't.
>
> Running mount gives the same result as before (shows textmode on all
> mounts).
>
> I tried installing cygwin (downloaded setup.exe from www.cygwin.com) from
> scratch on another computer in my office. That computer also runs WindowsXP.
> $HOME wasn't defined here, but it was on my primary computer. Don't know if
> that mattered.
>
> On that computer, mount shows all mountpoints as being of type binmode, and
> "cat file.bin | gzip -c > out.bin" works as it should.
>
> I have no Idea why my primary computer insists on mounting everything in
> textmode :-(.
>
> I did try to remove my .bashrc-file on my primary computer. It didn't help -
> and I couldn't find anything in there related to mounting.
>
> I wonder where the mount table is stored. Maybe it for some reason survived
> a reinstall of cygwin...
>
> Please read on for some more discoveries.
>
> >
> > Please try the following: "sed '' binaryfile.bin > acopy.bin" and compare
> > the files. Also "echo | sed '' > test.out; od -c test.out" and "perl -e
> > 'print q{ }x2560' | gzip -c > test.gz; od -c test.gz".
>
> thammer@blackbox /cygdrive/c/temp/temp
> $ echo | sed '' >test.out
>
> thammer@blackbox /cygdrive/c/temp/temp
> $ od -c test.out
> 0000000 \r \n
> 0000002
>
> thammer@blackbox /cygdrive/c/temp/temp
> $ perl -e 'print q{ }x2560' | gzip -c > test.gz
>
> thammer@blackbox /cygdrive/c/temp/temp
> $ od -c test.gz
> 0000000 037 213 \b \0 = . 271 ? \0 003 355 301 201 \0 \0 \0
> 0000020 \0 303 225 371 S 036 344 U 001 \0 360 d 6 271 357
> 0000040 252 \0 \r \n \0 \0
> 0000046
>
> Back to the mounting thread of thought.
>
> I tried to mount a directory as binary:
>
> $ mount -b c:\\temp\\temp\\t /mytest
> mount: warning - /mytest does not exist.
>
> $ cd /mytest
>
> thammer@blackbox /mytest
> $ echo | sed '' >test.out; od -c test.out
> 0000000 \n
> 0000001
>
> Hey, I'm getting somewhere :-).
>
> thammer@blackbox /mytest
> $ ls -l
> total 109
> -rwx------ 1 thammer mkgroup 110755 Nov 17 21:51 bin.jpg
>
> thammer@blackbox /mytest
> $ cat bin.jpg | gzip -c > another.jpg.gz
>
> thammer@blackbox /mytest
> $ gunzip another.jpg.gz
>
> thammer@blackbox /mytest
> $ ls -l
> total 218
> -rw-r--r-- 1 thammer mkgroup 110755 Nov 17 22:08 another.jpg
> -rwx------ 1 thammer mkgroup 110755 Nov 17 21:51 bin.jpg
>
> thammer@blackbox /mytest
> $ comp another.jpg bin.jpg
> Comparing another.jpg and bin.jpg...
> Files compare OK
>
> I think there's something fishy about the mount table and where it's
> located. I think it is for some reason stored _outside_ the c:\cygwin
> directory. Which means it won't get updated when I do a reinstall of cygwin.
>
> To verify this, I renamed c:\cygwin to c:\cygwin_new, and c:\cygwin_old to
> c:\cygwin, and opened a bash shell.
>
> thammer@blackbox /
> $ mount
> c:\temp\temp\t on /mytest type system (binmode)
> C:\cygwin\bin on /usr/bin type system (textmode)
> C:\cygwin\lib on /usr/lib type system (textmode)
> c:\cygwin on / type system (textmode)
> c: on /cygdrive/c type user (textmode,noumount)
> s: on /cygdrive/s type user (textmode,noumount)
>
> Hey! The /mytest mount is still there, as I suspected.
>
> Where could that mount table be....
>
> RTFM :).
>
> When I reinstalled cygwin, I forgot to delete the "HKLM\Software\Cygnus
> Solutions" registry subtree, I just deleted the "HKCU\Software\Cygnus
> Solutions" subtree.
>
> Oh well.
>
> ...
>
> I have one final question I would be very happy if you could answer:
>
> The problem I originally reported to you can be solved by myself by making
> sure that I specifically mount the directory I'm working in in binmode. I
> consider this an acceptable solution, but I don't feel good about it. I'm
> going to have to put this in makefiles that will be distributed to our
> customers, some of which might have text mounts, and having mount
> instructions there seems plain wrong.
>
> The question is this: Is there any way that I _from_the_commandline_ can
> force all programs and the shell (for redirection) to use binary mode even
> if the file is on a drive that is mounted in textmode? I'd like to do
> something like this:
>
> CYGWIN=somemagicstring bash -c cat file.bin | gzip -c > file2.bin.gz
>
> /* Actually it would be more like this, with the gzip command
> deep within the Makefile :
> CYGWIN=somemagicstring bash -c make dist
> */
>
> I tried s/somemagicstring/binmode/, and s/somemagicstring/tty/, but neither
> did me any good.
>
> If you have any suggestions as to if it's possible to avoid depending on a
> binary mount, I'd be happy to hear it.
>
> Thanks for the help so far :).
>
> .Thomas
Thomas,
No, there is no such environment variable. You'll just have to make sure
your mounts are all binmode. Fortunately, there's an easy way to do this
(using mount):
$ eval "`mount -m | egrep '"(/|/usr/(bin|lib))"' | sed 's/ -t / -b /'`"
The above will remount your textmode mounts for '/', '/usr/bin' and
'/usr/lib' to binmode (be they system or user, as long as you have the
appropriate privileges). This shouldn't cause any problems with the rest
of your system (unless you have some program that specifically relies on
its files being in textmode, in which case you can mount that program's
data directory separately).
HTH,
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ pechtcha@cs.nyu.edu
ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster." -- Patrick Naughton
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: Bug in gzip's stdout handling
@ 2003-11-17 22:19 Thomas Hammer
2003-11-18 18:51 ` Igor Pechtchanski
0 siblings, 1 reply; 10+ messages in thread
From: Thomas Hammer @ 2003-11-17 22:19 UTC (permalink / raw)
To: pechtcha; +Cc: cygwin, thammer
> -----Original Message-----
> From: Igor Pechtchanski [mailto:pechtcha@cs.nyu.edu]
> Sent: 14. november 2003 17:22
> To: Thomas Hammer
> Cc: cygwin@cygwin.com
> Subject: RE: Bug in gzip's stdout handling
>
<...>
Hi Igor,
This turned out to be a very long mail, so here's the summary:
- I figured it out. I had forgotten to delete the original mount table from
the registry before reinstalling cygwin. All my drives were still mounted in
textmode, and that's why cat and redirection failed.
- I don't know why mount and cygcheck -svr gives different reports regarding
mount mode.
- I have one question it would be nice if you answered. It's at the end of
the email.
And here's the rest of the email:
>
> (2) shows that you used to have text mounts. Your cygcheck.out shows
> binary mounts, so that's probably not the problem.
I forgot to mention that I reverted to my original version of cygwin (with
DOS-style newlines) when I discovered that using UNIX-style newlines didn't
fix the problem.
I did the following:
1) Renamed c:\cygwin to c:\cygwin_old
2) Reinstalled cygwin, specifying UNIX-style newlines when asked
3) Test if "cat file.bin | gzip -c > filecopy.gz" produced a valig gz-file.
It didn't
4) Deleted c:\cygwin and renamed c:\cygwin_old to c:\cygwin
I did not delete the registry keys or the local cygwin package directory. I
don't know is this matters or not.
I didn't know about text vs binary mounts until you mentioned it, and did
some reading up. One weird thing I came accross is that if I run mount, the
information seems to conflict with the information from cygcheck -svr.
$ mount
C:\cygwin\bin on /usr/bin type system (textmode)
C:\cygwin\lib on /usr/lib type system (textmode)
C:\cygwin on / type system (textmode)
c: on /cygdrive/c type user (textmode,noumount)
s: on /cygdrive/s type user (textmode,noumount)
The relevant lines from cygcheck -svr:
a: fd N/A N/A
c: hd NTFS 57231Mb 47% CP CS UN PA FC
d: cd N/A N/A
o: net N/A N/A
s: net NTFS 76308Mb 76% CP CS UN PA FC
C:\cygwin / system binmode
C:\cygwin/bin /usr/bin system binmode
C:\cygwin/lib /usr/lib system binmode
. /cygdrive system binmode,cygdrive
It looks to me as if mount claims all mounts are text mounts (which would
explain my problems, I guess). Whereas cygcheck -svr claims all my mounts
are binmode.
I'm beginning to wonder if I did something wrong when reinstalling cygwin
and specifying binary mode. I'm giving it another try now.
1) Renamed c:\cygwin to c:\cygwin_old
2) Renamed the HKCU\Software\Cygnus Solutions registry key
3) Renamed the local cygwin package dir.
4) Reinstalled cygwin, specifying UNIX-style newlines when asked
5) Test if "cat file.bin | gzip -c > filecopy.gz" produced a valig gz-file.
It didn't.
Running mount gives the same result as before (shows textmode on all
mounts).
I tried installing cygwin (downloaded setup.exe from www.cygwin.com) from
scratch on another computer in my office. That computer also runs WindowsXP.
$HOME wasn't defined here, but it was on my primary computer. Don't know if
that mattered.
On that computer, mount shows all mountpoints as being of type binmode, and
"cat file.bin | gzip -c > out.bin" works as it should.
I have no Idea why my primary computer insists on mounting everything in
textmode :-(.
I did try to remove my .bashrc-file on my primary computer. It didn't help -
and I couldn't find anything in there related to mounting.
I wonder where the mount table is stored. Maybe it for some reason survived
a reinstall of cygwin...
Please read on for some more discoveries.
>
> Please try the following: "sed '' binaryfile.bin > acopy.bin" and compare
> the files. Also "echo | sed '' > test.out; od -c test.out" and "perl -e
> 'print q{ }x2560' | gzip -c > test.gz; od -c test.gz".
thammer@blackbox /cygdrive/c/temp/temp
$ echo | sed '' >test.out
thammer@blackbox /cygdrive/c/temp/temp
$ od -c test.out
0000000 \r \n
0000002
thammer@blackbox /cygdrive/c/temp/temp
$ perl -e 'print q{ }x2560' | gzip -c > test.gz
thammer@blackbox /cygdrive/c/temp/temp
$ od -c test.gz
0000000 037 213 \b \0 = . 271 ? \0 003 355 301 201 \0 \0 \0
0000020 \0 303 225 371 S 036 344 U 001 \0 360 d 6 271 357
0000040 252 \0 \r \n \0 \0
0000046
Back to the mounting thread of thought.
I tried to mount a directory as binary:
$ mount -b c:\\temp\\temp\\t /mytest
mount: warning - /mytest does not exist.
$ cd /mytest
thammer@blackbox /mytest
$ echo | sed '' >test.out; od -c test.out
0000000 \n
0000001
Hey, I'm getting somewhere :-).
thammer@blackbox /mytest
$ ls -l
total 109
-rwx------ 1 thammer mkgroup 110755 Nov 17 21:51 bin.jpg
thammer@blackbox /mytest
$ cat bin.jpg | gzip -c > another.jpg.gz
thammer@blackbox /mytest
$ gunzip another.jpg.gz
thammer@blackbox /mytest
$ ls -l
total 218
-rw-r--r-- 1 thammer mkgroup 110755 Nov 17 22:08 another.jpg
-rwx------ 1 thammer mkgroup 110755 Nov 17 21:51 bin.jpg
thammer@blackbox /mytest
$ comp another.jpg bin.jpg
Comparing another.jpg and bin.jpg...
Files compare OK
I think there's something fishy about the mount table and where it's
located. I think it is for some reason stored _outside_ the c:\cygwin
directory. Which means it won't get updated when I do a reinstall of cygwin.
To verify this, I renamed c:\cygwin to c:\cygwin_new, and c:\cygwin_old to
c:\cygwin, and opened a bash shell.
thammer@blackbox /
$ mount
c:\temp\temp\t on /mytest type system (binmode)
C:\cygwin\bin on /usr/bin type system (textmode)
C:\cygwin\lib on /usr/lib type system (textmode)
c:\cygwin on / type system (textmode)
c: on /cygdrive/c type user (textmode,noumount)
s: on /cygdrive/s type user (textmode,noumount)
Hey! The /mytest mount is still there, as I suspected.
Where could that mount table be....
RTFM :).
When I reinstalled cygwin, I forgot to delete the "HKLM\Software\Cygnus
Solutions" registry subtree, I just deleted the "HKCU\Software\Cygnus
Solutions" subtree.
Oh well.
...
I have one final question I would be very happy if you could answer:
The problem I originally reported to you can be solved by myself by making
sure that I specifically mount the directory I'm working in in binmode. I
consider this an acceptable solution, but I don't feel good about it. I'm
going to have to put this in makefiles that will be distributed to our
customers, some of which might have text mounts, and having mount
instructions there seems plain wrong.
The question is this: Is there any way that I _from_the_commandline_ can
force all programs and the shell (for redirection) to use binary mode even
if the file is on a drive that is mounted in textmode? I'd like to do
something like this:
CYGWIN=somemagicstring bash -c cat file.bin | gzip -c > file2.bin.gz
/* Actually it would be more like this, with the gzip command
deep within the Makefile :
CYGWIN=somemagicstring bash -c make dist
*/
I tried s/somemagicstring/binmode/, and s/somemagicstring/tty/, but neither
did me any good.
If you have any suggestions as to if it's possible to avoid depending on a
binary mount, I'd be happy to hear it.
Thanks for the help so far :).
.Thomas
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2003-12-10 23:00 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-11-14 9:37 Bug in gzip's stdout handling Thomas Hammer
2003-11-14 15:28 ` Igor Pechtchanski
2003-11-14 15:52 ` Thomas Hammer
2003-11-14 16:22 ` Igor Pechtchanski
2003-11-18 23:03 ` Apache with mod_perl trouble Dmitry A. Pashko
2003-11-19 10:27 ` Patrick Eisenacher
2003-11-19 11:06 ` Dmitry A. Pashko
2003-12-10 23:31 ` dominix
2003-11-17 22:19 Bug in gzip's stdout handling Thomas Hammer
2003-11-18 18:51 ` Igor Pechtchanski
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).