Re: [Interest] Retrieving the object info due to exception std::bad_alloc

2018-03-01 Thread Ramakanth Kesireddy
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

Re: [Interest] Retrieving the object info due to exception std::bad_alloc

2018-03-01 Thread Konstantin Tokarev
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

Re: [Interest] Retrieving the object info due to exception std::bad_alloc

2018-03-01 Thread Ramakanth Kesireddy
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