Issues calling mtasc/swfmill as external processes

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

Issues calling mtasc/swfmill as external processes

Juan Delgado
Hi there,

I'm developing an internal build tool that needs to make calls to both
swfmill and mtasc. This is what I'm using:

var p = new Process(path, [args]);
var exitcode = p.exitCode();
var error = p.stderr.readAll().toString();
var output = p.stdout.readAll().toString();
p.close();

But for some reason trying to catch the exit code hangs the app. I
know calling exitCode() blocks the flow and I'm ok with that, the
problem is that the app never comes back, keeps waiting forever.

I know the calls to both mtasc and swfmill are ok, cause if i run them
by hand on the console they work as expected, and returning 0 as exit
code.

Any ideas what could  be going on?

I'm running haxe 2.0.5 and neko 1.8.1 on Leopard. I'm also using
xcross to generate a self-contained executable, but I get the same
result when running neko builder.n.

Thanks,

Juan

ps; should i ask this on the neko list better?

--
Juan Delgado - Zárate
http://zarate.tv
http://blog.zarate.tv

--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Issues calling mtasc/swfmill as external processes

Juan Delgado
More stuff related to processes.

I'm implementing in XAPI xa.Folder.forceDelte() which in mac/linux
uses rm -rf path and in windows should use RMDIR path /s /q.

For some reason when I try this:

var p = new Process('RMDIR', [path, '/s', '/q']);

I get an exception: "Process creation failure". I've searched the
list, but what I've found doesn't seem related to my problem. I can
run the exact same command from the command line and works as
expected, so no admin rights or anything similar involved.

I've tried case sensitivity, a dozen other parameter orders, even
different commands such as "del". Still not working.

Funny thing is that other commands such as attrib or dir work as expected.

Any idea why RMDIR looks like a special case?

Thanks,

J

ps: btw, this is the last thing I change before releasing XAPI 0.1.
You can check out the actual classes here:

http://github.com/zarate/xapi/tree/master/src/xa/

There's in-line docs as well and will be released through haxelib. I'm
only missing this Folder.forceDelete() for Windows :/

On Fri, Feb 12, 2010 at 10:38 AM, Juan Delgado <[hidden email]> wrote:

> Hi there,
>
> I'm developing an internal build tool that needs to make calls to both
> swfmill and mtasc. This is what I'm using:
>
> var p = new Process(path, [args]);
> var exitcode = p.exitCode();
> var error = p.stderr.readAll().toString();
> var output = p.stdout.readAll().toString();
> p.close();
>
> But for some reason trying to catch the exit code hangs the app. I
> know calling exitCode() blocks the flow and I'm ok with that, the
> problem is that the app never comes back, keeps waiting forever.
>
> I know the calls to both mtasc and swfmill are ok, cause if i run them
> by hand on the console they work as expected, and returning 0 as exit
> code.
>
> Any ideas what could  be going on?
>
> I'm running haxe 2.0.5 and neko 1.8.1 on Leopard. I'm also using
> xcross to generate a self-contained executable, but I get the same
> result when running neko builder.n.
>
> Thanks,
>
> Juan
>
> ps; should i ask this on the neko list better?
>
> --
> Juan Delgado - Zárate
> http://zarate.tv
> http://blog.zarate.tv
>



--
Juan Delgado - Zárate
http://zarate.tv
http://blog.zarate.tv

--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Issues calling mtasc/swfmill as external processes

Simon Richardson
sandboxed shell, from with in process ?

si

On 12 Feb 2010, at 16:07, Juan Delgado wrote:

> More stuff related to processes.
>
> I'm implementing in XAPI xa.Folder.forceDelte() which in mac/linux
> uses rm -rf path and in windows should use RMDIR path /s /q.
>
> For some reason when I try this:
>
> var p = new Process('RMDIR', [path, '/s', '/q']);
>
> I get an exception: "Process creation failure". I've searched the
> list, but what I've found doesn't seem related to my problem. I can
> run the exact same command from the command line and works as
> expected, so no admin rights or anything similar involved.
>
> I've tried case sensitivity, a dozen other parameter orders, even
> different commands such as "del". Still not working.
>
> Funny thing is that other commands such as attrib or dir work as expected.
>
> Any idea why RMDIR looks like a special case?
>
> Thanks,
>
> J
>
> ps: btw, this is the last thing I change before releasing XAPI 0.1.
> You can check out the actual classes here:
>
> http://github.com/zarate/xapi/tree/master/src/xa/
>
> There's in-line docs as well and will be released through haxelib. I'm
> only missing this Folder.forceDelete() for Windows :/
>
> On Fri, Feb 12, 2010 at 10:38 AM, Juan Delgado <[hidden email]> wrote:
>> Hi there,
>>
>> I'm developing an internal build tool that needs to make calls to both
>> swfmill and mtasc. This is what I'm using:
>>
>> var p = new Process(path, [args]);
>> var exitcode = p.exitCode();
>> var error = p.stderr.readAll().toString();
>> var output = p.stdout.readAll().toString();
>> p.close();
>>
>> But for some reason trying to catch the exit code hangs the app. I
>> know calling exitCode() blocks the flow and I'm ok with that, the
>> problem is that the app never comes back, keeps waiting forever.
>>
>> I know the calls to both mtasc and swfmill are ok, cause if i run them
>> by hand on the console they work as expected, and returning 0 as exit
>> code.
>>
>> Any ideas what could  be going on?
>>
>> I'm running haxe 2.0.5 and neko 1.8.1 on Leopard. I'm also using
>> xcross to generate a self-contained executable, but I get the same
>> result when running neko builder.n.
>>
>> Thanks,
>>
>> Juan
>>
>> ps; should i ask this on the neko list better?
>>
>> --
>> Juan Delgado - Zárate
>> http://zarate.tv
>> http://blog.zarate.tv
>>
>
>
>
> --
> Juan Delgado - Zárate
> http://zarate.tv
> http://blog.zarate.tv
>
> --
> haXe - an open source web programming language
> http://haxe.org


--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Issues calling mtasc/swfmill as external processes

Juan Delgado
Just got around the problem calling RMDIR. I'm calling
neko.Sys.command('RMDIR', [path, '/s', 'q']) instead.

Still have issues calling mtasc and swfmill, though.

J

On Fri, Feb 12, 2010 at 4:49 PM, Simon Richardson <[hidden email]> wrote:

> sandboxed shell, from with in process ?
>
> si
>
> On 12 Feb 2010, at 16:07, Juan Delgado wrote:
>
>> More stuff related to processes.
>>
>> I'm implementing in XAPI xa.Folder.forceDelte() which in mac/linux
>> uses rm -rf path and in windows should use RMDIR path /s /q.
>>
>> For some reason when I try this:
>>
>> var p = new Process('RMDIR', [path, '/s', '/q']);
>>
>> I get an exception: "Process creation failure". I've searched the
>> list, but what I've found doesn't seem related to my problem. I can
>> run the exact same command from the command line and works as
>> expected, so no admin rights or anything similar involved.
>>
>> I've tried case sensitivity, a dozen other parameter orders, even
>> different commands such as "del". Still not working.
>>
>> Funny thing is that other commands such as attrib or dir work as expected.
>>
>> Any idea why RMDIR looks like a special case?
>>
>> Thanks,
>>
>> J
>>
>> ps: btw, this is the last thing I change before releasing XAPI 0.1.
>> You can check out the actual classes here:
>>
>> http://github.com/zarate/xapi/tree/master/src/xa/
>>
>> There's in-line docs as well and will be released through haxelib. I'm
>> only missing this Folder.forceDelete() for Windows :/
>>
>> On Fri, Feb 12, 2010 at 10:38 AM, Juan Delgado <[hidden email]> wrote:
>>> Hi there,
>>>
>>> I'm developing an internal build tool that needs to make calls to both
>>> swfmill and mtasc. This is what I'm using:
>>>
>>> var p = new Process(path, [args]);
>>> var exitcode = p.exitCode();
>>> var error = p.stderr.readAll().toString();
>>> var output = p.stdout.readAll().toString();
>>> p.close();
>>>
>>> But for some reason trying to catch the exit code hangs the app. I
>>> know calling exitCode() blocks the flow and I'm ok with that, the
>>> problem is that the app never comes back, keeps waiting forever.
>>>
>>> I know the calls to both mtasc and swfmill are ok, cause if i run them
>>> by hand on the console they work as expected, and returning 0 as exit
>>> code.
>>>
>>> Any ideas what could  be going on?
>>>
>>> I'm running haxe 2.0.5 and neko 1.8.1 on Leopard. I'm also using
>>> xcross to generate a self-contained executable, but I get the same
>>> result when running neko builder.n.
>>>
>>> Thanks,
>>>
>>> Juan
>>>
>>> ps; should i ask this on the neko list better?
>>>
>>> --
>>> Juan Delgado - Zárate
>>> http://zarate.tv
>>> http://blog.zarate.tv
>>>
>>
>>
>>
>> --
>> Juan Delgado - Zárate
>> http://zarate.tv
>> http://blog.zarate.tv
>>
>> --
>> haXe - an open source web programming language
>> http://haxe.org
>
>
> --
> haXe - an open source web programming language
> http://haxe.org
>



--
Juan Delgado - Zárate
http://zarate.tv
http://blog.zarate.tv

--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Issues calling mtasc/swfmill as external processes

Juan Delgado
Hi there,

Regarding the original problem of this post (some processes hanging
forever), I've found what the problem was.

We are calling mtasc in verbose mode to automatically generate exclude
files parsing the output. Since it was parsing a fair amount of
classes, reading stdout in one go was just not working. Something like
this:

p = new Process(mtasc, [args]);

o = p.stdout.readAll().toString();

I've changed that to something like this:

o = '';
while(true)
{
   try{ o += p.stdout.readLine() + '\n'; } catch (e){ break; }
}

which seems to be working fine. And here comes the question.

Is there any scenario where you would NOT want to read stdout or
stderr line by line instead of in one go? I know you might need to
readBytes, but if you are going for the whole thing, it seems more
sensible reading line by line in case a big stream comes back. Any
downsides?

Also, what's the recommended way of reading stdout, stderr and exit code?

a) Create process + wait for exit code + read error and output
b) Create process + read error and output + wait for exit code

Is this something that can/should be done always in the same order?
(assuming you don't mind waiting for the process to end).

Thanks,

Juan

On Sat, Feb 13, 2010 at 3:24 PM, Juan Delgado <[hidden email]> wrote:

> Just got around the problem calling RMDIR. I'm calling
> neko.Sys.command('RMDIR', [path, '/s', 'q']) instead.
>
> Still have issues calling mtasc and swfmill, though.
>
> J
>
> On Fri, Feb 12, 2010 at 4:49 PM, Simon Richardson <[hidden email]> wrote:
>> sandboxed shell, from with in process ?
>>
>> si
>>
>> On 12 Feb 2010, at 16:07, Juan Delgado wrote:
>>
>>> More stuff related to processes.
>>>
>>> I'm implementing in XAPI xa.Folder.forceDelte() which in mac/linux
>>> uses rm -rf path and in windows should use RMDIR path /s /q.
>>>
>>> For some reason when I try this:
>>>
>>> var p = new Process('RMDIR', [path, '/s', '/q']);
>>>
>>> I get an exception: "Process creation failure". I've searched the
>>> list, but what I've found doesn't seem related to my problem. I can
>>> run the exact same command from the command line and works as
>>> expected, so no admin rights or anything similar involved.
>>>
>>> I've tried case sensitivity, a dozen other parameter orders, even
>>> different commands such as "del". Still not working.
>>>
>>> Funny thing is that other commands such as attrib or dir work as expected.
>>>
>>> Any idea why RMDIR looks like a special case?
>>>
>>> Thanks,
>>>
>>> J
>>>
>>> ps: btw, this is the last thing I change before releasing XAPI 0.1.
>>> You can check out the actual classes here:
>>>
>>> http://github.com/zarate/xapi/tree/master/src/xa/
>>>
>>> There's in-line docs as well and will be released through haxelib. I'm
>>> only missing this Folder.forceDelete() for Windows :/
>>>
>>> On Fri, Feb 12, 2010 at 10:38 AM, Juan Delgado <[hidden email]> wrote:
>>>> Hi there,
>>>>
>>>> I'm developing an internal build tool that needs to make calls to both
>>>> swfmill and mtasc. This is what I'm using:
>>>>
>>>> var p = new Process(path, [args]);
>>>> var exitcode = p.exitCode();
>>>> var error = p.stderr.readAll().toString();
>>>> var output = p.stdout.readAll().toString();
>>>> p.close();
>>>>
>>>> But for some reason trying to catch the exit code hangs the app. I
>>>> know calling exitCode() blocks the flow and I'm ok with that, the
>>>> problem is that the app never comes back, keeps waiting forever.
>>>>
>>>> I know the calls to both mtasc and swfmill are ok, cause if i run them
>>>> by hand on the console they work as expected, and returning 0 as exit
>>>> code.
>>>>
>>>> Any ideas what could  be going on?
>>>>
>>>> I'm running haxe 2.0.5 and neko 1.8.1 on Leopard. I'm also using
>>>> xcross to generate a self-contained executable, but I get the same
>>>> result when running neko builder.n.
>>>>
>>>> Thanks,
>>>>
>>>> Juan
>>>>
>>>> ps; should i ask this on the neko list better?
>>>>
>>>> --
>>>> Juan Delgado - Zárate
>>>> http://zarate.tv
>>>> http://blog.zarate.tv
>>>>
>>>
>>>
>>>
>>> --
>>> Juan Delgado - Zárate
>>> http://zarate.tv
>>> http://blog.zarate.tv
>>>
>>> --
>>> haXe - an open source web programming language
>>> http://haxe.org
>>
>>
>> --
>> haXe - an open source web programming language
>> http://haxe.org
>>
>
>
>
> --
> Juan Delgado - Zárate
> http://zarate.tv
> http://blog.zarate.tv
>



--
Juan Delgado - Zárate
http://zarate.tv
http://blog.zarate.tv

--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Issues calling mtasc/swfmill as external processes

Benjamin Dasnois
In reply to this post by Juan Delgado
Hi,

By the way Juan, I would avoid using a command to delete a directory.
Spawning another process just for that seems a bit overkill to me.
There must be another and better way to do that. Also, you're
supposing that the user will have these programs installed which is
really not mandatory (there are quite a lot of linux distro that uses
shells with builtins instead of providing all those commands as
standalone executables.)

Regards,

Benjamin Dasnois

On 2/12/10, Juan Delgado <[hidden email]> wrote:

> More stuff related to processes.
>
> I'm implementing in XAPI xa.Folder.forceDelte() which in mac/linux
> uses rm -rf path and in windows should use RMDIR path /s /q.
>
> For some reason when I try this:
>
> var p = new Process('RMDIR', [path, '/s', '/q']);
>
> I get an exception: "Process creation failure". I've searched the
> list, but what I've found doesn't seem related to my problem. I can
> run the exact same command from the command line and works as
> expected, so no admin rights or anything similar involved.
>
> I've tried case sensitivity, a dozen other parameter orders, even
> different commands such as "del". Still not working.
>
> Funny thing is that other commands such as attrib or dir work as expected.
>
> Any idea why RMDIR looks like a special case?
>
> Thanks,
>
> J
>
> ps: btw, this is the last thing I change before releasing XAPI 0.1.
> You can check out the actual classes here:
>
> http://github.com/zarate/xapi/tree/master/src/xa/
>
> There's in-line docs as well and will be released through haxelib. I'm
> only missing this Folder.forceDelete() for Windows :/
>
> On Fri, Feb 12, 2010 at 10:38 AM, Juan Delgado <[hidden email]> wrote:
>> Hi there,
>>
>> I'm developing an internal build tool that needs to make calls to both
>> swfmill and mtasc. This is what I'm using:
>>
>> var p = new Process(path, [args]);
>> var exitcode = p.exitCode();
>> var error = p.stderr.readAll().toString();
>> var output = p.stdout.readAll().toString();
>> p.close();
>>
>> But for some reason trying to catch the exit code hangs the app. I
>> know calling exitCode() blocks the flow and I'm ok with that, the
>> problem is that the app never comes back, keeps waiting forever.
>>
>> I know the calls to both mtasc and swfmill are ok, cause if i run them
>> by hand on the console they work as expected, and returning 0 as exit
>> code.
>>
>> Any ideas what could  be going on?
>>
>> I'm running haxe 2.0.5 and neko 1.8.1 on Leopard. I'm also using
>> xcross to generate a self-contained executable, but I get the same
>> result when running neko builder.n.
>>
>> Thanks,
>>
>> Juan
>>
>> ps; should i ask this on the neko list better?
>>
>> --
>> Juan Delgado - Zárate
>> http://zarate.tv
>> http://blog.zarate.tv
>>
>
>
>
> --
> Juan Delgado - Zárate
> http://zarate.tv
> http://blog.zarate.tv
>
> --
> haXe - an open source web programming language
> http://haxe.org
>


--
DASNOIS Benjamin
http://www.benjamindasnois.com

--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Issues calling mtasc/swfmill as external processes

Juan Delgado
Hi there,

I would have thought that "rm" would be pretty standard across linux
distros... is it really not the case? Or you mean that it might not be
available as an actual executable? RMDIR seems pretty standard across
Windows versions as well.

Anyway, if we decide is not safe to go rm/rmdir, I could always read
the folder and remove all files one by one, then call standard folder
delete. Sounds like safe, but extremely slow.

Any tricks or bits of the official API I might have missed and that
could help? Case in point, Found only 2 days ago about
neko.io.File.getContent() even though I've spent quite a few hours
browsing the std API. Shame on me :/

J

On Thu, Feb 18, 2010 at 10:43 AM, Benjamin Dasnois
<[hidden email]> wrote:

> Hi,
>
> By the way Juan, I would avoid using a command to delete a directory.
> Spawning another process just for that seems a bit overkill to me.
> There must be another and better way to do that. Also, you're
> supposing that the user will have these programs installed which is
> really not mandatory (there are quite a lot of linux distro that uses
> shells with builtins instead of providing all those commands as
> standalone executables.)
>
> Regards,
>
> Benjamin Dasnois
>
> On 2/12/10, Juan Delgado <[hidden email]> wrote:
>> More stuff related to processes.
>>
>> I'm implementing in XAPI xa.Folder.forceDelte() which in mac/linux
>> uses rm -rf path and in windows should use RMDIR path /s /q.
>>
>> For some reason when I try this:
>>
>> var p = new Process('RMDIR', [path, '/s', '/q']);
>>
>> I get an exception: "Process creation failure". I've searched the
>> list, but what I've found doesn't seem related to my problem. I can
>> run the exact same command from the command line and works as
>> expected, so no admin rights or anything similar involved.
>>
>> I've tried case sensitivity, a dozen other parameter orders, even
>> different commands such as "del". Still not working.
>>
>> Funny thing is that other commands such as attrib or dir work as expected.
>>
>> Any idea why RMDIR looks like a special case?
>>
>> Thanks,
>>
>> J
>>
>> ps: btw, this is the last thing I change before releasing XAPI 0.1.
>> You can check out the actual classes here:
>>
>> http://github.com/zarate/xapi/tree/master/src/xa/
>>
>> There's in-line docs as well and will be released through haxelib. I'm
>> only missing this Folder.forceDelete() for Windows :/
>>
>> On Fri, Feb 12, 2010 at 10:38 AM, Juan Delgado <[hidden email]> wrote:
>>> Hi there,
>>>
>>> I'm developing an internal build tool that needs to make calls to both
>>> swfmill and mtasc. This is what I'm using:
>>>
>>> var p = new Process(path, [args]);
>>> var exitcode = p.exitCode();
>>> var error = p.stderr.readAll().toString();
>>> var output = p.stdout.readAll().toString();
>>> p.close();
>>>
>>> But for some reason trying to catch the exit code hangs the app. I
>>> know calling exitCode() blocks the flow and I'm ok with that, the
>>> problem is that the app never comes back, keeps waiting forever.
>>>
>>> I know the calls to both mtasc and swfmill are ok, cause if i run them
>>> by hand on the console they work as expected, and returning 0 as exit
>>> code.
>>>
>>> Any ideas what could  be going on?
>>>
>>> I'm running haxe 2.0.5 and neko 1.8.1 on Leopard. I'm also using
>>> xcross to generate a self-contained executable, but I get the same
>>> result when running neko builder.n.
>>>
>>> Thanks,
>>>
>>> Juan
>>>
>>> ps; should i ask this on the neko list better?
>>>
>>> --
>>> Juan Delgado - Zárate
>>> http://zarate.tv
>>> http://blog.zarate.tv
>>>
>>
>>
>>
>> --
>> Juan Delgado - Zárate
>> http://zarate.tv
>> http://blog.zarate.tv
>>
>> --
>> haXe - an open source web programming language
>> http://haxe.org
>>
>
>
> --
> DASNOIS Benjamin
> http://www.benjamindasnois.com
>
> --
> haXe - an open source web programming language
> http://haxe.org
>



--
Juan Delgado - Zárate
http://zarate.tv
http://blog.zarate.tv

--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Issues calling mtasc/swfmill as external processes

Niel Drummond-3
In reply to this post by Juan Delgado
Juan Delgado wrote:
> [snip]
> Is there any scenario where you would NOT want to read stdout or
> stderr line by line instead of in one go? I know you might need to
> readBytes, but if you are going for the whole thing, it seems more
> sensible reading line by line in case a big stream comes back. Any
> downsides?
>  
not really, though if you are not writing a monitoring application (for
example cron jobs) it does not make sense to have verbose output, and
readAll should be able to cope.
> Also, what's the recommended way of reading stdout, stderr and exit code?
>
> a) Create process + wait for exit code + read error and output
> b) Create process + read error and output + wait for exit code
>
> Is this something that can/should be done always in the same order?
> (assuming you don't mind waiting for the process to end).
>  

applications can write to stderr or stdout without exiting at all, so in
principle if you are capturing output you should implement the latter.
If you are writing a generic API then I would vouch for the former,
because it may be unnecessary to capture output until something fails.

- Niel

> Thanks,
>
> Juan
>
> On Sat, Feb 13, 2010 at 3:24 PM, Juan Delgado <[hidden email]> wrote:
>  
>> Just got around the problem calling RMDIR. I'm calling
>> neko.Sys.command('RMDIR', [path, '/s', 'q']) instead.
>>
>> Still have issues calling mtasc and swfmill, though.
>>
>> J
>>
>> On Fri, Feb 12, 2010 at 4:49 PM, Simon Richardson <[hidden email]> wrote:
>>    
>>> sandboxed shell, from with in process ?
>>>
>>> si
>>>
>>> On 12 Feb 2010, at 16:07, Juan Delgado wrote:
>>>
>>>      
>>>> More stuff related to processes.
>>>>
>>>> I'm implementing in XAPI xa.Folder.forceDelte() which in mac/linux
>>>> uses rm -rf path and in windows should use RMDIR path /s /q.
>>>>
>>>> For some reason when I try this:
>>>>
>>>> var p = new Process('RMDIR', [path, '/s', '/q']);
>>>>
>>>> I get an exception: "Process creation failure". I've searched the
>>>> list, but what I've found doesn't seem related to my problem. I can
>>>> run the exact same command from the command line and works as
>>>> expected, so no admin rights or anything similar involved.
>>>>
>>>> I've tried case sensitivity, a dozen other parameter orders, even
>>>> different commands such as "del". Still not working.
>>>>
>>>> Funny thing is that other commands such as attrib or dir work as expected.
>>>>
>>>> Any idea why RMDIR looks like a special case?
>>>>
>>>> Thanks,
>>>>
>>>> J
>>>>
>>>> ps: btw, this is the last thing I change before releasing XAPI 0.1.
>>>> You can check out the actual classes here:
>>>>
>>>> http://github.com/zarate/xapi/tree/master/src/xa/
>>>>
>>>> There's in-line docs as well and will be released through haxelib. I'm
>>>> only missing this Folder.forceDelete() for Windows :/
>>>>
>>>> On Fri, Feb 12, 2010 at 10:38 AM, Juan Delgado <[hidden email]> wrote:
>>>>        
>>>>> Hi there,
>>>>>
>>>>> I'm developing an internal build tool that needs to make calls to both
>>>>> swfmill and mtasc. This is what I'm using:
>>>>>
>>>>> var p = new Process(path, [args]);
>>>>> var exitcode = p.exitCode();
>>>>> var error = p.stderr.readAll().toString();
>>>>> var output = p.stdout.readAll().toString();
>>>>> p.close();
>>>>>
>>>>> But for some reason trying to catch the exit code hangs the app. I
>>>>> know calling exitCode() blocks the flow and I'm ok with that, the
>>>>> problem is that the app never comes back, keeps waiting forever.
>>>>>
>>>>> I know the calls to both mtasc and swfmill are ok, cause if i run them
>>>>> by hand on the console they work as expected, and returning 0 as exit
>>>>> code.
>>>>>
>>>>> Any ideas what could  be going on?
>>>>>
>>>>> I'm running haxe 2.0.5 and neko 1.8.1 on Leopard. I'm also using
>>>>> xcross to generate a self-contained executable, but I get the same
>>>>> result when running neko builder.n.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Juan
>>>>>
>>>>> ps; should i ask this on the neko list better?
>>>>>
>>>>> --
>>>>> Juan Delgado - Zárate
>>>>> http://zarate.tv
>>>>> http://blog.zarate.tv
>>>>>
>>>>>          
>>>>
>>>> --
>>>> Juan Delgado - Zárate
>>>> http://zarate.tv
>>>> http://blog.zarate.tv
>>>>
>>>> --
>>>> haXe - an open source web programming language
>>>> http://haxe.org
>>>>        
>>> --
>>> haXe - an open source web programming language
>>> http://haxe.org
>>>
>>>      
>>
>> --
>> Juan Delgado - Zárate
>> http://zarate.tv
>> http://blog.zarate.tv
>>
>>    
>
>
>
>  


--
haXe - an open source web programming language
http://haxe.org