From: shags72 on
On Jun 12, 11:32 am, Alexandre Ferrieux <alexandre.ferri...(a)gmail.com>
wrote:
> On 12 juin, 15:29, shags72 <je...(a)mtco.com> wrote:
>
>
>
> >  What happens is
> > if using exec to open something it inconsistently hangs the program
> > and you must kill your session. Although if you set the affinity of
> > the program process to a single cpu then it won't hang. This is what I
> > had been doing but now the program is capable of using multi cpus and
> > we wouldn't be able to take advantage of the time savings. Which
> > people have tested and reported huge time savings, so I have to fix
> > this. Hope I explained this well enough and that this makes sense to
> > you. Thanks.
>
> When you say "set the cpu affinity of the process", are you talking
> about the (embedded Tcl) parent, or about the (other program) child ?
> If you haven't already, please try both configurations and report
> which one hangs.
>
> -Alex
I set it on the other program. I don't know how to set it on anything
different. If you could let me know how I would appreciate it a lot.
Thanks.
From: Alexandre Ferrieux on
On Jun 12, 7:19 pm, shags72 <je...(a)mtco.com> wrote:
> On Jun 12, 11:32 am, Alexandre Ferrieux <alexandre.ferri...(a)gmail.com>
> wrote:
>
>
>
> > On 12 juin, 15:29, shags72 <je...(a)mtco.com> wrote:
>
> > >  What happens is
> > > if using exec to open something it inconsistently hangs the program
> > > and you must kill your session. Although if you set the affinity of
> > > the program process to a single cpu then it won't hang. This is what I
> > > had been doing but now the program is capable of using multi cpus and
> > > we wouldn't be able to take advantage of the time savings. Which
> > > people have tested and reported huge time savings, so I have to fix
> > > this. Hope I explained this well enough and that this makes sense to
> > > you. Thanks.
>
> > When you say "set the cpu affinity of the process", are you talking
> > about the (embedded Tcl) parent, or about the (other program) child ?
> > If you haven't already, please try both configurations and report
> > which one hangs.
>
> > -Alex
>
> I set it on the other program. I don't know how to set it on anything
> different. If you could let me know how I would appreciate it a lot.
> Thanks.

Ha ! Then, you're observing a deadlock in [exec] on Windows multi-
core, which is solved by single-proc'ing the child ? Very interesting.
It might be a decisive clue to bug 1939509:

https://sourceforge.net/tracker/?func=detail&aid=1939509&group_id=10894&atid=110894

If you have an SF account, please go there and make yourself known.
Otherwise I'll mention this thread and try to stir things a bit :)

-Alex
From: shags72 on
On Jun 12, 12:32 pm, Alexandre Ferrieux <alexandre.ferri...(a)gmail.com>
wrote:
> On Jun 12, 7:19 pm, shags72 <je...(a)mtco.com> wrote:
>
>
>
>
>
> > On Jun 12, 11:32 am, Alexandre Ferrieux <alexandre.ferri...(a)gmail.com>
> > wrote:
>
> > > On 12 juin, 15:29, shags72 <je...(a)mtco.com> wrote:
>
> > > >  What happens is
> > > > if using exec to open something it inconsistently hangs the program
> > > > and you must kill your session. Although if you set the affinity of
> > > > the program process to a single cpu then it won't hang. This is what I
> > > > had been doing but now the program is capable of using multi cpus and
> > > > we wouldn't be able to take advantage of the time savings. Which
> > > > people have tested and reported huge time savings, so I have to fix
> > > > this. Hope I explained this well enough and that this makes sense to
> > > > you. Thanks.
>
> > > When you say "set the cpu affinity of the process", are you talking
> > > about the (embedded Tcl) parent, or about the (other program) child ?
> > > If you haven't already, please try both configurations and report
> > > which one hangs.
>
> > > -Alex
>
> > I set it on the other program. I don't know how to set it on anything
> > different. If you could let me know how I would appreciate it a lot.
> > Thanks.
>
> Ha ! Then, you're observing a deadlock in [exec] on Windows multi-
> core, which is solved by single-proc'ing the child ? Very interesting.
> It might be a decisive clue to bug 1939509:
>
> https://sourceforge.net/tracker/?func=detail&aid=1939509&group_id=108...
>
> If you have an SF account, please go there and make yourself known.
> Otherwise I'll mention this thread and try to stir things a bit :)
>
> -Alex- Hide quoted text -
>
> - Show quoted text -


OOOk. Not really sure what you meant by that. LOL. But if it helps
someone great. By the way I don't know what an SF account so I
probably don't have one, and the embedded version would be 8.1 if that
would help. What is wierd is that there is an interface program that
runs on one embedded version (8.1) that is where I write my tcl code,
but the software that sends the (what we call) events uses 8.3 or 4
can't remember. They didn't tell me this so I was always floundering
around using trying to use 8.3 syntax and getting invalid options on
different commands. now I know but then I heard that 8.1 was not a
very good version of tcl. Just hearsay I really don't know as I am
completely new at coding of any language and only been using this for
about a year. Do you agree with what Bruce said? following is a quote
from his post.

" but I would be surprised if the system can't use exec but can use
open with a pipeline. (maybe the "open is fine" is based on just
opening
files). "


I hope not because I would really like to use this instead of exec if
it will fix my issue. Somone was opening TK windows using it and he
said that it fixed this so I thought it might fix my issue with
opening notepad. You guys are great. Thanks.
From: shags72 on
On Jun 12, 1:56 pm, shags72 <je...(a)mtco.com> wrote:
> On Jun 12, 12:32 pm, Alexandre Ferrieux <alexandre.ferri...(a)gmail.com>
> wrote:
>
>
>
>
>
> > On Jun 12, 7:19 pm, shags72 <je...(a)mtco.com> wrote:
>
> > > On Jun 12, 11:32 am, Alexandre Ferrieux <alexandre.ferri...(a)gmail.com>
> > > wrote:
>
> > > > On 12 juin, 15:29, shags72 <je...(a)mtco.com> wrote:
>
> > > > >  What happens is
> > > > > if using exec to open something it inconsistently hangs the program
> > > > > and you must kill your session. Although if you set the affinity of
> > > > > the program process to a single cpu then it won't hang. This is what I
> > > > > had been doing but now the program is capable of using multi cpus and
> > > > > we wouldn't be able to take advantage of the time savings. Which
> > > > > people have tested and reported huge time savings, so I have to fix
> > > > > this. Hope I explained this well enough and that this makes sense to
> > > > > you. Thanks.
>
> > > > When you say "set the cpu affinity of the process", are you talking
> > > > about the (embedded Tcl) parent, or about the (other program) child ?
> > > > If you haven't already, please try both configurations and report
> > > > which one hangs.
>
> > > > -Alex
>
> > > I set it on the other program. I don't know how to set it on anything
> > > different. If you could let me know how I would appreciate it a lot.
> > > Thanks.
>
> > Ha ! Then, you're observing a deadlock in [exec] on Windows multi-
> > core, which is solved by single-proc'ing the child ? Very interesting.
> > It might be a decisive clue to bug 1939509:
>
> >https://sourceforge.net/tracker/?func=detail&aid=1939509&group_id=108...
>
> > If you have an SF account, please go there and make yourself known.
> > Otherwise I'll mention this thread and try to stir things a bit :)
>
> > -Alex- Hide quoted text -
>
> > - Show quoted text -
>
> OOOk. Not really sure what you meant by that. LOL. But if it helps
> someone great. By the way I don't know what an SF account so I
> probably don't have one, and the embedded version would be 8.1 if that
> would help. What is wierd is that there is an interface program that
> runs on one embedded version (8.1) that is where I write my tcl code,
> but the software that sends the (what we call) events uses 8.3 or 4
> can't remember. They didn't tell me this so I was always floundering
> around using trying to use 8.3 syntax and getting invalid options on
> different commands. now I know but then I heard that 8.1 was not a
> very good version of tcl. Just hearsay I really don't know as I am
> completely new at coding of any language and only been using this for
> about a year. Do you agree with what Bruce said? following is a quote
> from his post.
>
> "   but I would be surprised if the system can't use exec but can use
> open with a pipeline. (maybe the "open is fine" is based on just
> opening
> files).   "
>
> I hope not because I would really like to use this instead of exec if
> it will fix my issue. Somone was opening TK windows using it and he
> said that it fixed this so I thought it might fix my issue with
> opening notepad. You guys are great. Thanks.- Hide quoted text -
>
> - Show quoted text -

Oh and one more question. If it is embedded tcl version. I probably
won't be able to use any fix that is brought on to tcl at this time
right?
From: Alexandre Ferrieux on
On Jun 12, 8:56 pm, shags72 <je...(a)mtco.com> wrote:
> On Jun 12, 12:32 pm, Alexandre Ferrieux <alexandre.ferri...(a)gmail.com>
> wrote:
>
>
>
>
>
> > On Jun 12, 7:19 pm, shags72 <je...(a)mtco.com> wrote:
>
> > > On Jun 12, 11:32 am, Alexandre Ferrieux <alexandre.ferri...(a)gmail.com>
> > > wrote:
>
> > > > On 12 juin, 15:29, shags72 <je...(a)mtco.com> wrote:
>
> > > > >  What happens is
> > > > > if using exec to open something it inconsistently hangs the program
> > > > > and you must kill your session. Although if you set the affinity of
> > > > > the program process to a single cpu then it won't hang. This is what I
> > > > > had been doing but now the program is capable of using multi cpus and
> > > > > we wouldn't be able to take advantage of the time savings. Which
> > > > > people have tested and reported huge time savings, so I have to fix
> > > > > this. Hope I explained this well enough and that this makes sense to
> > > > > you. Thanks.
>
> > > > When you say "set the cpu affinity of the process", are you talking
> > > > about the (embedded Tcl) parent, or about the (other program) child ?
> > > > If you haven't already, please try both configurations and report
> > > > which one hangs.
>
> > > > -Alex
>
> > > I set it on the other program. I don't know how to set it on anything
> > > different. If you could let me know how I would appreciate it a lot.
> > > Thanks.
>
> > Ha ! Then, you're observing a deadlock in [exec] on Windows multi-
> > core, which is solved by single-proc'ing the child ? Very interesting.
> > It might be a decisive clue to bug 1939509:
>
> >https://sourceforge.net/tracker/?func=detail&aid=1939509&group_id=108...
>
> > If you have an SF account, please go there and make yourself known.
> > Otherwise I'll mention this thread and try to stir things a bit :)
>
> > -Alex- Hide quoted text -
>
> > - Show quoted text -
>
> OOOk. Not really sure what you meant by that. LOL. But if it helps
> someone great. By the way I don't know what an SF account so I
> probably don't have one, and the embedded version would be 8.1 if that
> would help.

OK never mind. If we squash that one thanks to your report, you'll be
on the photo ;-)

> about a year. Do you agree with what Bruce said? following is a quote
> from his post.
>
> "   but I would be surprised if the system can't use exec but can use
> open with a pipeline. (maybe the "open is fine" is based on just
> opening
> files).   "
>
> I hope not because I would really like to use this instead of exec if
> it will fix my issue. Somone was opening TK windows using it and he
> said that it fixed this so I thought it might fix my issue with
> opening notepad. You guys are great. Thanks.

I tend to agree with Bruce. The only difference that comes to mind
between [open |...] and [exec] is the availability of I/O pipes to the
child, and I don't see a direct link with a deadlock in your case.
Just to be sure, when you spawn the child process with [exec], you've
got an "&", right ?

Second question: have you actually tried [open |...] ? Does it solve
the issue without using the processor affinity trick ?

-Alex