Christopher Faylor writes:
> I should have asked this before: I don't think anyone has made it
> clear if they are running the cygwin ping or the Windows one. I've
> been assuming Cygwin. Is that correct?
Cygwin's ping. I've removed any remnants of Windows' PATH from all
Cygwin startup scripts.
On Fri, Aug 17, 2012 at 03:50:05PM +, Adam Dinwoodie wrote:
>Christopher Faylor wrote
>> On Fri, Aug 17, 2012 at 09:07:30AM +, Adam Dinwoodie wrote:
>>> I'm still seeing exactly the same issue having taken the 20120816 snapshot.
>>> If anything, I've been hitting the problem more.
>>
>> I s
Christopher Faylor wrote
> On Fri, Aug 17, 2012 at 09:07:30AM +, Adam Dinwoodie wrote:
>> I'm still seeing exactly the same issue having taken the 20120816 snapshot.
>> If anything, I've been hitting the problem more.
>
> I should have asked this before: I don't think anyone has made it clear
On Fri, Aug 17, 2012 at 09:07:30AM +, Adam Dinwoodie wrote:
>Christopher Faylor wrote:
>> On Tue, Aug 14, 2012 at 12:48:03PM +, Adam Dinwoodie wrote:
>>> I'm still using this snapshot (I've had no reason to stop until now), and
>>> have hit this issue two out of the last five times running
Achim Gratz NexGo.DE> writes:
> This is still happening with the 2012-08-16 19:31:57 UTC snapshot.
And now I see that all that killing business has left some "tcsh" processes in
task manager with a size of 60k (much too small for both tcsh and ping) that ps
in Cygwin doesn't show. I could termi
Achim Gratz NexGo.DE> writes:
> With the latest snapshot (2012-08-07), pinging a dead machine (i.e. has a DNS
> entry but doesn't answer) from tcsh in mintty, I can't Ctrl-C ping and have to
> wait until it finally times out.
>
> # ping deadbeef
> PING deadbeef (xx.xx.xx.xx): 56 data bytes
This
Christopher Faylor wrote:
> On Tue, Aug 14, 2012 at 12:48:03PM +, Adam Dinwoodie wrote:
>> I'm still using this snapshot (I've had no reason to stop until now), and
>> have hit this issue two out of the last five times running Cygwin ping. The
>> ping process is still visible in Process Explor
On 8/16/2012 3:26 PM, Christopher Faylor wrote:
On Thu, Aug 16, 2012 at 03:11:34PM -0400, Ken Brown wrote:
With the current snapshot (20120816 17:19:27), I have problems with
emacs-X11.exe. When I start it under X (by typing 'emacs&' in an xterm
window), its CPU usage goes up to 50% and its win
On Thu, Aug 16, 2012 at 03:11:34PM -0400, Ken Brown wrote:
>With the current snapshot (20120816 17:19:27), I have problems with
>emacs-X11.exe. When I start it under X (by typing 'emacs&' in an xterm
>window), its CPU usage goes up to 50% and its window never displays.
>The attached file gives
On 8/16/2012 2:37 PM, Christopher Faylor wrote:
On Tue, Aug 14, 2012 at 12:48:03PM +, Adam Dinwoodie wrote:
Christopher Faylor wrote:
On Fri, Aug 10, 2012 at 06:31:25AM +, Achim Gratz wrote:
Daniel Colascione writes:
It works for me in bash. I don't have tcsh installed, but I don't s
On Tue, Aug 14, 2012 at 12:48:03PM +, Adam Dinwoodie wrote:
>Christopher Faylor wrote:
>>On Fri, Aug 10, 2012 at 06:31:25AM +, Achim Gratz wrote:
>>>Daniel Colascione writes:
It works for me in bash. I don't have tcsh installed, but I don't see why
SIGINT would work differently the
On Tue, Aug 14, 2012 at 09:39:14PM +0200, Corinna Vinschen wrote:
>On Aug 15 02:59, jojelino wrote:
>> Hi, I think i found a glitch in gmon.c
>>
>> the testcase is following. and you can see it doesn't work.
>>
>> int main()
>> {
>> char *proffile;
>> {
>> char gmon_out[
On Aug 15 02:59, jojelino wrote:
> Hi, I think i found a glitch in gmon.c
>
> the testcase is following. and you can see it doesn't work.
>
> int main()
> {
> char *proffile;
> {
> char gmon_out[] = "gmon.out";
> proffile = gmon_out;
> }
> print
Hi, I think i found a glitch in gmon.c
the testcase is following. and you can see it doesn't work.
int main()
{
char *proffile;
{
char gmon_out[] = "gmon.out";
proffile = gmon_out;
}
printf("%s\n",proffile);
}
---
$ ./a
a(▒"
Actually the a
On Fri, Aug 10, 2012 at 10:23:41PM +0200, Achim Gratz wrote:
>Christopher Faylor writes:
>>>I killed make because I forgot to add a variable definition on the
>>>command line. Only later did I find it left that zombie git process
>>>that should have been terminated with it (I know it was associate
Christopher Faylor writes:
>>I killed make because I forgot to add a variable definition on the
>>command line. Only later did I find it left that zombie git process
>>that should have been terminated with it (I know it was associated with
>>that particular make invocation by its start time).
>
>
On Fri, Aug 10, 2012 at 08:33:36PM +0200, Achim Gratz wrote:
>Christopher Faylor writes:
>> ...and those are the kind of details which allows us to at least make
>> educated guesses about problems. Showing a "defunct" ps listing, not so
>> much...
>
>You know this, but a defunct listing means that
Christopher Faylor writes:
> ...and those are the kind of details which allows us to at least make
> educated guesses about problems. Showing a "defunct" ps listing, not so
> much...
You know this, but a defunct listing means that a process terminated,
but wasn't reaped by it's parent process. U
On Fri, Aug 10, 2012 at 07:57:24PM +0200, Achim Gratz wrote:
>Christopher Faylor writes:
>> You're not really giving us much to go on.
>
>I don't have anything else, these are the only two (small) issues I've
>seen after installation of the latest snapshot.
>
>> A process doesn't mean that somethi
Christopher Faylor writes:
> You're not really giving us much to go on.
I don't have anything else, these are the only two (small) issues I've
seen after installation of the latest snapshot.
> A process doesn't mean that something is not properly
> terminated. Is this also a tcsh shell running
On Fri, Aug 10, 2012 at 06:31:25AM +, Achim Gratz wrote:
>Daniel Colascione writes:
>>It works for me in bash. I don't have tcsh installed, but I don't see
>>why SIGINT would work differently there.
>
>Yes, it works in bash for me, too. Tcsh does something that apparently
>breaks with the new
Daniel Colascione dancol.org> writes:
> It works for me in bash. I don't have tcsh installed, but I don't see
> why SIGINT would work differently there.
Yes, it works in bash for me, too. Tcsh does something that apparently breaks
with the new snapshot, but since I don't get any error messages,
Christopher Faylor writes:
>>deadbeef PING Statistics
>>2 packets transmitted, 0 packets received, 100.0% packet loss
>
> Ping doesn't time out after only two packets. It sure looks like CTRL-C
> worked
> above.
Maybe ping got indeed interrupted, but I didn't get the shell prompt
back fo
On 8/9/12 2:21 AM, Achim Gratz wrote:
> Christopher Faylor cygwin.com> writes:
>> You mention generic "signal handling" rather than "sigwaitinfo" so I don't
>> know if there are other issues. It doesn't seem like much would work if
>> signal handling was completely broken, though.
>
> With the l
On Thu, Aug 09, 2012 at 09:21:47AM +, Achim Gratz wrote:
>Christopher Faylor cygwin.com> writes:
>> You mention generic "signal handling" rather than "sigwaitinfo" so I don't
>> know if there are other issues. It doesn't seem like much would work if
>> signal handling was completely broken, t
Christopher Faylor cygwin.com> writes:
> You mention generic "signal handling" rather than "sigwaitinfo" so I don't
> know if there are other issues. It doesn't seem like much would work if
> signal handling was completely broken, though.
With the latest snapshot (2012-08-07), pinging a dead mac
Achim Gratz NexGo.DE> writes:
> The X server is still running as well as a number of other X applications.
Something's wrong here with the new snapshot and signal handling / job control
in conjunction with X and the newest snapshot... this morning the shell
proclaimed (I left it running overnight
On 8/8/2012 2:59 PM, Christopher Faylor wrote:
> On Mon, Aug 06, 2012 at 05:15:10PM -0700, Daniel Colascione wrote:
>> On 8/6/2012 2:07 PM, Daniel Colascione wrote:
>>> I just saw a hang building Emacs (using "make bootstrap")
>>
>> Signal handling appears to be broken. Here's a simple testcase. Ru
On Mon, Aug 06, 2012 at 05:15:10PM -0700, Daniel Colascione wrote:
>On 8/6/2012 2:07 PM, Daniel Colascione wrote:
>> I just saw a hang building Emacs (using "make bootstrap")
>
>Signal handling appears to be broken. Here's a simple testcase. Run the program
>and hit control-c. It'll print "got Alar
I'm at the August 7th snapshot now and Emacs just died on me with this message:
> Connection lost to X server `:0.0'
When compiled with GTK, Emacs cannot recover from X disconnects.
This is a GTK bug: https://bugzilla.gnome.org/show_bug.cgi?id=85715
For details, see etc/PROBLEMS.
The X server is
On 8/6/2012 5:15 PM, Daniel Colascione wrote:
> On 8/6/2012 2:07 PM, Daniel Colascione wrote:
>> I just saw a hang building Emacs (using "make bootstrap")
>
> Signal handling appears to be broken. Here's a simple testcase. Run the
> program
> and hit control-c. It'll print "got Alarm clock", then
On 8/6/2012 2:07 PM, Daniel Colascione wrote:
> I just saw a hang building Emacs (using "make bootstrap")
Signal handling appears to be broken. Here's a simple testcase. Run the program
and hit control-c. It'll print "got Alarm clock", then stop accepting any
signals at all, even SIGSTOP. The same
On 8/6/2012 7:37 AM, Filipp Gunbin wrote:
> Christopher Faylor writes:
>
>> We're considering rolling a new release which fixes some of the problems
>> which have cropped up here in the last few weeks.
>>
>> So, if you haven't already, we'd appreciate having people try out the
>> latest snapshot a
Christopher Faylor writes:
> We're considering rolling a new release which fixes some of the problems
> which have cropped up here in the last few weeks.
>
> So, if you haven't already, we'd appreciate having people try out the
> latest snapshot at: http://cygwin.com/snapshots/ .
>
> cgf
Seems ok
Christopher Faylor cygwin.com> writes:
> So, if you haven't already, we'd appreciate having people try out the
> latest snapshot at: http://cygwin.com/snapshots/ .
The August 3rd snapshot looks good so far in my testing.
Regards,
Achim.
--
Problem reports: http://cygwin.com/problems.h
On 8/5/12 8:34 PM, Christopher Faylor wrote:
> We're considering rolling a new release which fixes some of the problems
> which have cropped up here in the last few weeks.
>
> So, if you haven't already, we'd appreciate having people try out the
> latest snapshot at: http://cygwin.com/snapshots/ .
We're considering rolling a new release which fixes some of the problems
which have cropped up here in the last few weeks.
So, if you haven't already, we'd appreciate having people try out the
latest snapshot at: http://cygwin.com/snapshots/ .
cgf
--
Problem reports: http://cygwin.com/prob
On Fri, Feb 24, 2006 at 06:59:50AM -0700, Eric Blake wrote:
>According to Christopher Faylor on 2/21/2006 6:06 PM:
>>Please observe usual bug reporting rules when reporting on any results
>>from testing a snapshot.
>
>I'm seeing a few regressions on Win98 with 20060220, 20060223. They
>are making
Eric Blake byu.net> writes:
> In an effort to help the testing be easier to perform, I will soon be
releasing
> an experimental coreutils-5.94-2 that uses the d_ino member in ls and also
> in /bin/pwd
Now released, but it pointed out an upstream bug in coreutils - 'ls -i'
currently stubbornly
Christopher Faylor cygwin.com> writes:
>
> Specifically, what needs testing is Corinna's new code which properly
> fills in d_ino into a dirent struct. I recently found that a samba bug
> caused strange behavior when performing an "ls" or a "find" in a
> directory on a samba share which had mor
We're close to making a new cygwin release but the snapshot needs some
testing.
Specifically, what needs testing is Corinna's new code which properly
fills in d_ino into a dirent struct. I recently found that a samba bug
caused strange behavior when performing an "ls" or a "find" in a
directory o
41 matches
Mail list logo
