On 2011-12-06 PM 6:37, Corinna Vinschen wrote:
A lot of changes and fixes have been made in Cygwin since 1.7.9 has
been released, so we're looking forward to release Cygwin 1.7.10 soon.
Please test the latest developer snapshots at http://cygwin.com/snapshots/
which should have "Release Candidat
On Sun, 2011-03-13 at 05:48 -0700, spot135 wrote:
> command is ./testdata_qnforward.sh
I don't know why it's trying to invoke ${RUN}, because it's not being
set. Try removing it and having it run "./qnforward" (if that doesn't
work, find out where 'qnforward' is located and run that).
--
Bruce
Bruce Cran wrote:
>
> On Sat, 2011-03-12 at 12:56 -0800, spot135 wrote:
>
>> I'm hopping its something simply related to cygwin some how not passing
>> the
>> variables correctly, I'm really just after somebody pointing me in the
>> right
>> direction because I'm really quite stumped as to what
On Sat, 2011-03-12 at 12:56 -0800, spot135 wrote:
> I'm hopping its something simply related to cygwin some how not passing the
> variables correctly, I'm really just after somebody pointing me in the right
> direction because I'm really quite stumped as to what it could be...
The application tha
Hi,
I'm having problem getting a piece of software to function probably within
cygwin. The app in question is called quicknet and it is used for speech
analysis.
I'm currently trying to run the software with the testdata that was provide
with the package and I'm running into problem. I've inc
On Mon, 16 Dec 2002, Max Bowsher wrote:
> mohit batra wrote:
>
> > i am trying to run a c program in cygwin howevr when
> > i run the program the printf statements output is not
> > shown on screen .
> >
> > also i want to know what is the extension that must be
> > given to c++ file in order to
:
-
From: Max Bowsher [EMAIL PROTECTED]
Date: Mon, 16 Dec 2002 14:40:50 -
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: c problem
mohit batra <[EMAIL PROTECTED]> wrote:
> i am trying to run a c program in cygwin howevr when
> i run the program the printf statemen
mohit batra <[EMAIL PROTECTED]> wrote:
> i am trying to run a c program in cygwin howevr when
> i run the program the printf statements output is not
> shown on screen .
>
> also i want to know what is the extension that must be
> given to c++ file in order to compile with c++ .
> whwn i tried t
hi
i am trying to run a c program in cygwin howevr when
i run the program the printf statements output is not
shown on screen .
also i want to know what is the extension that must be
given to c++ file in order to compile with c++ .
whwn i tried to compile with C or c++ or .cpp
extensions it gav
Somehow, something I've done in my environment seems to cause a problem
with control-c handling.
A control-c gets sent to any sub-shells and right through 'ssh' -- very
annoying:
I tried the cygwin X server, but at the time it wanted to own the whole desktop and
didn't behave in a civilized mann
At 10:50 AM 1/12/2002 +1100, Robert Collins wrote:
>Have you tried the latest snapshot and confirmed that this still occurs?
Yes, this is with the latest snapshot. I actually haven't upgraded past
1.3.2 because the problems (like this) get worse from then on (using bash
as /bin/sh being the onl
- Original Message -
From: "Andy Piper" <[EMAIL PROTECTED]>
>
> Its a console app that happily responds to ^C. If you run it directly
from
> within bash then ^C works, so I assume from what you say above that
this is
> a bug of some description.
Have you tried the latest snapshot and conf
At 01:22 AM 1/12/2002 +1100, Robert Collins wrote:
>- Original Message -
>From: "Andy Piper" <[EMAIL PROTECTED]>
>
> > ash script pid reported by shell: 828
> > ash script pid in task manager: 856
> > java pid reported by ps 1640PPID 828
> > java pid repor
- Original Message -
From: "Andy Piper" <[EMAIL PROTECTED]>
> ash script pid reported by shell: 828
> ash script pid in task manager: 856
> java pid reported by ps 1640PPID 828
> java pid reported by task mnager1640
> bash pid
At 11:11 PM 1/11/2002 +1100, Robert Collins wrote:
>Start the ash script in the background, and then use ps. See if the java
>program appears in ps. If it does - check via task manager or process
>explorer to see if the reported cygwin pid is the same as the actual
>java.exe pid.
>
>If it doesn't
At 11:11 PM 1/11/2002 +1100, Robert Collins wrote:
>Can I suggest you start a new thread when the topic changes, it helps
>prevent confusion - particulary if the original thread hangs around.
Sorry. I thought the two might be related.
> > Interactive bash shell starts:
> > -> shell scri
- Original Message -
From: "Andy Piper" <[EMAIL PROTECTED]>
> Many thanks for looking at this. While the iron is hot - this problem
is
> still outstanding and I don't know whether you would expect this to be
> fixed also:
Can I suggest you start a new thread when the topic changes, it h
Chris Faylor wrote:
>There is a snapshot up there now which seems to work ok.
>
>Again, many thanks to Robert Collins for tracking this down.
>
>Although I said I wasn't overly interested in tracking this down
>myself, I was interested in seeing the lessening in email traffic that I
>hope this fi
On Thu, Jan 10, 2002 at 06:59:54PM +1100, Robert Collins wrote:
>> I was going back over this thread before checking in a change to see if
>> I'd missed something.
>>
>> I just realized that I didn't address this concern. Don't know if it
>> matters but...
>>
>> The difference between the SIG_IGN
===
- Original Message -
From: "Christopher Faylor" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, January 10, 2002 1:46 PM
Subject: Re: bash/cmd CTRL-C problem...
> On Wed, Jan 09, 2002 at 12:16:04PM +1100, Robert Collins wrote:
> >-
There is a snapshot up there now which seems to work ok.
Again, many thanks to Robert Collins for tracking this down.
Although I said I wasn't overly interested in tracking this down
myself, I was interested in seeing the lessening in email traffic that I
hope this fix engenders.
I do expect th
On Wed, Jan 09, 2002 at 12:16:04PM +1100, Robert Collins wrote:
>- Original Message -
>From: "Christopher Faylor" <[EMAIL PROTECTED]>
>>I'm specifically trying not to do the "TRUE" thing, though, since
>>AFAICT it isn't always appropriate.
>
>If you want to SIG_IGN the signal, then it is:
ns" <[EMAIL PROTECTED]>
> Sent: Wednesday, January 09, 2002 2:01 AM
> Subject: Re: bash/cmd CTRL-C problem...
>
>
> > The output is looking as if it is working correctly now. Great work
>
> >
> > If this is accepted which module needs to be updated ? I
Christopher Faylor wrote:
> For the record, I really appreciate your tracking this down. I finally
> understand the issues here. These issues have been around for a long time
> and the problems that you uncovered are probably responsible for some
> longstanding cygwin strangeness.
Ditto.
- Original Message -
From: "Christopher Faylor" <[EMAIL PROTECTED]>
> On Wed, Jan 09, 2002 at 11:57:04AM +1100, Robert Collins wrote:
> >- Original Message -
> >From: "Christopher Faylor" <[EMAIL PROTECTED]>
> >
> >> So, I think the easiest fix for the current problem is just to
On Wed, Jan 09, 2002 at 11:57:04AM +1100, Robert Collins wrote:
>- Original Message -
>From: "Christopher Faylor" <[EMAIL PROTECTED]>
>
>> So, I think the easiest fix for the current problem is just to do a
>> 'signal (SIGINT, SIG_IGN)' prior to calling CreateProcess, restoring
>> the prev
===
- Original Message -
From: "Christopher Faylor" <[EMAIL PROTECTED]>
> So, I think the easiest fix for the current problem is just to do a
> 'signal (SIGINT, SIG_IGN)' prior to calling CreateProcess, restoring
> the previous signal handler if the CreateProcess fails.
You do realise,
On Wed, Jan 09, 2002 at 11:43:41AM +1100, Robert Collins wrote:
>>I have to think about the race issues here. It seems like you can't
>>get away without some kind of additional communication between the
>>parent and the child.
>
>True. The problem is that we can't communicate with non-cygwin
>ch
- Original Message -
From: "Christopher Faylor" <[EMAIL PROTECTED]>
> >* The new process must not have signalled it's creation back to us.
>
> I don't think this is right, actually. You basically don't want the
stub
> to *ever* send a CTRL-C in your scenario. I don't see why it matters
t
On Wed, Jan 09, 2002 at 09:16:55AM +1100, Robert Collins wrote:
>- Original Message -
>From: "Christopher Faylor" <[EMAIL PROTECTED]>
>
>
>> On Tue, Jan 08, 2002 at 06:00:16PM +1100, Robert Collins wrote:
>> >FWIW this patch (Chris where should I put the in_stub declaration)
>>
>> There is
- Original Message -
From: "Christopher Faylor" <[EMAIL PROTECTED]>
> On Tue, Jan 08, 2002 at 06:00:16PM +1100, Robert Collins wrote:
> >FWIW this patch (Chris where should I put the in_stub declaration)
>
> There is already an indicator that an execed process is running --
> hExeced, so
On Tue, Jan 08, 2002 at 06:00:16PM +1100, Robert Collins wrote:
>FWIW this patch (Chris where should I put the in_stub declaration)
There is already an indicator that an execed process is running --
hExeced, so I don't think you need the 'in_stub' thing.
However, it seems to me that this solutio
FWIW this patch (Chris where should I put the in_stub declaration)
Index: exceptions.cc
===
RCS file: /cvs/src/src/winsup/cygwin/exceptions.cc,v
retrieving revision 1.103
diff -u -p -r1.103 exceptions.cc
--- exceptions.cc
===
- Original Message -
From: "Christopher Faylor" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, January 08, 2002 11:21 AM
Subject: Re: CGF: please review my logic Re: bash/cmd CTRL-C problem...
> On Tue, Jan 08, 2002 at 11:15:11AM +1
On Tue, Jan 08, 2002 at 11:15:11AM +1100, Robert Collins wrote:
>- Original Message -
>From: "Christopher Faylor" <[EMAIL PROTECTED]>
>> If you are looking for the "stub" code, it's in spawn_guts, around
>line
>> 1078 in the current sources.
>
>Line 1078 is the EOF for spawn.cc (current CV
- Original Message -
From: "Christopher Faylor" <[EMAIL PROTECTED]>
> If you are looking for the "stub" code, it's in spawn_guts, around
line
> 1078 in the current sources.
Line 1078 is the EOF for spawn.cc (current CVS). Is that correct?
> I'd suggest tracing what happens there.
Ys, in
On Tue, Jan 08, 2002 at 10:00:33AM +1100, Robert Collins wrote:
>- Original Message -
>From: "Christopher Faylor" <[EMAIL PROTECTED]>
>> >It succeeds! (I'm running a slightly modified cygwin here, which as
>the
>> >patch at the end of this email shows (in combination with the source
>:})
>
- Original Message -
From: "Christopher Faylor" <[EMAIL PROTECTED]>
> >It succeeds! (I'm running a slightly modified cygwin here, which as
the
> >patch at the end of this email shows (in combination with the source
:})
> >should always indicate if there is an error).
>
> It should always s
Christopher,
I addressed my message to you out of politeness since it was intended for you. I
addressed the message to cygwin since I thought it might also be of interest to the
readers of the mailing list. It's not an unusual convention to follow on mailing
lists, however, I won't do this with y
On Mon, Jan 07, 2002 at 12:30:33PM -0500, Gregory W. Bond wrote:
>(I just returned from vacation so excuse me for responding to an old
>message but I really feel compelled to respond to this one...)
Why did you Cc me when I specifically set the Reply-To to
[EMAIL PROTECTED] and am obviously readi
On Mon, Jan 07, 2002 at 12:08:51PM -0500, Gregory W. Bond wrote:
>I agree that this behavior should be considered a bug since the bash
>cygwin behavior differs from bash behavior on other unix platforms.
>This has caused headaches for our project too.
Hmm. How does bash on "other unix platforms"
(I just returned from vacation so excuse me for responding to an old
message but I really feel compelled to respond to this one...)
Christopher,
This reply puzzles me. What is the point of cygwin if not to support
interoperability between win32 and unix environments? If all I wanted
was an all-u
> For the record, here is a very simple java test program that I sent to
Troy when
> we discussed this problem last November. This program simply intercepts
CTL-C
> and runs a shutdown hook prior to shutting down the Java VM. It works fine
under
> cmd.exe and cygwin ash, but does not work under cy
te:
> >
> > > Hi Corinna,
> > >
> > > thanks for the answer. No I haven't tried such an option as I must admit
> > > that I don't know about it.
> > > I will search for it in the docs and try to play around with it...
> > >
> &g
On Tue, Jan 08, 2002 at 12:15:27AM +1100, Robert Collins wrote:
>Ok.
>I didn't realise that signal() is implemented in the standard VC++
>libraries.
>Can you tell me any details of the signal implementation you are using
>on win32?
>If you wished to follow clean room r/e for this, I can implement
>
> > Michael
> >
> >
> > On Fri, 2001-12-21 at 16:24, Corinna Vinschen wrote:
> > > On Fri, Dec 21, 2001 at 11:09:05AM +0100, Michael Rumpf wrote:
> > > > Am I the only one having problems with this, or is this simply the
wrong
> > > > list to ask a question about
hael Rumpf wrote:
> > > Am I the only one having problems with this, or is this simply the wrong
> > > list to ask a question about the Cygwin bash... ??
> >
> > Nah, this is the right list. Nobody has an answer, though.
> >
> > Did you try `CYGWIN=..
> Ok.
> I didn't realise that signal() is implemented in the standard VC++
> libraries.
> Can you tell me any details of the signal implementation you are using
> on win32?
> If you wished to follow clean room r/e for this, I can implement the
> signal sending side to match up with what your libra
Ok.
I didn't realise that signal() is implemented in the standard VC++
libraries.
Can you tell me any details of the signal implementation you are using
on win32?
If you wished to follow clean room r/e for this, I can implement the
signal sending side to match up with what your library expects.
A
> Yes, that is what I meant.
>
> > bash (cygwin, of course)
> > app1 = "signals (MS CRT)"
> > app2 = "myclass.exe (MS CRT)" or "java myclass (???)"
>
> Lets leave java to the side. If we solve it with MS CRT, and java apps
> still have problems, then that becomes a new bug. Why? because there are
- Original Message -
From: "Michael Rumpf" <[EMAIL PROTECTED]>
Yes, that is what I meant.
> bash (cygwin, of course)
> app1 = "signals (MS CRT)"
> app2 = "myclass.exe (MS CRT)" or "java myclass (???)"
Lets leave java to the side. If we solve it with MS CRT, and java apps
still have pr
Hi Robert,
> On Mon, 2002-01-07 at 19:47, Michael Rumpf wrote:
>
>
> > The problem is that the signal handling of the bash is not working
correctly
> > in the C/C++ app which forks others.
>
> I'm not clear: Is the app that forks others a Cygwin app, or not?
>
> ie: as a process chain is it
> bas
On Mon, 2002-01-07 at 19:47, Michael Rumpf wrote:
> The problem is that the signal handling of the bash is not working correctly
> in the C/C++ app which forks others.
I'm not clear: Is the app that forks others a Cygwin app, or not?
ie: as a process chain is it
bash (cygwin)
app1 (cygwin)
app
Hi Christopher,
> Here's the harsh reality: it is extremely unlikely that anyone is going
> to investigate this. If you are using non-cygwin apps with bash and
> CTRL-C doesn't work then you are on your own.
OK.
> I will enthusiastically inspect and evaluate any fixes that you provide
> to cyg
On Fri, Jan 04, 2002 at 12:52:43PM +0100, Michael Rumpf wrote:
>I further investigated the bash CTRL-C problem and found out that pressing
>CTRL-C in the bash is "nearly" the same as CTRL-BREAK. I tried all the
>CYGWIN=tty/notty/ combinations but that did not change anything.
Hi Corinna,
I further investigated the bash CTRL-C problem and found out that pressing
CTRL-C in the bash is "nearly" the same as CTRL-BREAK. I tried all the
CYGWIN=tty/notty/ combinations but that did not change anything...
Test application:
I have several sample applications, o
setting?
>
> Corinna
>
> >
> > Michael
> >
> > - Original Message -
> > From: "Michael Rumpf" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Thursday, December 20, 2001 10:11 AM
> > Subject: Re: bash/cmd CTR
27; setting?
Corinna
>
> Michael
>
> - Original Message -
> From: "Michael Rumpf" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, December 20, 2001 10:11 AM
> Subject: Re: bash/cmd CTRL-C problem...
>
>
> > Hi,
>
Subject: Re: bash/cmd CTRL-C problem...
> Hi,
>
> sorry for following up myself, but I found out that Cygwin equally handles
> CTRL-BREAK and CTRL-C by sending a SIGINT to the process.
> See http://groups.yahoo.com/group/gnu-win32/message/27643 (last sentence).
> This seems to be
2001 7:47 AM
Subject: bash/cmd CTRL-C problem...
> Hi,
>
> I'm new to the list and I don't know if this problem is already solved,
but
> I couldn't find a hint neither on the archives nor on the FAQ or somewhere
> else on the net.
>
> My problem is related to
Hi,
I'm new to the list and I don't know if this problem is already solved, but
I couldn't find a hint neither on the archives nor on the FAQ or somewhere
else on the net.
My problem is related to bash/cmd and signal handling.
In my app I installed a signal handler for SIGINT. The app is going i
61 matches
Mail list logo
