[PATCH] libstdc++/6648

[Benjamin Kosnik]

> More generally, the standard and/or QoI concerns dictate proper
> interleaving between tied istream and ostream.  We need a framework to
> test all these timing and tying issues; and that should better cover
> the untested interactive cases.

This is on my near-term TODO list. Storing all these testcases in
narrow_stream_objects.cc is an OK intermediate step, I think.
 
> Here is one technique I have thought about: if we could replace
> lowest-layer read(), write() for various tests; we could study the
> proper interleaving pattern of calls.  I also wanted this technique to
> automate detection of bad OS system call usage. (i.e. the test cases
> where you have to run under truss, ktrace, strace, etc).

Hmm. Interesting. 

> Since I consider this an obvious fix now, I'd say install it on
> mainline and queue it for 3.1.1.  If I'm wrong, then I'll take the
> heat for approving it. ;-)
 
Looks good to me too, thanks,

benjamin