On Mon, 26 Sep 2011 23:14:43 +0100, Mehrdad <wfunction@hotmail.com> wrote:

> On 9/26/2011 3:07 PM, Andrej Mitrovic wrote:
>> SciTE (and probably N++ since it's based on scintilla) has a subsystem
>> setting which can affect how it invokes a process. See the "Command
>> subsystem" section here: http://www.scintilla.org/SciTEDoc.html
>>
>> Usually I run with subsystem 0.
>
> (1) Scintilla is just the text editor. It doesn't have anything to do with the integrated command line.
>
> (2) I tried both 0 and 1, and neither made a difference. In fact, while using 1 DID pop up an extra command-line window, in either case the I/O took place inside SciTE itself. And in both cases, both DMD and my program crashed.
>
> You should be able to easily reproduce this if you set the "Enable close exception" and  "Enable bad handles detection" Global Flags, using the Global Flags utility that comes with Debugging Tools for Windows. (Just make sure you reboot before you expect to see the change.)

On newer versions of windows you can use Application Verifier.. provided you run the exe you want to verify in a debugger (WinDbg or MSVC).

-- 
Using Opera's revolutionary email client: http://www.opera.com/mail/

On Mon, 26 Sep 2011 19:15:08 -0400, Mehrdad <wfunction@hotmail.com> wrote:

> On 9/26/2011 3:41 PM, Steven Schveighoffer wrote:
>> Probably -- let the OS close the handles instead of manually closing them :)
>>
>> -Steve
> I don't think that's a good idea because snn.lib likely does its own internal buffering of the data, which would be lost if the stream isn't closed.

That's what fflush is for.  The handles should simply be closed by the OS.

-Steve