First off - thanks Corinna - the rxvt/run issue on Windows 7 is
resolved with 1.7 - thread:
http://cygwin.com/ml/cygwin/2009-10/msg00372.html
Now onto reporting bugs... I am running cygwin 1.7.0-62 on Windows 7.
'ls' on network drives is failing. Also, mount -c '/' does not seem
to stick. Yes
It appears that two EXEs can coexist (with the registry setting) but
only whichever one was so named first will be run:
$ cat > lower.c <
int main(void) { printf("I am a lower-case a\n"); return 0; }
EOF
$ cat > upper.c <
int main(void) { printf("I am an UPPER-case A\n"); return 0; }
EOF
$ gcc
Dave Korn wrote:
> I'd investigate phdl. What OS version are you using? 32- or 64-bit? Have
> we possibly got the wrong packing or alignment of the PEB structure or
> something like that?
32bit Vista SP1. I can't imagine that the PEB would be messed up,
because then /every/ fork would die hor
The patch would probably solve the same problem for displayging Japanese
characters.
regards
Corinna Vinschen wrote:
> On Oct 15 12:29, nwpu053...@gmail.com wrote:
> > when i set the LANG to en_US.UTF-8, the `cygpath -D' could not display
> > the Chines character correctly.
> >
> > In other
Dave Korn wrote:
> I'd investigate phdl.
> Now is it just my imagination, or does Vista really insert an extra ULONG
> bitfield at offset 4 in the struct resulting in all subsequent members being
> offset by 4 relative to other versions of Windows? This needs verifying
> against the offici
Charles Wilson wrote:
> 43673 6:58:17.3634216 PM gpg-agent.exe 568 CreateFile
> C:\cygwin-1.7
> SUCCESS Desired Access: Execute/Traverse, Synchronize, Disposition:
> Open, Options: Directory, Synchronous IO Non-Alert, Attributes: n/a,
> ShareMode: Read, Write, Delete, Alloca
Charles Wilson wrote:
> So it looks to me like something in cwdstuff::init() triggered a signal,
> which was caught by cygwin and handled by aborting.
>
> Does that analysis look right?
It certainly does.
> [ ... ] appears that the child is dying in dcrt0.c dll_crt0_1() when it
> calls cygheap-
Dave Korn wrote:
> Charles Wilson wrote:
>> I'm not familiar at all with procmon (sysinternals, right?) but I'll
>> look into it.
>
> Yep, it's dead useful for making sure that stuff at least starts up, and you
> can often get a clue how far the code has got by seeing what handles it's
> opened
Dave Korn wrote:
> ... who leaves a copy in the -src tarball instead.
Oh, I didn't know that. Thanks, Dave.
I guess that kinda makes sense; you need the exact source for the .dbg
to work anyway. I'd been rolling my CVS dir back to the specified
version, and then using 'set substitute-path' to ma
Christopher Faylor wrote:
> On Thu, Oct 15, 2009 at 01:07:10PM -0400, Charles Wilson wrote:
> (hmm...why
>> aren't the cygwin1.dbg files available for the 1.7.0-nn releases? They
>> used to be shipped with 1.5.2x releases...)
>
> ...different person doing the release...
... who leaves a copy in
On Thu, Oct 15, 2009 at 01:07:10PM -0400, Charles Wilson wrote:
>Dave Korn wrote:
>> Charles Wilson wrote:
>>> the daemonized one. If I launch and then attach strace to
>>> the eventual pid of the daemonized process, it hangs (both strace and
>>> the process).
>>
>> How about "gdb --attach P
Charles Wilson wrote:
> Oh, CRAP.
>
> Wait.
>
> The libassuan test ALSO uses fork/exec. It is NOT trying to pass fds
> between completely unrelated processes. I bet if I get libassuan's test
> working, that will solve the gpg-agent problem too.
>
> Well, at least that makes the change/build/te
Dave Korn wrote:
> Charles Wilson wrote:
>> the daemonized one. If I launch and then attach strace to
>> the eventual pid of the daemonized process, it hangs (both strace and
>> the process).
>
> How about "gdb --attach PID"? Does that succeed? GDB has the advantage of
> being a Cygwin rat
On 15/10/2009 11:38, Dave Korn wrote:
Do you have a STC using just qmake itself so that I only have to build a
single package to try and track this down? e.g. does it fault just on
startup, can I just run "qmake --help" and reproduce the problem?
Yes, even qmake --help segfaults.
If you do
Charles Wilson wrote:
> the daemonized one. If I launch and then attach strace to
> the eventual pid of the daemonized process, it hangs (both strace and
> the process).
How about "gdb --attach PID"? Does that succeed? GDB has the advantage of
being a Cygwin rather than Win32 exe, which m
Yaakov (Cygwin/X) wrote:
> Ping?
Sorry, been terribly busy:
> On 06/10/2009 19:34, Yaakov (Cygwin/X) wrote:
>> On 05/10/2009 23:03, Yaakov (Cygwin/X) wrote:
>>> Just updated to cygwin-1.7.0-62 and gcc4-4.3.4-1 tonight, and it appears
>>> *anything* (sub-)dependent on libstdc++6 is segfaulting.
Ping?
On 06/10/2009 19:34, Yaakov (Cygwin/X) wrote:
On 05/10/2009 23:03, Yaakov (Cygwin/X) wrote:
Just updated to cygwin-1.7.0-62 and gcc4-4.3.4-1 tonight, and it appears
*anything* (sub-)dependent on libstdc++6 is segfaulting. Not just
MPlayer/FFmpeg (which dep libdirac, a C++ library), but an
Dave Korn wrote:
> Child gets started long enough to communicate with parent but then dies
> subsequently, still in early init, but late enough that the parent process
> create retries don't kick in. Don't hang about; get strace or procmon
> straight on the case with this, find out definitively
Charles Wilson wrote:
> Nothing. For all I can tell, the fork() fails to *actually* produce a
> child process -- even though the *parent* seems to think one has been
> created, and has a pid for the so-called child. Which doesn't actually
> exist.
>
> Can anybody think of a reason that might caus
I'm trying to track down a rather weird problem. I don't have an STC
because none of my attepted STCs exhibit the problem. Schematically, I
have:
=
pid_t pid = fork();
if (pid < 0) {
printf("fork failed\n");
exit (1);
}
if (pid > 0) {
/* parent
Hello
Could Cygwin be updated so that the PIF properties on C:\cygwin\Cygwin.bat
are set so as to allow QuickEdit? Currently for each install we need to
manually enable this default feature of CMD prompts on windows.
Workaround, edit per install:
1) right flick on "C>" icon select Properties
2) C
Is there a guide for setting up and maintaining cygwin in something bigger than
a personal machine?
I'm wondering if there are any howtos or guides that talks about building and
maintaining /etc/passwd and /etc/group, etc. on an ongoing basis, etc. in a
work group or even company wide setting.
2009/10/15 Markus Schaber:
>> % export LANG=C.UTF-8
>
> This was the solution - issuing that commando made it work.
>
> LANG=de.UTF-8 also seems to work.
>
> So I'll add this to my bashrc. Thanks a lot.
A better place for this is cygwin.bat for the console, or the Text
page of the options dialog f
Hi,
David Rothenberger wrote:
> % export LANG=C.UTF-8
This was the solution - issuing that commando made it work.
LANG=de.UTF-8 also seems to work.
So I'll add this to my bashrc. Thanks a lot.
Markus
**
Soloplan GmbH
So
On Oct 15 12:29, nwpu053...@gmail.com wrote:
> when i set the LANG to en_US.UTF-8, the `cygpath -D' could not display
> the Chines character correctly.
>
> In other environment, such as `ls' `vim', the the Chines character display
> well.
Thanks for the report. I think I see what's going on. I
25 matches
Mail list logo
