Re: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal

2010-06-17 Thread Christopher Faylor
On Fri, Jun 18, 2010 at 12:49:09AM -0500, Yaakov (Cygwin/X) wrote: >On Thu, 2010-06-17 at 18:31 -0400, Christopher Faylor wrote: >> Do you have a test case? I tried to make one but "it didn't fail for >> me". If you can generate a test case I'm sure I could fix the problem. > >The only place I se

Re: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal

2010-06-17 Thread Yaakov (Cygwin/X)
On Thu, 2010-06-17 at 18:31 -0400, Christopher Faylor wrote: > Do you have a test case? I tried to make one but "it didn't fail for > me". If you can generate a test case I'm sure I could fix the problem. The only place I see it consistently is when the java-gnome build calls gettext's tools (xg

Re: 1.7.5 ssh db2 SQL5005C Systemerror

2010-06-17 Thread carpl
Corinna Vinschen cygwin.com> writes: > > On Jun 15 14:34, carpl gmx.de wrote: > > > > Hi, > > > > i use cygwin 1.7.5 on XP and try to execute db2-commands on a win 2003 or win 2008 server with ssh. > > > > When i try to connect to a db2 database the following error occurs : > > SQL5005C Sy

Re: C++ app segfaults in libstdc++

2010-06-17 Thread Charles Wilson
On 6/17/2010 3:58 PM, Dave Korn wrote: > On 17/06/2010 16:23, Charles Wilson wrote: > >> As expected, this didn't work. But...the imports and exports are NOT >> what I expected, so I'm a little confused: > >> Err, what? (a) why is this DLL exporting modexc stuff, when it is marked >> dllimport in

Re: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal

2010-06-17 Thread Christopher Faylor
On Thu, Jun 17, 2010 at 04:33:42PM -0500, Yaakov (Cygwin/X) wrote: >On Fri, 2010-06-04 at 10:36 +0200, Corinna Vinschen wrote: >> This looks like an internal error in Cygwin which runs out of TLS >> filename buffers. For a start, could you please strace the perl >> process? This may help to figur

Re: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal

2010-06-17 Thread Yaakov (Cygwin/X)
On Fri, 2010-06-04 at 10:36 +0200, Corinna Vinschen wrote: > This looks like an internal error in Cygwin which runs out of TLS > filename buffers. For a start, could you please strace the perl > process? This may help to figure out the function in which the problem > occurs. I'll bring this to y

Re: C++ app segfaults in libstdc++

2010-06-17 Thread Dave Korn
On 17/06/2010 16:23, Charles Wilson wrote: > As expected, this didn't work. But...the imports and exports are NOT > what I expected, so I'm a little confused: > Err, what? (a) why is this DLL exporting modexc stuff, when it is marked > dllimport in this context? (b) why is this DLL exporting std:

[ANNOUNCEMENT] Updated: OpenSSH-5.5p1-2

2010-06-17 Thread Corinna Vinschen
I've just updated the Cygwin version of OpenSSH to 5.5p1-2. This version adds improved edit capabilities on the sftp command line by being built against the new libedit. Otherwise it's identical to the former 5.5p1-1 release. To update your installation, click on the "Install Cygwin now" link o

Re: C++ app segfaults in libstdc++

2010-06-17 Thread Charles Wilson
On Thu, 17 Jun 2010 10:05 -0400, "Charles Wilson" wrote: > On 6/17/2010 9:50 AM, Dave Korn wrote: > > To summarize the summary of the summary: C++ is complicated. > > No kidding. What if the datatypes used in the interface between the > module and main -- including ALL exception classes -- were

Re: Windows Server 2008 64-bit setup.exe/bash problem

2010-06-17 Thread Ernest Mueller
> Try turning on Vista compatibility for the setup.exe. And later for MinTTY or > any terminal, if you use it. Another good suggestion... In 2008 there's not a Vista compatibility option, but there are XP and Server 2003 options; I tried installing it with XP compatibility set on setup.exe but st

Re: R: [ANNOUNCEMENT] New: {libedit/libedit0/libedit-devel}-20090923-1

2010-06-17 Thread Corinna Vinschen
On Jun 17 13:38, Marco Atzeri wrote: > --- Gio 17/6/10, Corinna Vinschen ha scritto: > > > I just uploaded the new "libedit" > > package to cygwin.com. > > [...] > > Thanks > I appreciate as also ngspice can use it. > > For your info, it seems that upstream > just added UTF8 capability > > ht

Re: C++ app segfaults in libstdc++

2010-06-17 Thread Charles Wilson
On 6/17/2010 9:50 AM, Dave Korn wrote: > To summarize the summary of the summary: C++ is complicated. No kidding. What if the datatypes used in the interface between the module and main -- including ALL exception classes -- were defined in a second DLL, on which both module and main depend? Th

R: [ANNOUNCEMENT] New: {libedit/libedit0/libedit-devel}-20090923-1

2010-06-17 Thread Marco Atzeri
--- Gio 17/6/10, Corinna Vinschen ha scritto: > I just uploaded the new "libedit" > package to cygwin.com. > > This package is a requirement to get improved edit > capabilities in the > sftp tool from the OpenSSH package.  A new OpenSSH > package containing an > sftp tool linked against libedit

Re: C++ app segfaults in libstdc++

2010-06-17 Thread Dave Korn
On 17/06/2010 13:15, Dave Korn wrote: > On 17/06/2010 03:41, Charles Wilson wrote: > >> Any ideas? > > Yes, I have one: > >> catch (modexc e) { >> std::cerr << "caught: " << e.what () << '\n'; >> if (dlclose (handle)) >> { >> std::cerr << "dlclose failed: " << dlerror (

[ANNOUNCEMENT] New: {libedit/libedit0/libedit-devel}-20090923-1

2010-06-17 Thread Corinna Vinschen
I just uploaded the new "libedit" package to cygwin.com. This package is a requirement to get improved edit capabilities in the sftp tool from the OpenSSH package. A new OpenSSH package containing an sftp tool linked against libedit will follow shortly. "libedit" is an autotool- and libtoolized

Re: C++ app segfaults in libstdc++

2010-06-17 Thread Dave Korn
On 17/06/2010 03:41, Charles Wilson wrote: > Any ideas? Yes, I have one: > catch (modexc e) { > std::cerr << "caught: " << e.what () << '\n'; > if (dlclose (handle)) > { > std::cerr << "dlclose failed: " << dlerror () << '\n'; > return 1; > } > return

Re: Hello! I can't get to c:\Program Files using c:\Program/ Files\ any suggestions?

2010-06-17 Thread Thorsten Kampe
* wynfi...@gmail.com (Wed, 16 Jun 2010 18:38:40 +0900) > Thorsten, don't use Microsoft Windows style of pathnames! Use POSIX > compliant pathnames. Wynfield, I don't use "Microsoft Windows style of pathnames". I just pointed out that they work. Thorsten -- Problem reports: http://cygwin.