Comments (9)
note: i'm not using VS.NET, i'm just using visual studio C++
Original comment by [email protected]
on 23 Jul 2010 at 8:45
from crashrpt.
Please refer to this page
http://crashrpt.sourceforge.net/docs/html/using_minidump.html.
Does this fix your problem?
Original comment by [email protected]
on 24 Jul 2010 at 4:00
from crashrpt.
okay i tried following those instructions but i do not see a call stack.
Original comment by [email protected]
on 25 Jul 2010 at 4:43
Attachments:
from crashrpt.
Try the following:
1. Specify symbol path directories for the Visaul Studio. Open menu
Tools->Options->Debugging->Symbols and enter the path to the directory where
your PDB files and binaries are located. Then reopen the minidump (close the
solution, open it again and press F5).
2. Open the Modules window and check the symbol loading status for modules of
your program. The status should be 'Symbols loaded.'. Loading paths should
point to the directory where you saved the PDB files and binaries.
If symbols for some modules of your program are loaded, and you have the error,
than there were no debugging symbols generated for the module where crash had
occurred.
If there are still no symbols loaded for any module, than the debugger can't
locate the matching PDB files and/or binaries. Try to recompile the program and
enable PDB file generation.
Does this fix your problem?
Original comment by [email protected]
on 26 Jul 2010 at 12:40
from crashrpt.
Hmm.. after looking on your screenshot the second time, I see that you actually
have stack consisting of one frame:
kJams Pro.exe!MT_CrashPlease::operator()() Line 1158
It seems that you have correct PDB file at least for one module. Can you attach
a screenshot of your Modules window?
Original comment by [email protected]
on 26 Jul 2010 at 1:13
from crashrpt.
here is the modules window. showing that both my app (kjams) and it's one
dependent library (CFLite) are both loaded.
note i'm using incredibuild which creates several pdb's. see 2nd screen shot
Original comment by [email protected]
on 26 Jul 2010 at 8:01
Attachments:
from crashrpt.
It seems that everything is loaded ok. You have matching PDB files loaded for
kJams Pro.exe and CFLite.dll. As these modules are major for your application,
you are able to recover detailed stack traces for these modules.
In this particular case, the stack trace consists of a single frame. This may
be because of optimizations enabled or because of something else that affects
the stack trace accuracy. For my application, this happens sometimes, too. For
example, if I generate report manually on hot key press, the stack is not as
accurate as I expect.
I think IncrediBuild shouldn't affect the stack trace. I read their FAQ
http://www.xoreax.com/support_faq.htm and it seems that this tool generates the
correct debugging information.
I would advice you to do the following:
1. Try to read the minidump with the crprober.exe tool that presents in
crashrpt archive. You can find the info here
http://crashrpt.sourceforge.net/docs/html/crprober_tool.html. For my app, it
sometimes generates better stack traces than Visual Studio. Test how
crprober.exe opens minidumps of your application.
2. Continue testing your application with crash reporting enabled, or release
it to public. When many crash reports are received from testers or from users,
you will be able to determine how many stack traces are valid and how many are
not. Compare how those reports are read by Visual Studio and crprober.exe.
Original comment by [email protected]
on 27 Jul 2010 at 1:39
from crashrpt.
The documentation on how to open crash minidump was improved in v.1.2.7.
Original comment by [email protected]
on 10 Oct 2010 at 2:34
- Changed state: Fixed
from crashrpt.
Issue 64 has been merged into this issue.
Original comment by [email protected]
on 15 Oct 2010 at 12:43
from crashrpt.
Related Issues (20)
- Remove VS2005/ATL Compatibility HOT 2
- CrashRpt is not capturing Exact exception information some times. its crashed at crashHandler HOT 1
- Crashrpt not able to handle the Exceptions from ActiveX Controller call back in MFC . HOT 2
- can't make the crashreporter installed HOT 2
- No minidump created sometimes - reports "Only part of a ReadProcessMemory or WriteProcessMemory request was completed" HOT 1
- [deleted issue]
- Capture only windows belonging to the process HOT 1
- Czech localization HOT 2
- Potential crash in CrashSender.exe HOT 1
- uiAccess=true elevated process cannot create minidump HOT 1
- not compilable under Visual Studio 2013 HOT 5
- Include Polish translation (attached) HOT 1
- Redirects to a different server are not handled HOT 1
- If the crashsender is redirected, the crash report upload may happen twice.
- CrashCallback not working in VS 2013 HOT 3
- CrashSender crashes with access violation
- Can't make CrashRpt work with Qt HOT 1
- Translation files
- Setting bContinueExecution generates report twice
- can't open the crashfix server website HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from crashrpt.