Neusbeer wrote:
>
> Hello,
>
> just today something changed in my installation.
> but can't figure out what's wrong.
> when I type wget or vim it responses with nothing just a linebreak.
> Can somebody help me.
> I did some updating this week with setup.exe and got a kinda messed up
> /etc/pr
Difference with Linux might be matter of timing. (Or, might gdb version).
The problem is that gdb calls poll() while it has (all) data already in libc
buffers.
It also calls fileno() and isatty() arround that time.
(Also {m,c,re}alloc, free, pthread_sigmask, vsprints)
Gdb first calls poll() wit
http://cygwin.com/ml/cygwin-cvs/2011-q2/msg00196.html
introduced reordering of SH_- related memory blocks and the following change
| - unsigned size = offsets[i + 1] - offsets[i];
| + unsigned size = offsets[i] - offsets[i + 1];
| offsets[i] += delta;
| if (!VirtualAl
jan.kolar wrote:
>
> Completion can be very slow in directories with large number of files.
>
And it can be very slow in directories where previously WAS large number of
files,
although they are already deleted. Applies mainly to FAT filesystem.
JK
--
View this message in conte
http://cygwin.com/problems.html
suniuin wrote:
>
> hi all,
>
> I got the bash completion problem which is very upset me, following is
> an example:
> in my home directory, there is a file : pkf
>
> if I want to vi the file and I type :
>
> vi pk(press tab)
>
> but there is no response or it
> Jon Clugston wrote:
> I tried to reproduce by creating long command lines to other commands
> and none were corrupted.
I tried two now.
The first one turned out to be a script around xterm. :-(
The second fails the test:
xwininfo.exe -display :0 -children &
>>> tty0 00:00:00 xwininfo -chi
Christopher Faylor-8 wrote:
>
> On Mon, Oct 17, 2011 at 10:27:18AM +0200, Corinna Vinschen wrote:
>>On Linux, /proc/$PID/cmdline always contains the full command line as
>>it has been when the process got started, irrespectively of changes
>>after process startup. It looks like the loader crea
Another related 'recent update ?' message at cygwin-xfree:
http://old.nabble.com/Could-not-open-a-connection-to-your-authentication-agent.-tt32667563.html
"Not sure if this is directly related to the recent update, but after I
"did the update, I could not open an connect to the ssh agent
-
jan.kolar wrote:
>
>> I can reproduce this issue. It's not that it can't create the socket,
>> actually it does so, but for some reason it calls select and, when select
>> returns, it decides to clean up and exit.
>
> On modified cygwin 1.7.9-1, th
> I can reproduce this issue. It's not that it can't create the socket,
> actually it does so, but for some reason it calls select and, when select
> returns, it decides to clean up and exit.
On modified cygwin 1.7.9-1, the socket does not disappear
(until shortly, 5 seconds?, after I type exi
jan.kolar wrote:
>
> For example sendmail likes to do that (on Linux):
>root 3051 sendmail: accepting connections
>smmsp 3061 sendmail: Queue runner@00:01:00 for
> /var/spool/clientmqueue
>root 14631 sendmail: server [1.46.244.248] cmd
> I've checked and on Linux (at least) xterm's command line is not
> corrupted.
That means: unchanged ?
Or, with -sl 2000 +tb removed ?
A version (!) of xterm on Linux, which does not know +tb option, does not
change cmdline.
> From looking at the xterm code, it would appear that the X
> lib
defaria wrote:
>
> Why wouldn't exec(1) be responsible for setting up /proc and therefore
> fill in cmdline with effectively $0 *before* the program itself ever got
> around to calling XrmParseCommand? (I'm not well versed in the
> underlying mechanics here and I have not reviewed the code b
> jc807j2668 1 0 08:59 tty0 00:00:00 xterm -e ssh server
80x72+285+0 -e ssh server
> jc807j3004 1 0 08:59 tty0 00:00:00 xterm -e ssh server
> 80x72-8+0 -e ssh server
> jc807j2928 5852 0 09:12 ?00:00:00 xterm 2 +tb
> The actual command lines for the 3 x
The content /proc//cmdline is created by the proces itself, in a
separate thread.
Since you use memory intensive application (xterm -sl 2) we can
speculate
it might be caused by memory corruption in xterm.
Observe whether the processes with corrupted /proc//cmdline behave
properly
and try a
Oleksandr Gavenko-2 wrote:
>
> 12.10.2011 14:59, jan.kolar пишет:
>> Oleksandr Gavenko-2 pishet:
>>>$ cygcheck -c vim
>>>Cygwin Package Information
>>> Package VersionStatus
>>> vim 7.3.254-1 OK
Oleksandr Gavenko-2 pishet:
>03.10.2011 2:35, jan.kolar pishet:
>> Oleksandr Gavenko (aka gavenkoa) wrote:
>>>
>>> $ cat ~/.vimrc
>>> syntax on
>>>
>>> $ vim
>>> Error detected while processing /cygdrive/e/home/.vimrc:
Christopher Faylor-8 wrote:
>
> On Mon, Oct 10, 2011 at 10:43:42PM -0400, Ken Brown wrote:
>>My STCs still don't work right for me under the 2011-10-10 snapshot.
>>The bash subprocess no longer shows as stopped when I run ps, but it
>>doesn't produce any output either, and it doesn't terminat
Christopher Faylor-8 wrote:
>
> On Sun, Oct 09, 2011 at 07:58:15PM -0400, Christopher Faylor wrote:
>>On Sat, Oct 08, 2011 at 05:39:20PM -0400, Ken Brown wrote:
>>>Attached is a slight modification of the STC, in which I set stdin for
>>>the bash subprocess to /dev/null. With this modificatio
gviewer wrote:
>
> Hello, I used to be able to install WordNet alone on my Windows machine.
> Recently I want to install wordnet on a new Windows 7 machine. However,
> The WordNet installer always triggers the cygwin installer. I don't want
> to do that. then I remove cygwin from my machine, bu
Ken Brown-6 wrote:
>
> On 10/9/2011 4:10 PM, jan.kolar wrote:
>>
>>
>> Ken Brown-6 wrote:
>>>
>>> The attached STC arose from my attempt to understand the problem
>>> discussed starting in
>>>
>>> http://cygwin.com/ml/cyg
Ken Brown-6 wrote:
>
> The attached STC arose from my attempt to understand the problem
> discussed starting in
>
>http://cygwin.com/ml/cygwin/2011-09/msg00405.html .
>
> I'm starting a new thread because there appears to be a Cygwin problem
> having nothing to do with emacs.
>
> The ST
Ken Brown-6 wrote:
>
> On 10/8/2011 11:35 AM, Ken Brown wrote:
> ched is a slight modification of the STC, in which I set stdin for
> the bash subprocess to /dev/null. With this modification, the program
> works as expected (and as on Linux) with cygwin-1.7.9, but the same
> problem as befo
I admit I do not understand.
Is it pipefile or pipefail ?
What is "name-based commands" ?
And what you do?
At the bash prompt, you type ".." and it answers "".
Can you fill in the dots please?
--
View this message in context:
http://old.nabble.com/name-based-commands-aren
Corinna Vinschen-2 wrote:
>
> On Sep 26 14:18, Paul Maier wrote:
>> Hi,
>>
>> scrolling up the console output to review the console history, then
>> pressing
>> Enter scrambles the console.
>
> That's a long standing behaviour of the Cygwin console emulation.
> I guess it can be fixed, but som
Kris Thielemans-2 wrote:
>
> Hi
>
> I'm running (up-to-date) Cygwin 1.7.9-1 on Windows7 sp1 64-bit.
>
> I recently am getting lots of errors like this
>
> bash 2112 exception::handle: Exception: STATUS_ACCESS_VIOLATION
>
> The messages do not happen all the time (for example, from bash (in
Christopher Faylor-8 wrote:
>
> On Sun, Oct 02, 2011 at 03:12:39AM -0700, Marc Girod wrote:
>>marco atzeri-4 wrote:
>>> My experience is that using the standard "problem report" improve the
>>> chance to correctly identify the root cause and reduce the number of
>>> guess that everyone could hav
Oleksandr Gavenko (aka gavenkoa) wrote:
>
>$ cat ~/.vimrc
> syntax on
>
>$ vim
> Error detected while processing /cygdrive/e/home/.vimrc:
> line1:
> E484: Can't open file /usr/share/vim/syntax/syntax.vim
> Press ENTER or type command to continue
>
> This issue reported previously:
Paul Maier-2 wrote:
>
> Hi,
>
> scrolling up the console output to review the console history, then
> pressing
> Enter scrambles the console.
>
> This is Cygwin-specific: The same steps with Windows' cmd instead of bash
> is working fine.
>
>
> To reproduce:
>
> 1. Open Windows MS-DOS conso
Alan Sinclair-2 wrote:
>
> After installing Cygwin LSA authentication, code signing fails coming in
> over ssh from another machine.
> This is cygwin 1.7.9 on x64 Windows 2003 (CYGWIN_NT-5.2-WOW64 AlansW2033
> 1.7.9(0.237/5/3) 2011-03-29 10:10 i686 Cygwin)
>
> Running locally, signing succeeds
Marc Girod wrote:
>
> Hello,
>
> I keep my installation up-to-date on a weekly basis, and never fail to
> rebaseall/peflagsall as many times as needed to be able to start emacs
> in an X session without fork errors. Then I do a perlrebase.
>
> However, I eventually get STATUS_ACCESS_VIOLATION
Marc Girod wrote:
>
>
> marco atzeri-4 wrote:
>>
>> Problem reports: http://cygwin.com/problems.html
>> so at least we have an idea of your system
>>
>> in addition, have you checked
>> http://cygwin.com/faq/faq.using.html#faq.using.bloda
>>
>> Antivirus and driver are the most likely
> On 16/09/2011 7.46, J.V. wrote:
>> I install the latest cygwin on Windows XP Pro x32 on a VM under the
>> latest version of VirtualBox.
>>
>> When I do anything it takes a long time.
jvsrvcs wrote:
>
> OK , I was wrong. I removed bash completion / git completion and on a
> Virtual Box VM
João Moreira wrote:
>
> On Wed, Sep 14, 2011 at 7:40 PM, Larry Hall (Cygwin) wrote:
> ...
> During startup of cygwin, which took about 40 seconds,
> ...
>
What about the timing and output of the following:
strace bash --noprofile -norc -c /bin/echo
jk
--
View this message in context:
ht
Christopher Faylor-8 wrote:
>
> On Thu, Sep 08, 2011 at 03:00:54PM -0700, jan.kolar wrote:
>>Recommendations:
>> * Use popen() with added test for null fh.
>> gdb is much more stable.
>>
>> * For each 'run' restart gdb.
>>The
Christopher Faylor-8 wrote:
>
>>I suspect more a borderline cygwin issue that octave is just hitting.
>>But of course I could be wrong.
>
> Sure it could be but adding a band-aid to work around the issue is not
> the way to go.
>
So we have sequence
1. popen
2. fclose
3. pc
marco atzeri-4 wrote:
>
> Hi,
> I am trying to identify the octave segfault, last reported on
> http://cygwin.com/ml/cygwin-announce/2011-08/msg3.html
>
> To reproduce: run octave from xterm and at prompt
> -
> graphics_toolkit ("fltk")
> x=1:10;
> plot(x,x)
>
marco atzeri-4 wrote:
>
> New versions 3.4.2-1 of
>
> octave,
> octave-devel,
> octave-doc
>
> are available in the Cygwin distribution:
>
> CHANGES
> This is a upstream bug fix release of 3.4.x
>
Please
what versions of libgfortran3 and liblapack0
are needed ?
I tried to do
Marco,
this is not point where octave always crashes, since in an strace dump I
sent you separately, I read
188 145419026 [main] octave-3.4.2 11704 close: close (6)
31 145419057 [main] octave-3.4.2 11704 fhandler_base::close: closing
'pipe:[6]'
34 145419091 [main] octave-3.4.2 11704 close
> Then you need to install the rebase package:
> http://cygwin.com/cgi-bin2/package-grep.cgi?grep=rebaseall
Why the newest version
rebase/rebase-3.0-2 utilities for rebasing DLLs to load at alternate
addresses
is listed in the middle of this page?
It's confusing.
Again, cygcheck -p
40 matches
Mail list logo
