Thanks all for your thoughts.
Assuming that it throws bad_alloc exception, I added global replacement of
new operator but it throws linker error of multiple definition of new
operator though it seems to invoke overloaded version of new operator with
filename and line no.Any pointers on how to avoid
01.03.2018, 20:35, "Ramakanth Kesireddy" :
> When system runs on low memory, the object allocations through new in the Qt
> application does throw bad_alloc exception,right?
It may or may not throw exception, depending on OS kind, overcommit settings,
memory limits set for your application, and
When system runs on low memory, the object allocations through new in the
Qt application does throw bad_alloc exception,right?
On Thursday, March 1, 2018, Thiago Macieira
wrote:
> On Wednesday, 28 February 2018 15:23:22 PST Konstantin Tokarev wrote:
>> bad_alloc is mostly thrown due to too view m
On Wednesday, 28 February 2018 15:23:22 PST Konstantin Tokarev wrote:
> bad_alloc is mostly thrown due to too view memory for the request in
> question.
> > so when you continue your program, chances are good to see more
> > bad_allocs.
>
> Or don't get any bad_alloc at all, being killed by OOM Ki
28.02.2018, 09:51, "alexander golks" :
> Am Tue, 27 Feb 2018 23:12:51 +0530
> schrieb Ramakanth Kesireddy :
>
>> Hi,
>>
>> As mentioned in http://doc.qt.io/archives/qt-4.8/exceptionsafety.html, the
>> below code is being used to catch the exceptions in application:-
>>
>> QApplication app(arg
On Tuesday, 27 February 2018 09:42:51 PST Ramakanth Kesireddy wrote:
> Please let me know if there any means to get the runtime object info like
> class name, method name(if possible line number) throwing the exception
> std::bad_alloc in catch block?
There isn't, not portably.
--
Thiago Macieir
Am Tue, 27 Feb 2018 23:12:51 +0530
schrieb Ramakanth Kesireddy :
> Hi,
>
> As mentioned in http://doc.qt.io/archives/qt-4.8/exceptionsafety.html, the
> below code is being used to catch the exceptions in application:-
>
> QApplication app(argc, argv);
> ...
> try {
> app.exec();
> } catch (const
