public inbox for
 help / color / mirror / Atom feed
From: Bruce Edson <>
To: "Sourcenav (E-mail)" <>,
	 "Sourcenav-Devl (E-mail)" <>
Subject: RE: Running a separate TCL process using hyper
Date: Thu, 02 May 2002 13:00:00 -0000	[thread overview]
Message-ID: <> (raw)

Well, as further input, it appears that hyper is crashing upon exiting the
tcl script I've asked it to run.  Doesn't seem to matter whether I use r or
r+ on the open statement.  The tcl script I've created for test purposes,
puts up a message box and then exits once I respond to the message box.

I noticed that I could use 'puts' in the tcl script and its output went
through the pipe to the parent app where it could be read with a 'gets'.
This would work great for me.  However, I get an error an additional error
when hyper can't seem to exit that says 'can't write, channel file556 is not
open'.  Not sure if this is coming from the script in the spawned hyper
process, or from hyper itself.  The parent app does indeed receive
everything the spawned tcl script sends with the 'puts'.  The script ends
with a 'exit 0'.

This sure seems like a pretty simple task I'm trying to accomplish.  Spawn a
separate process to run a tcl script, get back occasional updates so I can
update a progress bar, exit the process (and hyper) when the script is done,
and then have the parent app remove the progress bar when it detects that
the spawned process has ended/exited/closed.  Is using hyper to run the tcl
script process part of my problem?  Is there a better way to do this?

Any help would be greatly appreciated.


-----Original Message-----
From: Bruce Edson []
Sent: Thursday, May 02, 2002 8:47 AM
To: Sourcenav (E-mail); Sourcenav-Devl (E-mail)
Subject: Running a separate TCL process using hyper

Sorry for sending this to both mail lists, but I figure until everyone has
moved over to the new one at SourceForge I will post to both.

We have created a TCL process that will augment the xref tables for Source
Navigator.  We want to do this so as to be able to cross-reference unique
macro method invocations in our code base.  As the process takes time we
would like to run it in a separate process much the way dbimp runs, although
we're using TCL to do this.  Now for the problem,  we can set up a pipe for
hyper to run the TCL script and that seems to work (we use 'open', and the
pipe seems to operate in both directions).  We would like to use a pipe so
that we can monitor progress and update a progress bar.  The problem is that
we can't find a way to know that the process has exited (to know when its
done).  The script has the TCL command 'exit 0' at the end.  We've tried
waiting for eof or for the pid to change, but it never does.  We've tried
sending back a unique string from the process so that the calling program
can then just 'close' the pipe.  The 'close' hangs.  I'm also left with a
hyper process still running in memory for any of these cases, so just not
waiting and continuing on, eventually gets me when I try to exit Source
Navigator.  Can someone give me a suggestion on how to get this hyper
process to end and a way to know that it has ended?



             reply	other threads:[~2002-05-02 20:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-02 13:00 Bruce Edson [this message]
     [not found] <26F9F6EAB586D411850700B0D049E6E4014D2FCD@shasta.pdx.stepte>
2002-05-02  9:06 ` Randall R Schulz
  -- strict thread matches above, loose matches on Subject: below --
2002-05-02  8:48 Bruce Edson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).