jirentabu / crashrpt

Automatically exported from code.google.com/p/crashrpt
0 stars 0 forks source link

CrashCallback not working in VS 2013 #244

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
We upgraded our solution to 2013 and now crashrpt doesn't catch crashes like 
stl invalid parameter handler, terminte, protected memory access, etc. The only 
times it works now is if our program force triggers a crash report. I have 
built crashrpt in VS 2013 and have it properly linked in. It worked for years 
with VS 2008. Has anyone had it work in a VS 2013 build? 

What version of CrashRpt are you using?
1.4.2

What is your version of Visual Studio?
Visual Studio 2013

What is your version of Windows operating system?
Windows 8.1

Original issue reported on code.google.com by ABrussZ...@gmail.com on 28 Aug 2014 at 4:00

GoogleCodeExporter commented 9 years ago
By "work" I mean you install crashrpt into your application and the 
CrashCallback function is triggered if you execute code such as:

std::vector<bool> vb(3, false);
vb[5] = true;

assuming you setup crashrpt to listen for those kinds of crashes.

Original comment by ABrussZ...@gmail.com on 28 Aug 2014 at 4:03

GoogleCodeExporter commented 9 years ago
It appears the issue was the c++ runtime behavior has changed such that things 
that used to trigger crashes do not anymore. 

For example this used to cause a crash:

std::vector<int> blah(4, 0.0);
double dval = blah[4];

and does not anymore. C'est la vie. This case can be closed.

Original comment by ABrussZ...@gmail.com on 17 Oct 2014 at 8:25

GoogleCodeExporter commented 9 years ago
Our app has not worked (the callback has not worked) for the past several 
months.  We upgraded to vs2013 at about the same time but suspect some windows 
update might have been the reason.  Can somebody confirm this library still 
works with an up to date Win7 and building with vs2013?

Original comment by edwinche...@gmail.com on 4 Feb 2015 at 1:18