Am 2016-03-26 08:27, schrieb Randolph Fritz:
On Mar 26, 2016, at 12:09 AM, Georg Mischler <schor...@schorsch.com>
wrote:
I tend to agree with Randolph. This is likely a problem that comes to
the surface due to the different memory layout applied by the MS
compiler.
I suppose it could also be a timing problem. Perhaps the Windows stdio
library is multi-threaded and this somehow interacts with pipes.
For a while I also had that suspicion, especially since in cmd.exe,
things go right (or at least slightly less wrong) once in a while.
But memory alignment doesn't have to be identical on each run, and I
don't see a a reason for making straight stdio calls multi-threaded,
unless you explicitly use the "overlapping io" functions.
We would also find lots of complaints online, if correct use of
stdio could lead to intermittent failure.
Hmmm…or perhaps MSVC’s code generation “optimizer” is creating
problems. Might be worth setting it to the lowest level and see if
that helps.
This is a debug build with zero optimization.
Then I'll have to figure out how I can get the MS debugger to invoke
such a chained pipeline for stepping through the process.
So far I could only take a glance when rcalc output was blocked for
some reason, so I had time to attach the debugger from the outside.
But that only gave me a static picture, which didn't really help.
I wonder if the Dr. Memory debugging tool (http://www.drmemory.org/)
would help?
I'll look into it, thanks!
-schorsch
--
Georg Mischler -- simulations developer -- schorsch at schorsch com
+schorsch.com+ -- lighting design tools -- http://www.schorsch.com/
_______________________________________________
Radiance-dev mailing list
Radiance-dev@radiance-online.org
http://www.radiance-online.org/mailman/listinfo/radiance-dev
