--- Comment #8 from pinskia at gcc dot gnu dot org 2008-02-13 19:06 ---
One issue is we have two standards here. The POSIX one and the C++ one. Now
getrlimit/SIGXFSZ signal is a POSIX issue while using filebuf is a C++ one.
Now does POSIX talk about filebuf ?
--
http://gcc.gnu.or
--- Comment #7 from sebor at roguewave dot com 2008-02-13 18:15 ---
I see I should have checked the actual stdio behavior instead of relying on
the standard. Recent Linux and Solaris both do, in fact, generate SIGXFSZ out
of C stdio. AIX 5.3 does not, and neither does HP-UX 11.23, althou
--- Comment #6 from rguenth at gcc dot gnu dot org 2008-02-13 16:56 ---
Calling the C stdio functions will result in the same behavior, so the as-if
rule is satisfied.
--
rguenth at gcc dot gnu dot org changed:
What|Removed |Added
-
--- Comment #5 from sebor at roguewave dot com 2008-02-13 16:37 ---
I understand that POSIX requires the signal but I'm not sure I see what that
has to do with filebuf. C++ specifies that filebuf member functions behave
"as if" by calling the C stdio functions.
See 27.8.1, p2:
In thi
--- Comment #4 from schwab at suse dot de 2008-02-13 16:08 ---
POSIX requires that write generates SIGXFSZ if the limit is exceeded (on
systems that support the XSI extensions).
--
schwab at suse dot de changed:
What|Removed |Added
--- Comment #3 from sebor at roguewave dot com 2008-02-13 15:46 ---
I used setrlimit() only to emulate low disk space conditions. The same
"problem"
occurs in a pure C++ program (i.e., one that makes no POSIX or other non-C++
calls) when it really does run out of disk space.
So again, s
--- Comment #2 from rguenth at gcc dot gnu dot org 2008-02-13 14:33 ---
This is just what is expected.
--
rguenth at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #1 from pinskia at gcc dot gnu dot org 2008-02-13 03:15 ---
getrlimit and setrlimit are outside of standard C/C++, they are part of POSIX.
So it might be best to ask the POSIX guys.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35176
