- Original Message -
From: "Christopher Faylor"
To:
Sent: Wednesday, July 15, 2009 1:03 AM
Subject: Re: perl threads on 2008 R2 64bit = crash ( was: perl 5.10 threads on
1.5.25 = instant crash )
On Wed, Jul 15, 2009 at 12:36:56AM +0100, Steven Hartland wrote:
This may or may not
On Wed, Jul 15, 2009 at 12:36:56AM +0100, Steven Hartland wrote:
>This may or may not help:
>
>According to VC++ debugger it always dies with:
>Unhandled exception at 0x610d089d in perl.exe: 0xC005: Access violation
>reading location 0x0004.
No, sorry, it really doesn't help. The VC++ de
After normal startup of bash, the following command hangs after printing
the header row:
$ typeperf '\Processor(_Total)\% Processor Time' -si 1 -sc 2
--
Solution: insert 'chcp 1252' in cygwin.bat before calling bash.exe:
-- cygwin.bat begin --
@echo off
chcp 1252
chdir /d E:\cygwin\bin
bash --lo
This may or may not help:
According to VC++ debugger it always dies with:
Unhandled exception at 0x610d089d in perl.exe: 0xC005: Access violation
reading location 0x0004.
According to gdb 0x610d089d = thread.cc:113
So running it through gdb it hits this break point ~ 280 times before i
$ ls //home
ls: reading directory //home: No such file or directory
$ # makes sense; I don't have a remote machine named home
$ cd //home
$ # huh? no error reported?
$ /bin/pwd # avoid shortcuts in bash builtin; /bin/pwd uses getcwd
//home
$ # huh? getcwd is happy with it?
$ ls
ls: reading director
- Original Message -
From: "Christopher Faylor"
No joy here with 1.7 either, just crashes out instantly.
Running Windows Server 2008 R2 Standard 64bit build 7100 on dual E5520
with 18GB RAM showing 16 cores if that may be of interest.
gdb is not much help, so not sure what to try
Perhaps this went unnoticed. Reposting it. I am still having
problems building cygwin dll. Has anyone seen this error?
Jacob Jacobson wrote:
> >
> > Getting close here. Apparently gets to the linking phase. Please help
> > with error below.
> >
> >
> > [build$:618] (../src/configure --prefix=/c/h
On Tue, Jul 14, 2009 at 09:36:24PM +0100, Steven Hartland wrote:
>- Original Message -
>From: "Corinna Vinschen"
... and the script works fine on Windows 7 Build 7201 running under
Cygwin 1.7.
>
>No joy here with 1.7 either, just crashes out instantly.
>
>Running Windows Server
Never mind, this turned out to be fine I didn't remember
to THEN use "-S" since I thought installing would start it.
Probably ok now...
From: marchy...@hotmail.com
To: cygwin@cygwin.com
Subject: getting informative diagnostics from cygrunsrv
Dat
- Original Message -
From: "Corinna Vinschen"
... and the script works fine on Windows 7 Build 7201 running under
Cygwin 1.7.
No joy here with 1.7 either, just crashes out instantly.
Running Windows Server 2008 R2 Standard 64bit build 7100 on dual E5520
with 18GB RAM showing 16 cores
I've had generally good luck with cygrunsrv and have used it
on 3 or 4 machines that are running right now with a variety
of target apps. However, I have wasted essentially the whole
day trying to get antying to run with it. I can start the process
on bk with "&" and it runs fine it opens a ser
On Jul 14 20:38, Steven Hartland wrote:
> - Original Message - From: "Corinna Vinschen"
>
>> On Jul 14 14:55, Christopher Faylor wrote:
>>> On Tue, Jul 14, 2009 at 07:18:44PM +0100, Steven Hartland wrote:
>>> >On Tue, 14 Jul 2009 19:16:46 +0100, Dave Korn wrote:
>>> >>> sub dothread { pri
On 14/07/2009 11:47, Dave Korn wrote:
ffmpeg is one thing that's likely to suffer from the COMMON alignment
problem very badly, to the extent that I used it as a testcase when I
developed the support for the new feature, and I have a nicely working version
on my PC:
Without support for ali
- Original Message -
From: "Corinna Vinschen"
On Jul 14 14:55, Christopher Faylor wrote:
On Tue, Jul 14, 2009 at 07:18:44PM +0100, Steven Hartland wrote:
>On Tue, 14 Jul 2009 19:16:46 +0100, Dave Korn wrote:
>>> sub dothread { print STDERR "I'm a thread!\n" }
>>> [/test]
>>
>> WFM wit
On Jul 14 14:55, Christopher Faylor wrote:
> On Tue, Jul 14, 2009 at 07:18:44PM +0100, Steven Hartland wrote:
> >On Tue, 14 Jul 2009 19:16:46 +0100, Dave Korn wrote:
> >>> sub dothread { print STDERR "I'm a thread!\n" }
> >>> [/test]
> >>
> >> WFM with perl 5.10.0 on both 1.5 and 1.7.
> >
> >Than
On Jul 14 14:08, Christopher Faylor wrote:
> On Tue, Jul 14, 2009 at 02:04:45PM -0400, Andrew Schulman wrote:
> >Yeah, good point. I agree, we should take that part out, if there are no
> >objections.
>
> Good point, I agree. No need for expiration. I'll bet Corinna agrees too.
Yep.
Corinna
On Tue, Jul 14, 2009 at 07:18:44PM +0100, Steven Hartland wrote:
>On Tue, 14 Jul 2009 19:16:46 +0100, Dave Korn wrote:
>>> sub dothread { print STDERR "I'm a thread!\n" }
>>> [/test]
>>
>> WFM with perl 5.10.0 on both 1.5 and 1.7.
>
>Thanks Dave, maybe a Windows Server 2008 R2 64bit issue?
FYI,
- Original Message -
From: "Dave Korn"
sub dothread { print STDERR "I'm a thread!\n" }
[/test]
WFM with perl 5.10.0 on both 1.5 and 1.7.
Thanks Dave, maybe a Windows Server 2008 R2 64bit issue?
Regards
Steve
--
Problem reports: http://cygwin.com/problems.html
FAQ:
Wolfgang Goetz wrote on Thursday, July 09, 2009 6:03 AM:
> perl-Tk is broken in 1.5 and 1.7
>
> Check by running the "Perl/Tk Widget Demonstrations":
>
> $ widget
> Use of uninitialized value $id in hash element at
> /usr/lib/perl5/vendor_perl/5.10/i686-cygwin/Tk/After.pm line 39. ...
> Use of un
On Tue, Jul 14, 2009 at 02:04:45PM -0400, Andrew Schulman wrote:
>Yeah, good point. I agree, we should take that part out, if there are no
>objections.
Good point, I agree. No need for expiration. I'll bet Corinna agrees too.
cgf
--
Problem reports: http://cygwin.com/problems.html
FAQ:
> > All back-ordered gold stars should also now have been awarded.
>
> You might look at old ITA messages, too. I'm sorta owed some for
> adopting orphaned packages. I don't know that I really deserve them,
> since I don't release new versions very often, but maybe others who
> actually do pu
Steven Hartland wrote:
> [test]
> #!/bin/perl -w
>
> use warnings;
> use strict;
> use threads;
>
> print STDERR "Testing threads...\n";
> my $thrd = threads->create( \&dothread );
> $thrd->join();
> print STDERR "Testing done\n";
>
> sub dothread { print STDERR "I'm a thread!\n" }
> [/test]
Andrew Schulman wrote:
All back-ordered gold stars should also now have been awarded.
You might look at old ITA messages, too. I'm sorta owed some for
adopting orphaned packages. I don't know that I really deserve them,
since I don't release new versions very often, but maybe others who
a
Also happens on 5.8.8 :(
Summary of my perl5 (revision 5 version 8 subversion 8) configuration:
Platform:
osname=cygwin, osvers=1.5.24(0.15642), archname=cygwin-thread-multi-64int
uname='cygwin_nt-5.1 reini 1.5.24(0.15642) 2007-01-31 10:57 i686 cygwin '
config_args='-de -Dmksymlinks -Dus
Been looking around but cant find any mention of it so asking here:
Is there a known issue with the latest 1.5.25 + perl 5.10 threads,
as doing anything with threads here causes an instant crash.
[test]
#!/bin/perl -w
use warnings;
use strict;
use threads;
print STDERR "Testing threads...\n";
m
Yaakov (Cygwin/X) wrote:
> Dave,
Hi Yaakov,
> I have been having some difficulties building the latest ffmpeg with
> gcc-4.3.2-2; the build would complete but the resulting binaries
> wouldn't launch due to the dreaded, ever-so-helpful C005
> initialization error. Building with gcc-3.4 wor
Dave,
I have been having some difficulties building the latest ffmpeg with
gcc-4.3.2-2; the build would complete but the resulting binaries
wouldn't launch due to the dreaded, ever-so-helpful C005
initialization error. Building with gcc-3.4 worked just fine, as it has
for some time on 1.
On Jul 14 11:47, Christopher Faylor wrote:
> On Tue, Jul 14, 2009 at 05:36:43PM +0200, Corinna Vinschen wrote:
> >On Jul 14 15:30, Eric Blake wrote:
> >> Karl M hotmail.com> writes:
> >>
> >> > I just noticed while looking around after updating dash that "ls
> >> > /bin/*sh"
> >> does not find
http://cygwin.com/acronyms/#PPIOSPE
Karl M wrote on Tuesday, July 14, 2009 10:37 AM:
>> Subject: RE: ls and wildcards
>> Date: Tue, 14 Jul 2009 10:26:19 -0500
>> From: bryan.thrall
>>
>> Karl M wrote on Tuesday, July 14, 2009 10:17 AM:
>>
>>> Hi All...
>>>
>>> I just noticed while looking arou
On Tue, Jul 14, 2009 at 05:36:43PM +0200, Corinna Vinschen wrote:
>On Jul 14 15:30, Eric Blake wrote:
>> Karl M hotmail.com> writes:
>>
>> > I just noticed while looking around after updating dash that "ls /bin/*sh"
>> does not find bash and dash, but
>> > it does on my Fedora core 6 machine at
On Tue, Jul 14, 2009 at 09:51:02AM +0200, Corinna Vinschen wrote:
>On Jul 14 00:20, Christopher Faylor wrote:
>> As a test for our brand-new gold star maintainer, I'd like to suggest
>> that he give himself two gold stars. One as a test to see if this thing
>> is on and another for volunteering.
>
On Jul 14 15:30, Eric Blake wrote:
> Karl M hotmail.com> writes:
>
> > I just noticed while looking around after updating dash that "ls /bin/*sh"
> does not find bash and dash, but
> > it does on my Fedora core 6 machine at work. I see the issue in both 1.5
> > and
> 1.7, attached is an exampl
Subject: [1.7] Updated:
{subversion,subversion-apache2,subversion-devel,subversion-perl,subversion-python,subversion-ruby}-1.6.3-2
A new version of subversion is now available for download. This
version is built for Cygwin 1.7.
CYGWIN NEWS:
This release enables the windows-cryptoapi
CYGWIN NEWS:
This release enables the windows-cryptoapi password store, so
encrypted passwords can be stored.
NEWS:
=
This is a new upstream release. See CHANGES (URL below) for more
information.
IMPORTANT: This release will silently upgrade your Subversion
working copies to the
On Jul 14 10:26, Thrall, Bryan wrote:
> Karl M wrote on Tuesday, July 14, 2009 10:17 AM:
>
> > Hi All...
> >
> > I just noticed while looking around after updating dash that "ls
> /bin/*sh"
> > does not find bash and dash, but it does on my Fedora core 6 machine
> at work.
> > I see the issue in
Karl M hotmail.com> writes:
> I just noticed while looking around after updating dash that "ls /bin/*sh"
does not find bash and dash, but
> it does on my Fedora core 6 machine at work. I see the issue in both 1.5 and
1.7, attached is an example in
> cygwin 1.7.
[http://cygwin.com/acronyms/#PCY
Karl M wrote on Tuesday, July 14, 2009 10:17 AM:
> Hi All...
>
> I just noticed while looking around after updating dash that "ls
/bin/*sh"
> does not find bash and dash, but it does on my Fedora core 6 machine
at work.
> I see the issue in both 1.5 and 1.7, attached is an example in cygwin
1.7.
Hi All...
I just noticed while looking around after updating dash that "ls /bin/*sh" does
not find bash and dash, but it does on my Fedora core 6 machine at work. I see
the issue in both 1.5 and 1.7, attached is an example in cygwin 1.7.
Thanks,
...Karl
_
> On Jul 14 00:20, Christopher Faylor wrote:
> > As a test for our brand-new gold star maintainer, I'd like to suggest
> > that he give himself two gold stars. One as a test to see if this thing
> > is on and another for volunteering.
Thanks, one is sufficient.
> > I'd also like to give a five a
Wohooo!
On Jul 14 06:29, Eric Blake wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> The package dash has been upgraded to 0.5.5.1-2 for those using cygwin
> 1.7, simultaneously replacing dash-0.5.5.1-1 and ash-20040127-4. The ash
> package is now obsolete; ash.exe is provided by the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The package dash has been upgraded to 0.5.5.1-2 for those using cygwin
1.7, simultaneously replacing dash-0.5.5.1-1 and ash-20040127-4. The ash
package is now obsolete; ash.exe is provided by the dash package.
NEWS:
=
This is a minor patch releas
On Jul 14 00:20, Christopher Faylor wrote:
> As a test for our brand-new gold star maintainer, I'd like to suggest
> that he give himself two gold stars. One as a test to see if this thing
> is on and another for volunteering.
>
> I'd also like to give a five apiece to Jon Turney and the intrepid
42 matches
Mail list logo
