David,

Thanks for this report. I will refer it to the person who built the most
recent Windows binaries, who will probably contact you privately if he
hasn't done so already.  From a standpoint of what is supposed to happen, 2>
looks like UNIX syntax to me, not Windows, but assuming you are using a
shell that is appropriate, we can debug forward as follows. If standard
error output is showing up in a black-on-white-background virtual console,
it would mean that the VM being used isn't the one you intend. The virtual
consoles occur in wiconx.exe. It may be that in the Windows-binary-build
hand-off, there was some confusion about how to build the various
iconx's used in Windows, which unfortunately does not give ideal behavior if
we just stick to one-iconx-for-everything.

There is one more possibility, which is that your program uses graphics and
wiconx.exe is being selected automatically based on that. Since there is a
console iconx.exe that supports graphics, it may be a matter of telling
unicon/icont to use iconx instead of wiconx.  I will have to look into
whether this line of thinking is even relevant. In the meantime, can you
tell me whether your program uses graphics, or a function or record or class
named Event ?

Sorry for all the confusion!  Also: the recompiling of a program should not
cause it to be run unless -x is used. That one is mysterious.

Clint

On Fri, Apr 2, 2010 at 7:26 AM, David Gamey <[email protected]> wrote:

> I just put in the new binaries for Windows and bumped into some odd
> behavior.
> When I compile and work from command line.  ex.
>
>    unicon test.icn
>    test.exe 2> errout.txt
>
> The &errout is grabbed in a window and not sent to the file.
>
> Also, I had a loop so after terminating the program the next time I
> recompiled at command line it compiled and ran the program.
>
> Any thoughts.
> David
>
------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Unicon-group mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/unicon-group

Reply via email to