realbasic-nug
[Top] [All Lists]

Re: OS X 10.6.2 causes hangs in Shell set to Mode 2

To: REALbasic NUG <realbasic-nug@lists.realsoftware.com>
Subject: Re: OS X 10.6.2 causes hangs in Shell set to Mode 2
From: Charles Yeomans <charles@declareSub.com>
Date: Wed, 11 Nov 2009 14:18:39 -0500
Authentication-results: mx.google.com; spf=neutral (google.com: 74.124.194.228 is neither permitted nor denied by best guess record for domain of realbasic-nug-bounces@lists.realsoftware.com) smtp.mail=realbasic-nug-bounces@lists.realsoftware.com
Delivered-to: listarchive@realsoftware.com
In-reply-to: <4AFB0463.3050402@inspiringapps.com>
References: <fed2e2560911110736i21a90cadp33b3a024b01691e9@mail.gmail.com> <24D87E7B-13C2-465E-9BDA-86CCC790CED6@bainsware.com> <4AFB0463.3050402@inspiringapps.com>
Reply-to: REALbasic NUG <realbasic-nug@lists.realsoftware.com>
Sender: realbasic-nug-bounces@lists.realsoftware.com

On Nov 11, 2009, at 1:37 PM, Joe Strout wrote:

Navdeep Bains wrote:

I'm glad I'm not the only seeing this issue. The hang is on the Shell.Close call, which in turn calls the POSIX "close" function. Mode 1 Shells exhibit the same behavior.
I haven't been able to find any workarounds.

The workaround in some cases is to not call Shell.Close while the shell is running -- you can just tell the command you're running to exit (or otherwise wait for it to terminate) instead.

But of course this may be difficult in some apps, depending on what you're doing.



We worked around this problem by adding a Kill method to the Shell class. You can use a second shell to run kill, or declare and call the corresponding C function to send a signal to the target process.

Charles Yeomans

_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>


<Prev in Thread] Current Thread [Next in Thread>