On 2023-09-06 16:20, Asad Ali via Cygwin wrote:
On Fri, Dec 30, 2022 at 5:46 AM Asad Ali wrote:
I'm a penetration tester and bug bounty hunter. I have found a potential
vulnerability in the site. Please review the report below.
Is there any update on this ? I'm hoping to receive a reward for t
Hi Team,
Is there any update on this ? I'm hoping to receive a reward for the
reported bug.
Waiting for your response.
On Fri, Dec 30, 2022 at 5:46 AM Asad Ali wrote:
> Hey Team,
>
>
>
> I'm a penetration tester and bug bounty hunter. I have found a potential
> vulnerability in the site. Pleas
Am 10.03.2022 um 10:37 schrieb n952162:
xterm*VT100.Translations only when mouse is over the window with focus
Discovered with click-to-focus, in FVWM
In particular, I'm talking about the function keys. In this case, these
are NOT mapped in fvwm, but in xterm.
Pressing a function key, like F1,
On Tue, Feb 8, 2022 at 3:02 PM julie77793 wrote:
Cygwin doesn't create an environment variable in bash to indicate that the
> platform is Cygwin under Windows.
>
FYI, as a point of decorum: The subject line of this thread is rather
undiplomatic.
(Bug usually means "software should do X but fails
On 2/8/22 2:01 PM, julie77...@gmail.com wrote:
Cygwin doesn't create an environment variable in bash to indicate that the
platform is Cygwin under Windows.
This causes compatibility problems when running various tools. Most of my
issues have been with Python tools running Windows Python.
I have
Hi, again
I've just realized that new cygwin DLL keeps terminal edit capabilities for
DOS commands (basically: retriving previous commands with arrow keys), what is
a very good feature.(I use mintty as terminal. I forgot to mention in my
previous email).
So, I apologize and answer myself: now
On 12/13/2020 9:41 AM, Marco Atzeri via Cygwin wrote:
On 13.12.2020 13:43, Takashi Yano via Cygwin wrote:
On Sat, 12 Dec 2020 20:05:05 + (UTC)
Alberto Moral Beneitez via Cygwin wrote:
Hi, everybody
Please try:
env CYGWIN=disable_pcon rlwrap cmd
Also, you can use alias like:
alias rlwra
On 13.12.2020 13:43, Takashi Yano via Cygwin wrote:
On Sat, 12 Dec 2020 20:05:05 + (UTC)
Alberto Moral Beneitez via Cygwin wrote:
Hi, everybody
Please try:
env CYGWIN=disable_pcon rlwrap cmd
Also, you can use alias like:
alias rlwrap="env CYGWIN=disable_pcon rlwrap"
I had the impressi
On Sat, 12 Dec 2020 20:05:05 + (UTC)
Alberto Moral Beneitez via Cygwin wrote:
> Hi, everybody
> First of all, this is my first bug report, so I don't know if I am doing
> correctly... I don't know if one must be registered to summit this type of
> repport. And be patient with my English.
>
On 2020/04/02 06:43, Andrey Repin wrote:
That's not what actually happens.
...\Documents> ls -1 *.pdf
21927-ticket.pdf
'Stars! Universe Map.pdf'
---
Thank you for your update.
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentatio
Greetings, L A Walsh!
> On 2020/03/24 00:18, Jay Libove via Cygwin wrote:
>> Problem:
>> Under certain circumstances (see Steps to Reproduce, below) Cygwin programs'
>> built-in argv[] globbing will produce unexpected:
>> "{programName}: cannot access '{glob pattern}: No such file or directory"
>
On 2020/03/24 00:18, Jay Libove via Cygwin wrote:
Problem:
Under certain circumstances (see Steps to Reproduce, below) Cygwin programs'
built-in argv[] globbing will produce unexpected:
"{programName}: cannot access '{glob pattern}: No such file or directory"
e.g.
"ls: cannot access '*.pdf': No
Maybe it can simply be fixed by changing the order of setting up locale stuff
and applying the expansion in cygwin?
(I would look into the code if I had a clue where to find the respective
things.)
I would guess dcrt0.cc, the Cygwin DLL runtime initialization.
..mark
--
Problem reports:
Am 24.03.2020 um 08:18 schrieb Jay Libove via Cygwin:
Hi Cygwin team,
Here is a consolidated bug report based on the discussion in recent days which I'd started under
the subject " shell expansion produces e.g. "ls: cannot access '*.pdf': No such file or
directory" in Windows CMD shell, but wor
On Thu, 29 Aug 2019, 02:38 Steven Penny, wrote:
> On Wed, 28 Aug 2019 15:57:23, Quanah Gibson-Mount wrote:
> > My original post contained a link to a patch allowing for Cygwin to
> > correctly terminate native Windows processes. I understand it is not
> the
> > position of the Cygwin project to
On Wed, 28 Aug 2019 15:57:23, Quanah Gibson-Mount wrote:
My original post contained a link to a patch allowing for Cygwin to
correctly terminate native Windows processes. I understand it is not the
position of the Cygwin project to deal with situation, so I think we can
just let it drop.
I w
--On Wednesday, August 28, 2019 2:33 PM -0700 Kaz Kylheku
<920-082-4...@kylheku.com> wrote:
Cygwin can't introduce Unix-like shutdown mechanisms (like the
handling a non-fatal signal) into non-Cygwin processes which have
no concept of that. It makes no sense.
My original post contained a link
On 2019-08-28 08:59, Quanah Gibson-Mount wrote:
--On Wednesday, August 28, 2019 6:45 PM +0200 Corinna Vinschen
wrote:
Not likely. Cygwin handles Ctrl-C by generating SIGINT. This only
works reliably with Cygwin processes. There's
$ /bin/kill -f
to call the Win32 function TerminateProce
On Aug 28 08:59, Quanah Gibson-Mount wrote:
>
>
> --On Wednesday, August 28, 2019 6:45 PM +0200 Corinna Vinschen
> wrote:
>
> > Not likely. Cygwin handles Ctrl-C by generating SIGINT. This only
> > works reliably with Cygwin processes. There's
> >
> > $ /bin/kill -f
> >
> > to call the
--On Wednesday, August 28, 2019 6:45 PM +0200 Corinna Vinschen
wrote:
Not likely. Cygwin handles Ctrl-C by generating SIGINT. This only
works reliably with Cygwin processes. There's
$ /bin/kill -f
to call the Win32 function TerminateProcess(pid) on a non-Cygwin
process or an unresp
On Aug 28 08:18, Quanah Gibson-Mount wrote:
>
>
> --On Thursday, July 25, 2019 11:32 AM -0700 Quanah Gibson-Mount
> wrote:
>
> > As found and reported to the MSYS team back in 2006 by Howard Chu, if a
> > native process is spawned, control-C, the kill command, etc, may not
> > actually kill the
--On Thursday, July 25, 2019 11:32 AM -0700 Quanah Gibson-Mount
wrote:
As found and reported to the MSYS team back in 2006 by Howard Chu, if a
native process is spawned, control-C, the kill command, etc, may not
actually kill the process. Details are here:
I haven't seen a reply to this
On May 10 14:57, Agner Fog wrote:
> Bug description:
>
> The sqrtl function under Clang causes an access violation when the argument
> is negative.
>
> This error occurs only under Cygwin.
>
> This error occurs only with the sqrtl function, not with sqrt or sqrtf
>
> Attached:
>
> sqrt.cpp: pr
Agner Fog, on Friday, May 10, 2019 04:55 PM, wrote...
>$ uname -a
>CYGWIN_NT-10.0 DESKTOP-08PNUTF 3.0.6(0.338/5/3) 2019-04-06 16:18 x86_64
>Cygwin
>
>
>$ clang --version
>clang version 5.0.1 (tags/RELEASE_501/final)
>Target: x86_64-unknown-windows-cygnus
>Thread model: posix
>InstalledDir: /usr/
$ uname -a
CYGWIN_NT-10.0 DESKTOP-08PNUTF 3.0.6(0.338/5/3) 2019-04-06 16:18 x86_64
Cygwin
$ clang --version
clang version 5.0.1 (tags/RELEASE_501/final)
Target: x86_64-unknown-windows-cygnus
Thread model: posix
InstalledDir: /usr/bin
On 10/05/2019 21.54, Jose Isaias Cabrera wrote:
Agner F
Agner Fog, on Friday, May 10, 2019 03:44 PM, wrote...
>
>On 10/05/2019 15.50, Jose Isaias Cabrera wrote:
>
>> It works for me.
>
>Now it turns out that all the long double math functions cause access
>violations.
>
>If you can't reproduce the error, what can I do to trace it?
>
>
>Exception: STAT
On 10/05/2019 15.50, Jose Isaias Cabrera wrote:
It works for me.
Now it turns out that all the long double math functions cause access
violations.
If you can't reproduce the error, what can I do to trace it?
Exception: STATUS_ACCESS_VIOLATION at rip=00180173164
Sam Habiel wrote:
Wow
Am 10.05.2019 um 15:38 schrieb Sam Habiel:
> Wow I can't believe that The Agner Fog posted on the Cygwin mailing list!
>
> https://www.agner.org/
>
> On Fri, May 10, 2019 at 8:58 AM Agner Fog wrote:
>>
>> Bug description:
>>
>> The sqrtl function under Clang causes an access violation when the
>
Agner Fog, on Friday, May 10, 2019 08:57 AM, wrote...
>
>Bug description:
>
>The sqrtl function under Clang causes an access violation when the
>argument is negative.
>
>This error occurs only under Cygwin.
>
>This error occurs only with the sqrtl function, not with sqrt or sqrtf
>
It works for me.
Wow I can't believe that The Agner Fog posted on the Cygwin mailing list!
https://www.agner.org/
On Fri, May 10, 2019 at 8:58 AM Agner Fog wrote:
>
> Bug description:
>
> The sqrtl function under Clang causes an access violation when the
> argument is negative.
>
> This error occurs only under C
Ole Tange writes:
> I get core dump when running:
>
> $ /bin/echo `seq 100`
> Segmentation fault (core dumped)
>
> This also looks bad:
>
> $ /bin/wc `seq 100`
> 2 [main] -bash 15396 C:\cygwin\bin\bash.exe: *** fatal error - cmalloc
> would have returned NULL
> Hangup
They both just
On Wed, 7 Nov 2018 13:37:53, Ole Tange wrote:
I get core dump when running:
$ /bin/echo `seq 100`
Segmentation fault (core dumped)
This also looks bad:
$ /bin/wc `seq 100`
2 [main] -bash 15396 C:\cygwin\bin\bash.exe: *** fatal error - cmallo=
c would have returned NULL
Hangup
N
On Sep 3 21:12, Achim Gratz wrote:
> Corinna Vinschen writes:
> >> How feasible would it be to generate an alternate setup.ini
> >> (setup-snapshots.ini or something) and include the snapshots in the
> >> actual mirror with a switch to setup to select the alternate file?
> >> When we finally get t
Corinna Vinschen writes:
>> How feasible would it be to generate an alternate setup.ini
>> (setup-snapshots.ini or something) and include the snapshots in the
>> actual mirror with a switch to setup to select the alternate file?
>> When we finally get to it with OCaml's CI, that is probably how I
>
On Sep 2 08:37, David Allsopp wrote:
> Corinna Vinschen wrote:
> > On Sep 1 16:41, David Allsopp wrote:
> > > Corinna Vinschen wrote:
> > > > Some of the path handling is seriously crippled as soon as you start
> > > > using backslashes, and that's a delipberate decision and won't
> > > > change,
Corinna Vinschen wrote:
> On Sep 1 16:41, David Allsopp wrote:
> > Corinna Vinschen wrote:
> > > Some of the path handling is seriously crippled as soon as you start
> > > using backslashes, and that's a delipberate decision and won't
> > > change, even after fixing the aforementioned bug.
> >
> >
cyg Simple wrote:
> On 9/1/2018 5:52 PM, Andrey Repin wrote:
> > Greetings, David Allsopp!
> >
> >>> In terms of this OCAML build system problem:
> >>>
> >>> Please fix your build system. Do not mix POSIX and Win32 paths, use
> >>> POSIX paths only. Backslashes are *no* drop-in replacement for sl
On 9/1/2018 5:52 PM, Andrey Repin wrote:
> Greetings, David Allsopp!
>
>>> In terms of this OCAML build system problem:
>>>
>>> Please fix your build system. Do not mix POSIX and Win32 paths, use POSIX
>>> paths only. Backslashes are *no* drop-in replacement for slashes.
>
>> The "problem" for
Greetings, David Allsopp!
>> In terms of this OCAML build system problem:
>>
>> Please fix your build system. Do not mix POSIX and Win32 paths, use POSIX
>> paths only. Backslashes are *no* drop-in replacement for slashes.
> The "problem" for us is more subtle than this. The program which is
>
On Sat, 1 Sep 2018 21:23:56, Corinna Vinschen wrote:
> > Yes, you would run the chance that you would have to mend an official
> > release several times ... but is that bad?
>
> The idea of test releases is to avoid problem like the one we're discussing
> here in official releases. I'd like to ge
> As for the bug in question: I pushed a patch which should fix this
> issue. I created new developer snapshots and uploaded them to
> https://cygwin.com/snapshots/. Please give them a try.
Thank you Corinna for the quick fix and investigation!
I set up an environment to test it out:
https
On Sep 1 20:08, Houder wrote:
> On Sat, 1 Sep 2018 17:54:35, Corinna Vinschen wrote:
> > I'll fix this and release a 2.11.1 soon, but I still have a question:
> >
> > Why do I push out test releases if nobody cares?
>
> Yes, I know, it is a _hypothetical_question_. You do not really expect
> an
On Sep 1 16:41, David Allsopp wrote:
> Corinna Vinschen wrote:
> > Some of the path handling is seriously crippled as soon as you start using
> > backslashes, and that's a delipberate decision and won't change, even after
> > fixing the aforementioned bug.
>
> I don't quite follow this - does tha
On Sat, 1 Sep 2018 17:54:35, Corinna Vinschen wrote:
> I'll fix this and release a 2.11.1 soon, but I still have a question:
>
> Why do I push out test releases if nobody cares?
Yes, I know, it is a _hypothetical_question_. You do not really expect
an answer.
However it was my thought exactly. N
Corinna Vinschen wrote:
> On Sep 1 09:56, Andreas Hauptmann wrote:
> > On Sat, 1 Sep 2018 01:24:49 +
> > Bryan Phelps wrote:
> >
> > > I'll continue to look around for a more minimal repro,
> >
> > The normalization of paths with backslashes has changed.
> >
> > The following doesn't work any
On Sep 1 09:56, Andreas Hauptmann wrote:
> On Sat, 1 Sep 2018 01:24:49 +
> Bryan Phelps wrote:
>
> > I'll continue to look around for a more minimal repro,
>
> The normalization of paths with backslashes has changed.
>
> The following doesn't work any longer:
>
> cd /tmp
> stat "..
Am 01.09.2018 um 10:10 schrieb Marco Atzeri:
Am 01.09.2018 um 03:24 schrieb Bryan Phelps:
Hello,
Thank you for all the work on Cygwin! I've been using it to spin up
an environment to build the OCaml compiler / toolchain, and it was
working great.
However, today, all our CI builds mysterio
Marco Atzeri wrote:
> Am 01.09.2018 um 03:24 schrieb Bryan Phelps:
> > Hello,
> >
> >
> > Thank you for all the work on Cygwin! I've been using it to spin up an
> environment to build the OCaml compiler / toolchain, and it was working great.
> >
> >
> > However, today, all our CI builds mysteriousl
Am 01.09.2018 um 03:24 schrieb Bryan Phelps:
Hello,
Thank you for all the work on Cygwin! I've been using it to spin up an
environment to build the OCaml compiler / toolchain, and it was working great.
However, today, all our CI builds mysteriously started failing - at first, I
suspected it
Am 01.09.2018 um 03:24 schrieb Bryan Phelps:
Hello,
In the meantime - is there a way we can pin the cygwin package to the 2.10.0-1
version, to unblock our builds?
Thank you!
Bryan
What is the problem in installing the previous version of the package ?
---
Diese E-Mail wurde von Avast A
On Sat, 1 Sep 2018 01:24:49 +
Bryan Phelps wrote:
> I'll continue to look around for a more minimal repro,
The normalization of paths with backslashes has changed.
The following doesn't work any longer:
cd /tmp
stat "..\bin\file.exe" # or
stat "..\\bin\\file.exe"
This however s
On Nov 14 22:22, Ian Hawkins wrote:
> 1 [main] rsync 1176 find_fast_cwd: WARNING: Couldn't compute FAST_CWD
> pointer. Please report this problem to
Old Cygwin version, please update.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer
On May 20 16:41, Sean Gugler wrote:
> Confirmed fixed, Corinna. Awesome! Thank you!
> ~ Sean
>
> On Tue, 20 May 2014 12:39:20 +0200, Corinna Vinschen wrote:
> >On May 19 15:28, Sean Gugler wrote:
> >> Greetings,
> >>
> >> I've discovered that 5.25" and 3.5" floppy drive access became broken
> >> a
Confirmed fixed, Corinna. Awesome! Thank you!
~ Sean
On Tue, 20 May 2014 12:39:20 +0200, Corinna Vinschen wrote:
>On May 19 15:28, Sean Gugler wrote:
>> Greetings,
>>
>> I've discovered that 5.25" and 3.5" floppy drive access became broken
>> as of Cygwin1.dll version 1.7.19-1 (2013-06-05 01:07:23
On May 19 15:28, Sean Gugler wrote:
> Greetings,
>
> I've discovered that 5.25" and 3.5" floppy drive access became broken
> as of Cygwin1.dll version 1.7.19-1 (2013-06-05 01:07:23). I reported
> this back in October, but perhaps the message never got through. The
> problem persists with the late
On 04/09/2013 7:09 PM, Christopher Faylor wrote:
On Wed, Sep 04, 2013 at 03:26:10PM -0600, Warren Young wrote:
This bug could well be Wine's, rather than Cygwin's.
Wine can always play the "It's not documented to work that way card" but
the bottom line is still that it is not a "platform" that
On Thursday, September 05, 2013 at 4:28 AM, Warren Young wrote:
I purposefully said "and licensing" though, because the Windows license
swamps the hardware costs.
It can be true about the SSD and RAM costs but it's not the same kind of
sandbox too (Wine vs VM). But about the licensing costs I
On 9/4/2013 15:54, Earnie Boyd wrote:
On Wed, Sep 4, 2013 at 5:26 PM, Warren Young wrote:
Wine is
cheaper than a VM in terms of hardware requirements and licensing.
You must have some very expensive hardware.
I figure a VM costs me $25-50 in RAM and SSD space. Because it's not a
full OS,
On Wed, Sep 04, 2013 at 03:26:10PM -0600, Warren Young wrote:
>This bug could well be Wine's, rather than Cygwin's.
Wine can always play the "It's not documented to work that way card" but
the bottom line is still that it is not a "platform" that we are interested
in devoting time to.
cgf
--
Pro
On Wed, Sep 4, 2013 at 5:26 PM, Warren Young wrote:
> On 9/4/2013 09:36, Jim Garrison wrote:
>>
>> Am I missing something, or is there a reason one would want to run a
>> Linux emulator under a Windows emulator on Linux?
>
>
> For myself, it is occasionally nice to have a Cygwin sandbox environment
On 9/4/2013 09:36, Jim Garrison wrote:
Am I missing something, or is there a reason one would want to run a
Linux emulator under a Windows emulator on Linux?
For myself, it is occasionally nice to have a Cygwin sandbox environment
to play with when I'm on one of my Macs, away from a Windows bo
On Wed, Sep 04, 2013 at 03:36:46PM +, Jim Garrison wrote:
>Am I missing something, or is there a reason one would want to run a
>Linux emulator under a Windows emulator on Linux?
That is the question I've been asking for years. Someone always has an
answer but I'm never been convinced that it
Am I missing something, or is there a reason one would want to run a Linux
emulator under a Windows emulator on Linux?
On Tue, Sep 03, 2013 at 10:08:44PM -0700, Austin English wrote:
>I recently noticed the 64-bit cygwin installer crashes under wine.
>After further debugging, it appears that the issue is that cygwin is
>misaligning the stack, causing a crash. I've copy/pasted the analysis
>below:
>
>Hello folks,
>
On Jun 25 18:09, Corinna Vinschen wrote:
> On Jun 25 18:03, Corinna Vinschen wrote:
> > On Jun 25 15:38, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
> > > > Your locale is zh_CN.UTF-8. What you're expecting is only guaranteed
> > > > in the C locale:
> > > [...]
> Which also means, AFAICS, Cygwin'
On Jun 25 18:03, Corinna Vinschen wrote:
> On Jun 25 15:38, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
> > > Your locale is zh_CN.UTF-8. What you're expecting is only guaranteed
> > > in the C locale:
> >
> > I'm not quite sure it applies here. I'm using US English Windows 7.
> >
> > LANG = 'e
Lavrentiev, Anton sent the following at Tuesday, June 25, 2013 11:44 AM
>> The character ordering is based on the default Windows ordering for the
>> locale, and that's dictionary ordering, apparently.
>
>Ah, I see what you meant here. There's an elaborated explanation:
>
>http://www.gnu.org/softwa
On Jun 25 15:38, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
> > Your locale is zh_CN.UTF-8. What you're expecting is only guaranteed
> > in the C locale:
>
> I'm not quite sure it applies here. I'm using US English Windows 7.
>
> LANG = 'en_US.UTF-8'
>
> I get the same result:
>
> $ echo abc
> The character ordering is based on the default Windows ordering for the
> locale, and that's dictionary ordering, apparently.
Ah, I see what you meant here. There's an elaborated explanation:
http://www.gnu.org/software/gawk/manual/html_node/Ranges-and-Locales.html
Anton Lavrentiev
Contractor
> Your locale is zh_CN.UTF-8. What you're expecting is only guaranteed
> in the C locale:
I'm not quite sure it applies here. I'm using US English Windows 7.
LANG = 'en_US.UTF-8'
I get the same result:
$ echo abcdeABCDE | sed -e 's/[B-D]/_/g'
ab__eA___E
BUT:
$ echo abcdeABCDE | LANG=C sed '
On Jun 25 22:37, Atry wrote:
> [...]
> $ echo abcdeABCDE | sed -e 's/[B-D]/_/g'
> ab__eA___E
Your locale is zh_CN.UTF-8. What you're expecting is only guaranteed in
the C locale:
$ LANG=C && echo abcdeABCDE | sed -e 's/[B-D]/_/g'
The character ordering is based on the default Windows ordering
On 1/20/2011 8:04 PM, Jonathan Kamens wrote:
This is a bug in a program that is installed and used in pretty much every
single Cygwin installation in the world.
Other people have reported encountering the bug.
I've identified the bug and provided a patch, three weeks ago.
Can I please get some
ix to acknowledge my
existence?
Much obliged,
jik
-Original Message-
From: Jonathan Kamens [jik at kamens dot us]
Sent: Friday, January 07, 2011 11:22 AM
To: cygwin at cygwin dot com
Subject: RE: Bug report for run.exe with patch
ACK?
-Original Message-
From: Jonathan Kamens [j
Sec,
On Thu, Jul 08, 2010 at 03:00:21PM +0200, Stefan `Sec` Zehl wrote:
> I have a problem with cygwin and procmail. If messages exceed a
> certain size, procmail just hangs, eating 100% cpu without doing
> anything.
>
> I've been trying to debug this further, but it just hangs, even with an
> e
On Jun 21 14:22, Linda Walsh wrote:
> I have two accounts on my client machine. One is m...@workstation,
> the other is m...@domain. They are both me and I need to have them
> be able access each other's files mostly transparently.
>
> As a result, in windows, I setup a group (megroup) that cont
On 6/8/2010 1:25 AM, Corinna Vinschen wrote:
Your bug is something else.
I'm still waiting for some helpful debugging like an strace or, even
better, a simple testcase in plain C.
Corinna
If someone using windows 7 out there, can install Latex2html with the
current cygwin, they should be a
On Jun 8 00:54, Nasser M. Abbasi wrote:
> On 6/8/2010 12:46 AM, Alexander T wrote:
> >There is a similar post from 2009 where the conclusion is that this
> >can be caused by very deep forking
> >(http://readlist.com/lists/cygwin.com/cygwin/6/34359.html). Is it
> >possible that the make script does
On 6/8/2010 12:46 AM, Alexander T wrote:
There is a similar post from 2009 where the conclusion is that this
can be caused by very deep forking
(http://readlist.com/lists/cygwin.com/cygwin/6/34359.html). Is it
possible that the make script does very deep, or is stuck in infinite,
recursion?
Yes
Err, 'very deep' was a bit misleading, the error seemed to show up at
2-3 levels according to the last post in that thread.
On 6/8/10, Alexander T wrote:
> There is a similar post from 2009 where the conclusion is that this
> can be caused by very deep forking
> (http://readlist.com/lists/cygwin.
There is a similar post from 2009 where the conclusion is that this
can be caused by very deep forking
(http://readlist.com/lists/cygwin.com/cygwin/6/34359.html). Is it
possible that the make script does very deep, or is stuck in infinite,
recursion?
On 6/8/10, Nasser M. Abbasi wrote:
> On 6/7/20
On 6/7/2010 7:03 PM, Charles Wilson wrote:
On 6/7/2010 8:49 PM, Nasser M. Abbasi wrote:
$ make test
0 [main] perl 5308 C:\cygwin\bin\perl.exe: *** fatal error -
Internal error: TP_NUM_W_BUFS too small.
Error while converting image: No such file or directory
Error: Cannot read 'img
On 6/7/2010 8:49 PM, Nasser M. Abbasi wrote:
>
> $ make test
>
> 0 [main] perl 5308 C:\cygwin\bin\perl.exe: *** fatal error -
> Internal error: TP_NUM_W_BUFS too small.
>
> Error while converting image: No such file or directory
>
> Error: Cannot read 'img2.png': No such file or direc
On 6/7/2010 2:13 PM, Larry Hall (Cygwin) wrote:
Chris wasn't asking you to try this to see if the cygcheck warnings would
go away. He was asking you to try this to see if it made any difference
with your original problem.
OK, I just did. The perl crash is still there.
Please let me know if
On Mon, Jun 07, 2010 at 01:34:21PM -0700, Nasser M. Abbasi wrote:
>On 6/7/2010 1:15 PM, Christopher Faylor wrote:
>> Rather than express amazement that I raised the issue why not just prove
>> that this doesn't mean anything by simplifying your path and trying
>> again?
>
>I am not expressing amaze
On 6/7/2010 4:34 PM, Nasser M. Abbasi wrote:
On 6/7/2010 1:15 PM, Christopher Faylor wrote:
Rather than express amazement that I raised the issue why not just prove
that this doesn't mean anything by simplifying your path and trying
again?
I am not expressing amazement, I was asking a simple q
On 6/7/2010 1:15 PM, Christopher Faylor wrote:
Rather than express amazement that I raised the issue why not just prove
that this doesn't mean anything by simplifying your path and trying
again?
I am not expressing amazement, I was asking a simple question, if one
can't install windows perl
On Mon, Jun 07, 2010 at 12:59:51PM -0700, Nasser M. Abbasi wrote:
>On 6/7/2010 12:41 PM, Christopher Faylor wrote:
>> On Mon, Jun 07, 2010 at 11:48:54AM -0700, Nasser M. Abbasi wrote:
>>>
>>> This is a bug report. attached is output of cygcheck -s -v -r (I get
>>> some access denited warnings btw)
On 6/7/2010 12:41 PM, Christopher Faylor wrote:
On Mon, Jun 07, 2010 at 11:48:54AM -0700, Nasser M. Abbasi wrote:
This is a bug report. attached is output of cygcheck -s -v -r (I get
some access denited warnings btw):
$ cygcheck -s -v -r> cygcheck.out
/usr/bin/cygrunsrv: warning: OpenService
On Mon, Jun 07, 2010 at 11:48:54AM -0700, Nasser M. Abbasi wrote:
>
>This is a bug report. attached is output of cygcheck -s -v -r (I get
>some access denited warnings btw):
>
>$ cygcheck -s -v -r> cygcheck.out
>/usr/bin/cygrunsrv: warning: OpenService failed for 'DcomLaunch': Win32
>error 5
>Ac
Dave Korn wrote:
> Derek Kalweit wrote:
>> If you add a \ to the end of the download path with the 1.7 installer,
>> packages fail to download properly and the installer terminates with an
>> error. I finally realized it was just an amateur mistake in the
>> installer code and tried it without the
Derek Kalweit wrote:
> If you add a \ to the end of the download path with the 1.7 installer,
> packages fail to download properly and the installer terminates with an
> error. I finally realized it was just an amateur mistake in the
> installer code and tried it without the \, and it worked fine.
On Wed, Oct 24, 2007 at 12:21:27PM -0700, Robert P. Goddard wrote:
> This is a reply to the message
Yo! Just reply to the message. You don't have to announce that you're
doing it.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/pr
Can you post the bug{1,2}.cpp files? I would guess that its not a bug,
but rather you are relying on an undefined order of static
initialization that happens to do what you want sometimes but not
others. It's impossible to say for sure without seeing the source files,
though.
Oh I see, you di
This is a reply to the message
http://cygwin.com/ml/cygwin/2007-10/msg00509.html:
The linker is supposed to resolve a function-local static variable into
one exactly one instance, constructed on the first call, even if the
function is expanded in-line from multiple compilation units. It seems
Brad Bell wrote:
I seem to have run across a bug using g++ with -O2 under Cygwin. It has
to do with using static class member functions and standard string.
The bash shell script command
./bug.sh
creates three files, compiles, links, and runs the result. I have run
this command on severa
[EMAIL PROTECTED] wrote:
>\??\C:\cygwin\bin\ioperm.sys has been blocked from loading due to
> incompatibility
>with this system. Please contact your software vendor for a compatible
> version of
>the driver.
Yes, there's no way a 32 bit driver should work in a 64 bit OS.
> Suggesti
* From: Robert Peaslee
* To: cygwin at cygwin dot com
* Date: Fri, 16 Mar 2007 17:19:18 -0400
* References:
<[EMAIL PROTECTED]>
Thrall, Bryan wrote:
>Yes, WinXP stores your username twice ("Full name" and "User Name") and
>Cygwin uses the "hidden" one ("User Name"), but I
On Fri, Mar 16, 2007 at 10:49:36PM -, Thorsten Kampe wrote:
>* Robert Peaslee (Fri, 16 Mar 2007 16:52:40 -0400)
>> Actually, this information is incorrect.
>>
>> Windows XP stores the first username you choose and will associate your
>> current username to it regardless of what you change it
* Robert Peaslee (Fri, 16 Mar 2007 16:52:40 -0400)
> Actually, this information is incorrect.
>
> Windows XP stores the first username you choose and will associate your
> current username to it regardless of what you change it to. Cygwin
> stores nothing, it is asking Windows what your username
Thrall, Bryan wrote:
Yes, WinXP stores your username twice ("Full name" and "User Name") and
Cygwin uses the "hidden" one ("User Name"), but I'm pretty sure you
don't have to reinstall XP to change it!
IIRC, you can change the username from Control Panel->User
Accounts->Advanced tab->Advanced bu
1 - 100 of 159 matches
Mail list logo
