To resume my mail:
On Wed 2018-05-30 (12:57), Ulli Horlacher wrote:
>
> One of my Perl programs produces strange runtime errors on a Windows 7
> system (CYGWIN_NT-6.1 32bit) of my colleague:
>
> 0 [main] perl 4232 child_info_fork::abort: address space needed
>by 'Encode.dll' (0x37
On Wed 2018-06-06 (17:49), Marco Atzeri wrote:
> >> No, it's most likely (or should be, anyway) an XS library for the Encode
> >> module of Perl. The address it gets loaded to is awfully low, so it's
> >> either BLODA or you're using another library that's occupying the reabse
> >> space for this
On 6/6/2018 5:31 PM, Ulli Horlacher wrote:
On Mon 2018-06-04 (21:24), Achim Gratz wrote:
Ulli Horlacher writes:
No, it's most likely (or should be, anyway) an XS library for the Encode
module of Perl. The address it gets loaded to is awfully low, so it's
either BLODA or you're using another
On Mon 2018-06-04 (21:24), Achim Gratz wrote:
> Ulli Horlacher writes:
>
> > /client/bin is a directory which I have created.
> > It should not collide with anything.
>
> So what's in there, is in PATH etc. pp.
In /client/bin are my own programs, mostly Perl scripts and yes, it is in
$PATH.
>
Ulli Horlacher writes:
> /client/bin is a directory which I have created.
> It should not collide with anything.
So what's in there, is in PATH etc. pp.
> The problem is:
>
> [main] perl 4232 child_info_fork::abort: address space needed by 'Encode.dll'
> (0x37) is already occupied
>
> Encode
On Wed 2018-05-30 (21:56), Achim Gratz wrote:
> Ulli Horlacher writes:
>
> > Line 106 in /client/bin/fexsend is:
>
> That path looks suspiciously like something not properly packaged for
> Cygwin. If so, it may use DLL that are not rebased and collide with
> Cygwin's.
/client/bin is a directory
Ulli Horlacher writes:
> Line 106 in /client/bin/fexsend is:
That path looks suspiciously like something not properly packaged for
Cygwin. If so, it may use DLL that are not rebased and collide with
Cygwin's.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]
One of my Perl programs produces strange runtime errors on a Windows 7
system (CYGWIN_NT-6.1 32bit) of my colleague:
0 [main] perl 4232 child_info_fork::abort: address space needed
by 'Encode.dll' (0x37) is already occupied
Can't fork, trying again in 5 seconds at /client/bin/
Ken,
your suggestion to put the TeXLive bin dir as the first entry of
PATH enabled TeXLive/ConTex.
Great. I sincerely appreciate you assistance.
Now I will try to ferret out the problem and report on it when I find it.
Regards
On Wed, Aug 22, 2012 at 12:30 PM, Ken Brown wrote:
> On 8/22/20
Wynfield Henman writes:
> I reinstalled all cygwin zlib modules and the problem persisted. The
> only zlib I found was the cygwin installed one. Since it is POSIX
> compliant and TeXLive installs with it it shouldn't be a problem, I
> should think. But, there is one due to, pdftex I think.
The
On 8/22/2012 2:06 PM, Wynfield Henman wrote:
Ken,
thanks for replying and helping. Here is the information that you
asked about.
The example ConTeXt file, example.tex, is attached hereto.
PATH is in the cygcheck.out file.
No other zlib.h was found.
I can't reproduce the problem on my syst
I reinstalled all cygwin zlib modules and the problem persisted. The
only zlib I found was the cygwin installed one. Since it is POSIX
compliant and TeXLive installs with it it shouldn't be a problem, I
should think. But,
there is one due to, pdftex I think.
Regards
On Mon, Aug 20, 2012 at 11:
Wynfield Henman gmail.com> writes:
> This results in: "PANIC: unprotected error in call to Lua API
> (zlib library version does not match -
> header: 1.2.5, library: 1.2.7)"
Reinstall zlib and install zlib-devel. If that doesn't help, check where the
zlib.h header file i
On 8/20/2012 11:18 AM, Wynfield Henman wrote:
TeXLive Version: 2012 ("--all" updated to August 20th, 2012)
Downloaded from: REPOSITORY="http://mirror.ctan.org/systems/texlive/tlnet";
Yes, this is the wild verison. ConTeXt changes very rapidly and I
fancy following and testing those changes. Th
TeXLive Version: 2012 ("--all" updated to August 20th, 2012)
Downloaded from: REPOSITORY="http://mirror.ctan.org/systems/texlive/tlnet";
Yes, this is the wild verison. ConTeXt changes very rapidly and I
fancy following and testing those changes. Thanks to cygwin for
allowing me to do that.
The a
On Fri, Oct 14, 2011 at 11:49:31AM +0200, phi...@free.fr wrote:
> Hello,
>
> I have just installed cygwin on Windows 7 and I get the following runtime
> error once every so often:
> Runtime Error! Program c:\cygwin\bin\bash.exe R6016 - not enough space for
> thread data
Hello,
I have just installed cygwin on Windows 7 and I get the following runtime error
once every so often:
Runtime Error! Program c:\cygwin\bin\bash.exe R6016 - not enough space for
thread data
Furthermore, when I open a terminal and source my old .bashrc file, the
following message appear
On 01/04/2010 19:39, Brad Allen wrote:
> Nobody replied on this, so I've given up on cygwin.
Oops, sorry. This is a high traffic mailing list, sometimes things get
overlooked. Please believe that it wasn't malicious.
> The bash shell included with msysgit is turning out to be a nice
> replace
On 4/1/2010 2:39 PM, Brad Allen wrote:
Nobody replied on this, so I've given up on cygwin.
Persistence is a virtue. :-)
The bash shell included with msysgit is turning out to be a nice
replacement, and unlike cygwin, doesn't seem to have any problems with
Python's virtualenv.
You're welcome
Nobody replied on this, so I've given up on cygwin.
The bash shell included with msysgit is turning out to be a nice
replacement, and unlike cygwin, doesn't seem to have any problems with
Python's virtualenv.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://
due to a RunTime Error,
stating that "This application has requested the Runtime to terminate
it in an unusual way. Please contact the application's support team
for more information."
During my initial attempt, I had failed to properly select my
employer's proxy server setting
Manikanta Gadamsetty wrote on 11 March 2008 06:47:
> Hi,
>
>I have downloaded the Cygwin. when i am installing it i am getting a
> problem as
>
> Microsoft visual C++ Runtime Library
> Runtime Error!
> Program:C\Documents and Settings\GadamsM\Desktop\rhse
Hi,
I have downloaded the Cygwin. when i am installing it i am getting
a problem as
Microsoft visual C++ Runtime Library
Runtime Error!
Program:C\Documents and Settings\GadamsM\Desktop\rhsetup.exe
This application has requested the Runtime to terminate it
in an unusual way. Please
Igor Peshansky wrote:
On Wed, 25 Apr 2007, Dmitry Golovaty wrote:
Thanks, Igor.
PATH is usually processed left-to-right. As an alternative to what
Brian suggested, simply prepending C:\cygwin\bin to the PATH should
work.
C:\cygwin\bin has been in the PATH all the time; the pr
On Wed, 25 Apr 2007, Dmitry Golovaty wrote:
> Thanks, Igor.
>
> > PATH is usually processed left-to-right. As an alternative to what
> > Brian suggested, simply prepending C:\cygwin\bin to the PATH should
> > work.
>
> C:\cygwin\bin has been in the PATH all the time; the problem seems to
> have b
Thanks, Igor.
PATH is usually processed left-to-right. As an alternative to what Brian
suggested, simply prepending C:\cygwin\bin to the PATH should work.
C:\cygwin\bin has been in the PATH all the time; the problem seems to have
been that the PATH statement contained a MATLAB directory some
On Fri, 20 Apr 2007, Dmitry Golovaty wrote:
> Thanks - the culprit is the MATLAB entry
>
> /cygdrive/c/Program Files/MATLAB/R2007a/bin/win32
>
> in the path; removing it fixes the problem ... is there way to pluck
> it out automatically (e.g. in .bashrc) when the path is imported from
> Windows at
Thanks again - everything works now.
Dmitry
Brian Dessent wrote:
Dmitry Golovaty wrote:
Thanks - the culprit is the MATLAB entry
/cygdrive/c/Program Files/MATLAB/R2007a/bin/win32
in the path; removing it fixes the problem ... is there way to pluck
it out automatically (e.g. in .bashrc) w
Dmitry Golovaty wrote:
> Thanks - the culprit is the MATLAB entry
>
> /cygdrive/c/Program Files/MATLAB/R2007a/bin/win32
>
> in the path; removing it fixes the problem ... is there way to pluck
> it out automatically (e.g. in .bashrc) when the path is imported from
> Windows at Cygwin start-up? T
another thread - I did not subscribe in time to get the original
message.
Dmitry
[EMAIL PROTECTED] wrote:
Microsoft Visual C++ Runtime Library
Runtime Error!
Program C:\cygwin\bin\convert.exe
R6034
An application has made an attempt to load the C runtime library
incorrectly.
Is there anything
[EMAIL PROTECTED] wrote:
> Microsoft Visual C++ Runtime Library
>
> Runtime Error!
>
> Program C:\cygwin\bin\convert.exe
>
> R6034
> An application has made an attempt to load the C runtime library
> incorrectly.
>
> Is there anything that I can do to fix thi
to launch a .sh shell script
to perform cleanup(?).
this thing stayed stuck in an apparently look of memory errors. had to use
task manager to kill it.
after that any attempt to start bash gave a "runtime error 216 at [various]"
...also with an infinite stream of complaints which cou
At 03:15 PM 8/27/2004, you wrote:
>I'm getting a setup.exe runtime error when trying to install from a local
>disk (after downloading from the internet) just after the MD5 checks.
>
>I thought it was about time I upgrade.
>
>My current cygwin1.dll version 1.5.5 (does s
David A. Cobb <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED], [EMAIL PROTECTED]
> Cc: Cygwin Application Packaging Discussion List <[EMAIL PROTECTED]>
> Subject: Re: setup 2.427 runtime error
>
> Shaffer, Kenneth wrote:
>
> >I'm getting a setup.exe runtime er
Shaffer, Kenneth wrote:
I'm getting a setup.exe runtime error when trying to install from a local
disk (after downloading from the internet) just after the MD5 checks.
I just reported a possibly similar situation; discussions of setup.exe
mostly take place on cygwin-apps list.
I'm
I'm getting a setup.exe runtime error when trying to install from a local
disk (after downloading from the internet) just after the MD5 checks.
I thought it was about time I upgrade.
My current cygwin1.dll version 1.5.5 (does setup use the dll?)
--
Ken Shaffer
- - - - - - - Append
> -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
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
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
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
I have the following example to propose:
/** aa.c **/
#define NXY 5000
#define NXY 7000
int xy[NXY][NXY];
main(){
printf("ok\n");
}
This will work when NXY=5000, but will generate a SIGSEV exception before
reaching the first statement when NXY=7000.
The array in the faulty case is 187MB. The gcc
I have been using cygwin for quite a while, and this problem has
me baffled.
When I attempt to install cygwin (using setup.exe version 2.427), the
installation aborts with the following error:
"Microsoft Visual C++ Runtime Library"
Runtime error!
Program C:\cygwin-setup\setup.exe
Th
After running a windows update, which installed some 12 critical patches
for windows 2000, and 4 optional ones, the gdb/cygpath/others crash has
disappeared.
example of the problem:
C:\cygwin>cygpath
28 [main] ? 2608 init_cheap: Couldn't reserve space for cygwin's heap, Win3
2 error 487
c:
I just wanted to report that I have the same problem with the cygwin
snapshots that I have tried (0217,0218,0220,0221) on my (now freshly
reinstalled) w2k machine with all hotfixes and servicepacks applied. I
have also tried with XFree86-xserv 4.3.0-44 with same results.
Another application that c
Just looked at what was going on in that other thread, and noticed that
the original poster over in that thread, Chih-Yi Kuan, is having this
problem with gdb under stock 1.5.7-1:
(from gdb under bash)
3 [main] ? 3552 cygheap_fixup_in_child: Couldn't reserve space
for cygwin's heap (0x6
Thanks you.
> -Original Message-
> From: Brian Ford [mailto:[EMAIL PROTECTED]
> Sent: Friday, February 20, 2004 12:17 AM
> To: Chih-Yi Kuan
> Cc: 'Cygwin List'
> Subject: RE: Gdb runtime error
>
>
> On Thu, 19 Feb 2004, Chih-Yi Kuan wrote:
> >
On Thu, 19 Feb 2004, Chih-Yi Kuan wrote:
> Larry Hall [mailto:cygwin-lh at cygwin dot com] wrote:
>
Please do not quote plain text email addresses in replies. They are food
for spammers.
Also, Larry forgot to remind you to please *attach* your cygcheck output
next time. If you put in inline, it
Sorry but can you explain more detail about how to use these files?
Thank you.
> -Original Message-
> From: Larry Hall [mailto:[EMAIL PROTECTED]
> Sent: Thursday, February 19, 2004 11:32 PM
> To: Chih-Yi Kuan; [EMAIL PROTECTED]
> Subject: Re: Gdb runtime error
>
>
At 12:15 AM 2/19/2004, Chih-Yi Kuan you wrote:
>After the cygwin setup from the cygwin installer. Execution of gdb in
>bash results in the follow error message:
>
>*
>
> 3 [main] ? 3552 cygheap_fixup_in_child: Couldn't reserve space
>for cygwin's heap (0x6167 <0x15A0
After the cygwin setup from the cygwin installer. Execution of gdb in
bash results in the follow error message:
*
3 [main] ? 3552 cygheap_fixup_in_child: Couldn't reserve space
for cygwin's heap (0x6167 <0x15A>) in child, Win32 error 487
C:\cygwin\bin\gdb.exe
My apologies.
I finally decided to look for myself in binutils.. And found a way to fix
the issue.
I proposed a patch to the binutils folks.
--Ivan
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: h
In August 1st I wrote:
> For a some time I have experienced a major problem with Cygwin
> setup.exe. Otherwise it runs normally (I can select download
> site, packages, it downloads packages) but it does not
> install/uninstall anything. Instead it crashes to "Runtime
>
Continuing my attempts to run xdvi under cygwin, here are my
success and new problem:
I have fixed the problem with fcntl(F_SETOWN) - it actually
is an option in the configuration file which allows to inhibit
the use of this function.
But xdvi still goes nuts and crashes after eating the entire
You may be right. I was just looking to the memory
eaten by the xdvi process as reported by the W2K's
task manager. The crash was occurring at 128Mb of
allocated memory, and now occurs at 256Mb.
Thanks for this clarification, and thanks Corinna for the
explanation about vfork(). I hope I will be
:59:30 -0400:
>
>>-==- HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\
>
>>Create a new DWORD value there called "heap_chunk_in_mb" that
>>contains >the maximum amount of memory (in Mb) your application needs
>>(watch the
>>hex/decimal toggle).
On Thu, Mar 07, 2002 at 10:15:06AM -0500, Nicolae Santean wrote:
> 1. Apparently, the heap_chunk_in_mb registry does not always tweak
> the memory default limit for cygwin. Many people report this issue
> and it actually happened to me as well. But, here's what I tried:
> increased the value to 51
no registry key is set. -==-
>Good luck.
>Randall Schulz Mountain View, CA USA
>Hello,
>I have recently compiled xdvi22.53 under cygwin1.3.9, but I am having
>problems running it. The runtime error is:
xdvi: fcntl F_SETOWN: Invalid argument
- mktexpk --mfmode cx --bdpi 300 -
On Wed, Mar 06, 2002 at 10:32:38PM -0500, Nicolae Santean wrote:
>
> I believe that the 128 megabyte realloc failure is a consequence
> (memory leak - maybe) of the other errors:
>
> "xdvi: fcntl F_SETOWN: Invalid argument", "setsid: Not owner"
>
> I am getting these errors first, and then I wa
I believe that the 128 megabyte realloc failure is a consequence
(memory leak - maybe) of the other errors:
"xdvi: fcntl F_SETOWN: Invalid argument", "setsid: Not owner"
I am getting these errors first, and then I watch the memory being
slowly flooded. By no means xdvi should go to 128Mb. I sus
gle). Exit and restart all cygwin applications.
The default is 128 (i.e. 128Mb) if no registry key is set.
-==-
Good luck.
Randall Schulz
Mountain View, CA USA
At 18:39 2002-03-06, you wrote:
>Hello,
>
>I have recently compiled xdvi22.53 under cygwin1.3.9, but
>I am having pro
Hello,
I have recently compiled xdvi22.53 under cygwin1.3.9, but
I am having problems running it. The runtime error is:
xdvi: fcntl F_SETOWN: Invalid argument
- mktexpk --mfmode cx --bdpi 300 --mag 'magstep(0.5)'
--dpi 329 cmsl10 '>&3'
setsid: Not owner
xdvi: fcntl
61 matches
Mail list logo
