Re: mmap bug on Windows 9x

Anton Ertl wrote: > > On Windows 9x/ME different calls to mmap sometimes produce the same > address (without that memory being unmapped in the meantime, at least > not by application code). You find a condensed test program below. On Windows ME with cygwin1.dll 1.5.10 it outputs: try mmap($0, $

Re: gcc 3.3.1-3 runtime error: static data storage size

Pietro schrieb: > Gerrit, > I think you just did: > the program should print "ok" upon executing and it didn't. if you debug, > say, with insight, aa.exe will bail before reaching the printf statement, > generating a segmentation violation signal. > let me know. thanks for looking into it. > P

[ANNOUNCEMENT] Updated: distcc-2.16-1

The distcc-2.16-1 package has been updated in the Cygwin distribution. Changes === 1) Resync with upstream release. -- Harold Hunt *** To update your installation, click on the "Install Cygwin now" link on the http://cygwin.com

[ANNOUNCEMENT] New package: cppunit-1.9.14-1

The package 'cppunit' is now available with the Cygwin distribution. Description === CppUnit is a C++ unit testing framework. It started its life as a port of JUnit to C++ by Michael Feathers. -- Harold Hunt *** To update

Re: ssmtp man page (Was: Re: sending email from Cygwin)

On Jul 16 12:01, [EMAIL PROTECTED] wrote: > On 15 Jul, Corinna Vinschen wrote: > > > Incidentally is it appropriate to include Cygwin-port-specific > > > information in a man page? > > > > Well, from a user perspective it might be cool, but IMHO the original > > man page shouldn't be cha

Re: [BUG] mprotect() on Windows NT 5+

On Jul 15 23:10, Xavier Joubert wrote: > Selon Corinna Vinschen: > > I've checked in a fix, so that mprotect tests for > > the original protection mode of the first page in the area, and uses > > READWRITE or WRITECOPY, whichever matches the original protection. > > Whow! That's amazing! I didn'

Re: UNC Pathname Handling within Applications

Hi, please send me every mail only once. Thanks. * Larry Hall wrote (2004-07-16 04:21): >At 07:30 PM 7/15/2004, you wrote: >>* Shankar Unni wrote (2004-07-16 00:52): >>>Thorsten Haude wrote: - Is there any standard way to approach this problem? Has it come up before in other applications?

Svwgv Imm.E`diate Acc_ess To Va~.l1um..X.A`_nax..Bu-.spar.. 0ve_-rnite To Your D_`00r

canon beheersers bedrinkt Can.`a'`da dr,`ugs & fast shi_.ppi~ng K ` R http://tq.q.cnhptz.com/29/ A friend gave me the number of a lady across town who worked at home doing alterations. I was desperate and willing to try anything, so I decided to give her a call. How many of us get snowballed b

Whack-a-Mole: Purging Cygnus from Registry

I'm using an rsyncd package that uses its own version of cygwin, and does not play nice when installed on a machine with Cygwin. It is part of BackupPC, which is turning out to be an incredible piece of backup software. So, I've got one Windows XP machine that is seemingly possessed -- I have

Re: Whack-a-Mole: Purging Cygnus from Registry

On Jul 16 05:46, Todd Curry wrote: > I'm using an rsyncd package that uses its own version of cygwin, and > does not play nice when installed on a machine with Cygwin. It is part > of BackupPC, which is turning out to be an incredible piece of backup > software. Please ask for support in the b

Re: UNC Pathname Handling within Applications

On Jul 16 14:06, Thorsten Haude wrote: > I think some people might see the surprising path, *think* the > software is broken and stop using it. Another problem ist the toolkit. > > I agree that the leading extra slash should be supported, but it might > not be as easy as it sounds. Thorsten, eve

Re: maintaner of gcc

> * Gerrit P. Haase <[EMAIL PROTECTED]> [2004-07-16 00:58:04 +0200]: > > Sam schrieb: > >>> * Gerrit P. Haase <[EMAIL PROTECTED]> [2004-07-15 15:24:45 +0200]: >>> >>> What is wrong with 3.3.x release series? Are there any serious bugs? >>> Are there issues (for you)? Why do you need 3.4.x? > >> g

Re: UNC Pathname Handling within Applications

Hi, * Corinna Vinschen wrote (2004-07-16 15:01): >even if I repeat other postings, please note that double slashes are >absolutely fine according to the standards. Leading double slashes may >have a special meaning on POSIX implementations and the *well* *known* >Windows specific meaning is an UN

Re: UNC Pathname Handling within Applications

On Jul 16 15:10, Thorsten Haude wrote: > Hi, > > * Corinna Vinschen wrote (2004-07-16 15:01): > >even if I repeat other postings, please note that double slashes are > >absolutely fine according to the standards. Leading double slashes may > >have a special meaning on POSIX implementations and th

Re: coredump on kill

On Fri, 16 Jul 2004, Carlo Florendo y Flora wrote: > Hello, > > Upon invoking the following command, I get a coredump: > > /usr/bin/kill --list > > By the way, "kill -l" (bash built-in) works. > > Attached is cygcheck's output and the dump itself. > > Does anyone know of a workaround? > I do ;-).

Re: Whack-a-Mole: Purging Cygnus from Registry

Todd Curry wrote: > I'm using an rsyncd package that uses its own version of cygwin, and > does not play nice when installed on a machine with Cygwin. It is part > of BackupPC, which is turning out to be an incredible piece of backup > software. > > So, I've got one Windows XP machine that is seem

Re: COM Port Question

On Thu, 15 Jul 2004, Tester Field wrote: > Hi, >   > I have installed Cygwin on a Dell PC with windows > 2000, and I am trying to sent AT command to an > external modem attached on COM1. >   > My questions are: >   > 1) What do I need to do for cygwin to recognize COM1? Nothing :-). > 2) Is ther

RE: Whack-a-Mole: Purging Cygnus from Registry

> -Original Message- > From: cygwin-owner On Behalf Of Todd Curry > Sent: 16 July 2004 13:47 > I'm using an rsyncd package that uses its own version of cygwin, and > does not play nice when installed on a machine with Cygwin. > It is part > of BackupPC, which is turning out to be an in

RE: coredump on kill

> -Original Message- > From: cygwin-owner On Behalf Of Brian Ford > Sent: 16 July 2004 14:43 > On Fri, 16 Jul 2004, Carlo Florendo y Flora wrote: > > > Hello, > > > > Upon invoking the following command, I get a coredump: > > > > /usr/bin/kill --list > > > > By the way, "kill -l" (bash bu

Re: COM Port Question

Thank you for your response. I was wondering if there any way of testing whether the device attached to COM1, is receiving any data. I have done ls-al /dev/com1 and I see the file. However, how can I verify that the device attached is receiving any data. Any idea? Any utilities provided to monitor

Re: gcc 3.3.1-3 runtime error: static data storage size

On Fri, Jul 16, 2004 at 10:36:23AM +0200, Gerrit P. Haase wrote: >Pietro schrieb: > >> Gerrit, > >> I think you just did: > >> the program should print "ok" upon executing and it didn't. if you debug, >> say, with insight, aa.exe will bail before reaching the printf statement, >> generating a segme

[OT] RE: COM Port Question

> -Original Message- > From: cygwin-owner On Behalf Of Tester Field > Sent: 16 July 2004 14:58 > Thank you for your response. I was wondering if there > any way of testing whether the device attached to > COM1, is receiving any data. I have done ls-al > /dev/com1 and I see the file. Howeve

Re: Whack-a-Mole: Purging Cygnus from Registry

On Fri, Jul 16, 2004 at 05:46:59AM -0700, Todd Curry wrote: >I'm using an rsyncd package that uses its own version of cygwin, and >does not play nice when installed on a machine with Cygwin. It is part >of BackupPC, which is turning out to be an incredible piece of backup >software. **cgf wake

Re: coredump on kill

On Fri, Jul 16, 2004 at 02:37:23PM -0800, Carlo Florendo y Flora wrote: >Hello, > >Upon invoking the following command, I get a coredump: > >/usr/bin/kill --list > >By the way, "kill -l" (bash built-in) works. > >Attached is cygcheck's output and the dump itself. > >Does anyone know of a workaround

Re: Whack-a-Mole: Purging Cygnus from Registry

On Jul 16 10:21, Christopher Faylor wrote: > On Fri, Jul 16, 2004 at 05:46:59AM -0700, Todd Curry wrote: > >I'm using an rsyncd package that uses its own version of cygwin, and > >does not play nice when installed on a machine with Cygwin. It is part > >of BackupPC, which is turning out to be an

Re: mmap bug on Windows 9x

On Jul 16 09:12, Anton Ertl wrote: > Anton Ertl wrote: > > > > On Windows 9x/ME different calls to mmap sometimes produce the same > > address (without that memory being unmapped in the meantime, at least > > not by application code). > > You find a condensed test program below. > > On Windows M

Bad protocol 'tcp' with perl/lwp module connections

Running a cgi script like the following from the command line works pretty fine. Running the same script from within the browser result in an error message like: http://192.168.0.5/cgi-bin/lwp.cgi > 500 Can't connect to search.cpan.org:80 (Bad protocol 'tcp') The sample script: -

bad interpreter

I do not know what I have setup incorrecty: Looking over the list I have learned and made sure both ash and bash are both in the /bin/ directory and seem to have been installed correctly. If I run a script with the initial heading of: #! /bin/bash I get this error: bash-2.05b$ ./Test bash: ./Te

Re: gcc 3.3.1-3 runtime error: static data storage size

Christopher wrote: > On Fri, Jul 16, 2004 at 10:36:23AM +0200, Gerrit P. Haase wrote: >>Pietro schrieb: >> >>> Gerrit, >> >>> I think you just did: >> >>> the program should print "ok" upon executing and it didn't. if you debug, >>> say, with insight, aa.exe will bail before reaching the printf st

cygrunsrv -S sshd - Access is denied.

Hello, I'm having difficulty with sshd on an Windows XP system. It worked fine for months and then failed after upgrading to OpenSSH_3.8.1p1. The command cygrunsrv fails with the error cygrunsrv: Error starting a service: StartSevervice: Win32 error 5: Access is denied I did a number of t

RE: gcc 3.3.1-3 runtime error: static data storage size

> -Original Message- > From: cygwin-owner On Behalf Of Christopher Faylor > Sent: 16 July 2004 15:16 > >Yes, I see. Yhe problem is the default stack size on cygwin > (2 MB), you > >can increase it. > > > >$ gcc -o aa -Wl,--stack,8388608 aa.c > > > >$ ./aa > >ok > > > >$ cat aa.c > >#defi

Re: cygrunsrv -S sshd - Access is denied.

Hello Dick, On Fri, Jul 16, 2004 at 10:21:27AM -0500, Dick Repasky wrote: > -rwxr-x---1 rrepasky Users 277504 Apr 19 15:19 /usr/sbin/sshd* Seems that your sshd is not executable by SYSTEM. You might want to check also the DLLs used by sshd (cygwin1, cygz, cygcrypto-0.9.7 on my system).

Re: Whack-a-Mole: Purging Cygnus from Registry

Corinna, This is purely a cygwin question: this particular XP machine *had* cygwin installed, and I must remove it before installing any backuppc-related-repackagings-of-cygwinue software gets installed. Thanks, Todd (still whacking moles) -Original Message- From: Corinna Vinschen <[EMAI

Re: UNC Pathname Handling within Applications

Thorsten, The best way to insure that you get only one copy of any response from the list is to set your reply-to to point to the list. Depending on the software you use, you may find that you can easily filter out duplicates too. I don't second-guess the implied intent of posters to whom I res

Re: Whack-a-Mole: Purging Cygnus from Registry

At 11:45 AM 7/16/2004, you wrote: >Corinna, > >This is purely a cygwin question: this particular XP machine *had* cygwin installed, >and I must remove it before installing any backuppc-related-repackagings-of-cygwinue >software gets installed. OK, so find all the cygwin1.dlls left on your syste

Re: Whack-a-Mole: Purging Cygnus from Registry

Larry, Max, Dave, Thanks! There were 26 instances of cygwin1.dll on the machine. When removed, rebooted, and regedited, the registry is now 100% free of moles! Thanks again, Todd -Original Message- From: Larry Hall <[EMAIL PROTECTED]> To: Todd Curry <[EMAIL PROTECTED]>; [EMAIL PROTECTE

RE: Whack-a-Mole: Purging Cygnus from Registry

> -Original Message- > From: cygwin-owner On Behalf Of Todd Curry > Sent: 16 July 2004 18:13 > To: [EMAIL PROTECTED] > Subject: Re: Whack-a-Mole: Purging Cygnus from Registry > > > Larry, Max, Dave, > > Thanks! There were 26 instances of cygwin1.dll on the machine. A new cygwin-li

Re: UNC Pathname Handling within Applications

Hi, I sent the sollowing message to Larry via private mail: - - - Schnipp - - - Hi Larry, please don't use tofu mails. http://www.vranx.de/mail/tofu.html * Larry Hall wrote (2004-07-16 17:41): >The best way to insure that you get only one copy of any response from the >list is to set your reply

Re: UNC Pathname Handling within Applications

Thorsten Haude wrote: The path is also displayed at various places. The user might be surprised to see surplus slashes. [Starting to drift OT, sorry..] Who's generating the surplus slashes? Is this because of trailing "/" in paths, and you're internally compositing names somehow? I thought the on

Re: cygrunsrv -S sshd - Access is denied.

Baurjan, Thanks! Changing ownership and permissions didn't do it. I had to set an appropriate facl. Dick On Fri, 16 Jul 2004, Baurjan Ismagulov wrote: > Hello Dick, > > On Fri, Jul 16, 2004 at 10:21:27AM -0500, Dick Repasky wrote: > > -rwxr-x---1 rrepasky Users 277504 Apr 19 15:19

Re: ssmtp man page (Was: Re: sending email from Cygwin)

On Fri, 16 Jul 2004, Corinna Vinschen wrote: > On Jul 16 12:01, luke.kendallcisra.canon.com.au wrote: > > On 15 Jul, Corinna Vinschen wrote: > > > > Incidentally is it appropriate to include Cygwin-port-specific > > > > information in a man page? > > > > > > Well, from a user perspective it mig

Re: UNC Pathname Handling within Applications

At 02:13 PM 7/16/2004, you wrote: >Hi, > >I sent the sollowing message to Larry via private mail: Sorry. Everything I post to the list I want to be on the list. So only the list version got through. I guess you figured that out by now. If you would like to continue this or some other discussi

Re: bad interpreter

On Fri, 16 Jul 2004, David J Jones wrote: > I do not know what I have setup incorrecty: > Looking over the list I have learned and made sure both ash and bash are > both in the /bin/ directory and seem to have been installed correctly. > > If I run a script with the initial heading of: > > #! /bin

Re: Bad protocol 'tcp' with perl/lwp module connections

On Fri, 16 Jul 2004, Dirk Fokken, Cross Development wrote: > Running a cgi script like the following from the command line works > pretty fine. > > Running the same script from within the browser result in an error > message like: > > http://192.168.0.5/cgi-bin/lwp.cgi > > 500 Can't connect to sea

Re: UNC Pathname Handling within Applications

Hi, * Larry Hall wrote (2004-07-16 21:19): >At 02:13 PM 7/16/2004, you wrote: >>I sent the sollowing message to Larry via private mail: > >Sorry. Everything I post to the list I want to be on the list. I expected that to be a misconfiguration of some kind, now you say you do that on purpose. It'

Re: UNC Pathname Handling within Applications

Hi, * Shankar Unni wrote (2004-07-16 20:36): >Thorsten Haude wrote: > >>The path is also displayed at various places. The user might be >>surprised to see surplus slashes. > >[Starting to drift OT, sorry..] > >Who's generating the surplus slashes? Is this because of trailing "/" in >paths, and yo

mail command as a script

Based on the post of jerzy szczudłowski (thanks jerzy :), I made an enhanced version for a mail-mailx replacement. It is done as a bash script. I just want to post the script on the list for whoever needs such a feature, as I did. To the ssmtp package maintainer: How about considering to include

Re: UNC Pathname Handling within Applications

At 03:55 PM 7/16/2004, you wrote: >>>Actually, I wonder what possible reasons could exist to send every >>>mail twice, and even by default. I haven't checked, but I guess you >>>cannot subscribe this list or any other write-only, so in what >>>possible situation would the second mail enhance co

Re: UNC Pathname Handling within Applications

On Fri, 16 Jul 2004, Thorsten Haude wrote: > Please tell me how I activate the write-only subscription. See . Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,

Re: UNC Pathname Handling within Applications

Hi, * Larry Hall wrote (2004-07-16 22:29): >At 03:55 PM 7/16/2004, you wrote: Actually, I wonder what possible reasons could exist to send every mail twice, and even by default. I haven't checked, but I guess you cannot subscribe this list or any other write-only, so in what possib

Re: UNC Pathname Handling within Applications

On Fri, Jul 16, 2004 at 09:55:49PM +0200, Thorsten Haude wrote: >* Larry Hall wrote (2004-07-16 21:19): >Your email client *sets* Mail-Followup-To, so it must be pretty crappy >to ignore it on inbound mail. This field is added by the ezmlm software that is used to manage our mailing lists. >I've

Re: ssmtp man page (Was: Re: sending email from Cygwin)

On Fri, Jul 16, 2004 at 12:01:03PM +1000, luke.kendall wrote: > This is a usability issue. It's hard enough to teach people to type: > > man > > teaching them to type: > > more /usr/share/doc/Cygwin/ssmtp-0.x.y/README.ssmtp-0.x.y I'm partial to: cygcheck -l ssmtp|fgrep README

RE: Whack-a-Mole: Purging Cygnus from Registry

At Friday, July 16, 2004 11:45 AM, Todd Curry wrote: > Corinna, > > This is purely a cygwin question: this particular XP machine *had* > cygwin installed, and I must remove it before installing any > backuppc-related-repackagings-of-cygwinue software gets installed. > > Thanks, > > Todd > (still

Re: UNC Pathname Handling within Applications

Hi, * Christopher Faylor wrote (2004-07-16 23:19): >On Fri, Jul 16, 2004 at 09:55:49PM +0200, Thorsten Haude wrote: >>* Larry Hall wrote (2004-07-16 21:19): >>Your email client *sets* Mail-Followup-To, so it must be pretty crappy >>to ignore it on inbound mail. > >This field is added by the ezmlm

Re: Problem with echo in tcsh 6.13.00-2 in Cygwin 1.5.10 (fwd)

On Fri, 16 Jul 2004, David Mastronarde wrote: > On Mon, 12 Jul 2004, David Mastronarde wrote: > > > > > The latest version of tcsh has a problem with the built-in echo. > > When echo is used to write to a file from within a script, and then the > > script runs a program that attempts to open the

Re: ssmtp man page (Was: Re: sending email from cygwin)

On Fri, Jul 16, 2004 at 02:25:32PM -0700, Yitzchak Scott-Thoennes wrote: >On Fri, Jul 16, 2004 at 12:01:03PM +1000, luke.kendall wrote: >> This is a usability issue. It's hard enough to teach people to type: >> >> man >> >> teaching them to type: >> >> more /usr/share/doc/Cygwin/ssmt

Re: UNC Pathname Handling within Applications

On Fri, Jul 16, 2004 at 11:32:56PM +0200, Thorsten Haude wrote: >Hi, > >* Christopher Faylor wrote (2004-07-16 23:19): >>On Fri, Jul 16, 2004 at 09:55:49PM +0200, Thorsten Haude wrote: >>>* Larry Hall wrote (2004-07-16 21:19): >>>Your email client *sets* Mail-Followup-To, so it must be pretty crapp

Re: ssmtp man page (Was: Re: sending email from cygwin)

On Fri, 16 Jul 2004, Christopher Faylor wrote: > On Fri, Jul 16, 2004 at 02:25:32PM -0700, Yitzchak Scott-Thoennes wrote: > >On Fri, Jul 16, 2004 at 12:01:03PM +1000, luke.kendall wrote: > >> This is a usability issue. It's hard enough to teach people to type: > >> > >>man > >> > >> teaching

Re: ssmtp man page (Was: Re: sending email from cygwin)

On Fri, Jul 16, 2004 at 09:53:44PM -0400, Igor Pechtchanski wrote: >On Fri, 16 Jul 2004, Christopher Faylor wrote: > >> On Fri, Jul 16, 2004 at 02:25:32PM -0700, Yitzchak Scott-Thoennes wrote: >> >On Fri, Jul 16, 2004 at 12:01:03PM +1000, luke.kendall wrote: >> >> This is a usability issue. It's h

Re: UNC Pathname Handling within Applications

Hi, * Christopher Faylor wrote (2004-07-17 03:50): >I don't understand why it matters that the first message would be >deleted since you can't predict if the message would be directly to you >or to the cygwin list. However, please don't enlighten me since I can >live with not knowing. More impor