[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 111102] Memcheck seems to have problems with large (memory
From:       Brian WIlliams <brianw1138SKS () comcast ! net>
Date:       2005-10-06 13:59:09
Message-ID: 20051006135909.23334.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=111102         




------- Additional Comments From brianw1138SKS comcast net  2005-10-06 15:59 -------
The problem was not with a non-throwing new(); the new() in question throws, but \
valgrind does not initiate the error, instead returning NULL. Of course, the program \
in question, expecting an exception, happily eats itself on the NULL. The lack of \
message merely adds insult to injury. The reply in Comment #3 states that it is \
impossible for valgrind to throw the no memory exception, which I accept at face \
value, in that valgrind doesn't throw. However, GDB, DDE and even MS Dev Studio has \
been doing exactly that for years. All that aside, the situation I am seeing is that \
between my program and valgrind, we have eaten all available memory. I feel that a \
more equitable solution (other than a rewrite) is to recognize the fatal condition \
and stop, stating that the reason for the abort is no more memory. At the very least, \
I can take that unambigous message back to my SysAdmin and get more memory installed.


[prev in list] [next in list] [prev in thread] [next in thread]