I have tried with an user that is in administrators group and it still
doesn't work.
and the cat socket error really is no such device or address and the
same is reported in rxvt so I guess we can't conclude from that that
permissions are a problem.
What other info can I provide?
Should I strace s
Andrew Schulman wrote:
> Andrew Schulman wrote:
> >> Hi!
> >> What is the current status of screen reattach?
> >> For me it does not work under the default cygwin bash shell, which
> >> uses cmd console afaik and it does not work under cygwin sshd. The
> >> only way it works is under cygwin rxvt. I
Correction: besides rxvt, screen also works in xterm.
However I can't get screen working in the default cygwin CMD console
running bash and also can't get it working over ssh.
On 2007-10-05, Damjan Lango wrote:
> I have read the screen/README.Cygwin and couldn't find a solution.
> I have set the
Another update on my screen adventures, please accept my apologies
since i'm posting so frequently.
I have removed completely the /tmp/uscreens/S-Damjan directory and
it's contents and killed all the cygwin processes. Now screen
reattaching works in CMD cygwin bash window as well (and rxvt and
xte
rxvt default font setting is awful, at least on vista.
Here is a screenshot:
http://damjan.lango.googlepages.com/rxvt-font.jpg
comparing the default font with some other font settings (terminal,
lucida console, 7x14)
rxvt --help which should report used resources says:
$ rxvt --help 2>&1 | grep fo
Daniel Noll wrote:
On Friday 05 October 2007 13:07:41 Larry Hall (Cygwin) wrote:
OK, we now know the symptoms and the problem. But we don't have any basic
configuration information to do some simple triage with. In short:
Problem reports: http://cygwin.com/problems.html
Please read an
As I see you're requesting cygcheck -s -v -r output for other
problems, I'm attaching it here as well if it helps with my ssh /
screen reattach problem.
btw, when cygcheck completed, it also reported:
'id' program not found
'id' program not found
but id is working fine:
$ id
uid=1000(Damjan) gid=51
[EMAIL PROTECTED] wrote:
Can you please tell me if Cygwin is expected to run on Windows 2003 64
bit Enterprise Edition?
Yes (but Cygwin won't magically be 64-bit). I use Cygwin on a 2k3 r2 x64
box to create a unix-like build environment (that matches the other
platforms we support). Note that
On Fri, Oct 05, 2007 at 10:43:08AM -0500, Matthew Woehlke wrote:
> [EMAIL PROTECTED] wrote:
>> Can you please tell me if Cygwin is expected to run on Windows 2003 64
>> bit Enterprise Edition?
>
> Yes (but Cygwin won't magically be 64-bit). I use Cygwin on a 2k3 r2 x64
> box to create a unix-like
I'm having the exact same problem on win64 with gdb. The PATH variable has
been set manually to avoid possible syntax errors, but the same problem
exists when I don't shorten the PATH. Cygcheck doesn't list any dlls as
missing. gdb works on my win32 computer.
Any other ideas?
Doug
$ uname -a
Doug Coleman wrote:
> I'm having the exact same problem on win64 with gdb. The PATH variable has
> been set manually to avoid possible syntax errors, but the same problem
> exists when I don't shorten the PATH. Cygcheck doesn't list any dlls as
> missing. gdb works on my win32 computer.
>
> An
I had come across with the following problem: after upgrading Cygwin from
version 1.5.19-4 to 1.5.24-2 my application (relational database)
began to function several times slower. The reason was a slowdown of
a function, which performs rebalancing of table index tree; this function
calls write() fu
René Berber-2 wrote:
>
> Doug Coleman wrote:
>
>> I'm having the exact same problem on win64 with gdb. The PATH variable
>> has
>> been set manually to avoid possible syntax errors, but the same problem
>> exists when I don't shorten the PATH. Cygcheck doesn't list any dlls as
>> missing. g
René Berber-2 wrote:
>
> Doug Coleman wrote:
>
>> I'm having the exact same problem on win64 with gdb. The PATH variable
>> has
>> been set manually to avoid possible syntax errors, but the same problem
>> exists when I don't shorten the PATH. Cygcheck doesn't list any dlls as
>> missing. gd
Doug Coleman wrote:
> Here is 'info files' in gdb. There have been other posts about the same
> problem, but no resolution afaik:
> http://cygwin.com/ml/cygwin/2007-03/msg00182.html
Yes, same problem.
> $ gdb ./factor-nt
> GNU gdb 6.5.50.20060706-cvs (cygwin-special)
> Copyright (C) 2006 Free S
Doug Coleman wrote:
> So I attached to the running process and that works!
Nice one, nothing maps to the infamous address (in fact everyting is way above
that -- with one more digit in the address), seems like the gdb bug report at
MingW might be in the right track.
> Here is an info files from
Dave,
I'm not sure what to do. I see you attached a diffs file. Is there a utility
such as patch that I can use to apply those diffs? What would be the
command?
Thanks,
Siegfried
>
>On 04 October 2007 22:13, Siegfried Heintze wrote:
>
>> Siegfried wrote:
>> OK, I tried that. See below for the res
On 05 October 2007 03:28, Lynn Winebarger wrote:
[ Cc'ing the mailing list back in. ]
> On 10/4/07, Lynn Winebarger <> wrote:
>> On 10/4/07, Dave Korn <> wrote:
>>> Yes, why not; feel free to send them both to me, off list. Can't promise
>>> I'll spot anything, but I'll take a look. (My first
On 05 October 2007 23:16, Siegfried Heintze wrote:
> Dave,
> I'm not sure what to do. I see you attached a diffs file. Is there a utility
> such as patch that I can use to apply those diffs? What would be the
> command?
There's a utility *exactly* such as patch that you can use to apply those
d
I forgot to cc the list, but the origin of the issue might be of
interest to someone.
On 10/5/07, Dave Korn <[EMAIL PROTECTED]> wrote:
> Well, this was a weird one. I think the underlying problem must be a bug in
> larceny's final link stage during the build. First, this command made your
> bi
Matthew Woehlke wrote:
> [EMAIL PROTECTED] wrote:
>> Can you please tell me if Cygwin is expected to run on Windows 2003 64
>> bit Enterprise Edition?
>
> Yes (but Cygwin won't magically be 64-bit). I use Cygwin on a 2k3 r2 x64
> box to create a unix-like build environment (that matches the other
21 matches
Mail list logo
