search

jirentabu / crashrpt

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

'CRT new operator fault handler' broken #81

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
CRT new operator fault handler broken.

What steps will reproduce the problem?
2. Create simple MFC app.
3. Install all crashrpt handlers.
4. insert code in any suitable place "char *dummy = new char[LONG_MAX];"
5. crashrpt crashes.

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?
crashrpt 1.2.9.
MS VS2010.

Please provide any additional information below.

Original issue reported on code.google.com by gure...@gmail.com on 15 Apr 2011 at 10:48

GoogleCodeExporter commented 9 years ago 
generated crashdump points to 
int CCrashHandler::GenerateErrorReport()
line m_pCrashDesc->m_dwProcessId = GetCurrentProcessId();
disabling all optimizations not helped.

Original comment by gure...@gmail.com on 15 Apr 2011 at 11:43

GoogleCodeExporter commented 9 years ago

Original comment by zexspect...@gmail.com on 21 Apr 2011 at 2:36

GoogleCodeExporter commented 9 years ago 
I tried to reproduce, but the simple MFC application just showed me "Out of 
memory" message box, and no crash happened at all. 

1. Can you attach your MFC application to this ssue?

2. Please clarify, how is it possible that "crashrpt crashes" and "minidump is 
generated" at the same time. If CrashRpt would crash, there wouldn't be any 
minidump, is it?

Original comment by zexspect...@gmail.com on 15 May 2011 at 7:34

GoogleCodeExporter commented 9 years ago 
http://pix.am/yLyv.png

callback points to crashrpt.dll

Original comment by gure...@gmail.com on 18 May 2011 at 6:14

GoogleCodeExporter commented 9 years ago 
As your screenshot displays, this is not a bug. See the Call Stack window - the 
stack trace looks ok. For additional information about using crash dumps, see 
http://crashrpt.sourceforge.net/docs/html/using_minidump.html

I plan to close this issue, because I don't think this is a real bug.

Original comment by zexspect...@gmail.com on 22 May 2011 at 10:52

GoogleCodeExporter commented 9 years ago 
Call Stack pointing to you crashrpt lib code, not at application code.
may be its crt bug. that's not good at all.

Original comment by gure...@gmail.com on 23 May 2011 at 7:02

GoogleCodeExporter commented 9 years ago 
This is not a bug - neither in CRT nor in CrashRpt. Since you used 
crGererateErrorReport() function, the source of crash is in CrashRpt.dll 
module, so the stack trace looks like expected. If a crash happens inside of 
your app's function, the source of crash would be in your module.

I close the issue.

Original comment by zexspect...@gmail.com on 23 May 2011 at 1:42