drdump.com
Open in
urlscan Pro
213.79.122.191
Public Scan
Submitted URL: http://www.drdump.com/
Effective URL: https://drdump.com/crash-reporting-system
Submission: On November 29 via api from NL — Scanned from NL
Effective URL: https://drdump.com/crash-reporting-system
Submission: On November 29 via api from NL — Scanned from NL
Form analysis 1 forms found in the DOM
Name: aspnetForm — POST ./crash-reporting-system
<form name="aspnetForm" method="post" action="./crash-reporting-system" onsubmit="javascript:return WebForm_OnSubmit();" id="aspnetForm">
<div>
<input type="hidden" name="__EVENTTARGET" id="__EVENTTARGET" value="">
<input type="hidden" name="__EVENTARGUMENT" id="__EVENTARGUMENT" value="">
<input type="hidden" name="__VIEWSTATE" id="__VIEWSTATE"
value="/wEPDwUKLTQ1MDIzODAzNGQYAQUeX19Db250cm9sc1JlcXVpcmVQb3N0QmFja0tleV9fFgMFJmN0bDAwJGN0bDAwJE1haW5NZW51JExvZ2luU3RhdHVzJGN0bDAxBSZjdGwwMCRjdGwwMCRNYWluTWVudSRMb2dpblN0YXR1cyRjdGwwMwUlY3RsMDAkY3RsMDAkTWFpblByaXZhY3lQb2xpY3lDaGVja0JveNquYyfvb9BNEf/fHw2dQ1rQyYguCStZECOlAKtFuOgQ">
</div>
<script type="text/javascript">
//<![CDATA[
var theForm = document.forms['aspnetForm'];
if (!theForm) {
theForm = document.aspnetForm;
}
function __doPostBack(eventTarget, eventArgument) {
if (!theForm.onsubmit || (theForm.onsubmit() != false)) {
theForm.__EVENTTARGET.value = eventTarget;
theForm.__EVENTARGUMENT.value = eventArgument;
theForm.submit();
}
}
//]]>
</script>
<script src="/WebResource.axd?d=I7Nnq3mpb_EOFXoABBWEqQCxHucUEq_s33Y8OV2Z17ArSXKKeZAoAbpiyED6lhQxAv82iCt2iFblNkDuJeoSn7PXLf0pz9XSbUg9DBPXrJw1&t=638286173964787378" type="text/javascript"></script>
<script type="text/javascript">
//<![CDATA[
function WebForm_OnSubmit() {
if (typeof(ValidatorOnSubmit) == "function" && ValidatorOnSubmit() == false) return false;
return true;
}
//]]>
</script>
<div>
<input type="hidden" name="__VIEWSTATEGENERATOR" id="__VIEWSTATEGENERATOR" value="ACC07762">
<input type="hidden" name="__EVENTVALIDATION" id="__EVENTVALIDATION"
value="/wEdAAv6kkr4CC24sidsTakfHs6Kx6R5yCCULBn2OG9JNwV14wV1GpUMm9Z5e+izxBIuE1nIzy58L7lBX/dYCfBj6zHj7mnysaHnhBl5WmlWsF6Iav4K66sBi9minUo6iRKMWpniPHKJ2qYPkTls6EfrijWQ6f++RjXvY3CH+U9CUGnR3wpWSiP1stGXfnXskJUpuDAC/aeZeoy3rxSPGET+Zxhd4Wyqwnlfqlhu1J76VQX0rC2GkW2dmNrLAQ6ckG92p0CqPdyHdg7couJBhQigtq3n">
</div>
<input type="hidden" name="ctl00$ctl00$RecaptchaResponseHiddenField" id="ctl00_ctl00_RecaptchaResponseHiddenField">
<header>
<div class="container logo">
<div class="big-logo">
<a href="https://drdump.com/">Doctor Dump</a>
</div>
<div class="small-logo">
<a href="https://idol-software.com">By Idol Software</a>
</div>
</div>
<div class="my_menu_bar">
<div class="container">
<nav role="navigation" class="navbar">
<div class="navbar-header">
<button type="button" data-target="#navbarCollapse" data-toggle="collapse" class="navbar-toggle">
<span class="sr-only">Toggle navigation</span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
</button>
</div>
<div id="navbarCollapse" class="collapse navbar-collapse">
<ul class="nav navbar-nav">
<li><a href="/crash-reporting-system">Features</a></li>
<li><a href="/integrate-crash-reporting-to-windows-cpp-application">Integration</a></li>
<li><a href="/testimonials">Testimonials</a></li>
<li><a href="AppVersion.aspx?AppVersionID=2&Login=guest" id="ctl00_ctl00_MainMenu_A4">Demo tour</a></li>
</ul>
<ul class="nav navbar-nav navbar-right">
<li><a id="ctl00_ctl00_MainMenu_LoginStatus" href="javascript:__doPostBack('ctl00$ctl00$MainMenu$LoginStatus$ctl02','')">Login</a></li>
<li><a href="/signup">Signup</a></li>
</ul>
</div>
</nav>
</div>
</div>
</header>
<div class="wrapper">
<div class="container">
<h1> About Doctor Dump Crash Reporting System</h1>
<p style="font-size: 1.3em"> Doctor Dump is a free <strong>crash reporting</strong> and memory dump analyzing service. It collects, organizes and stores crash reports from your customers, gives you all necessary data to fix the bug and provides
your users with solution/workaround to the problem immediately after the crash.</p>
<h2> How it works</h2>
<div id="how_it_works" class="slideshow" style="visibility: visible; opacity: 1; display: block; position: relative; overflow: visible; transition: height 0.05s ease-out, width 0.05s ease-out; -webkit-tap-highlight-color: rgba(0, 0, 0, 0);">
<div data-slidr="slide1" class="slide"
style="display: block; visibility: visible; position: absolute; opacity: 1; z-index: 1; pointer-events: auto; backface-visibility: hidden; transform-style: preserve-3d; animation: 0.4s ease-out 0s 1 normal none running slidr-fade-in;">
<div class="slidetext"> First of all you need to <a href="/integrate-crash-reporting-to-windows-cpp-application">integrate</a> the Doctor Dump <strong>crash reporting library</strong> into your <strong>Windows C++</strong> application.
After that when a crash or unhandled exception occurs it will be caught and a report about the bug will be sent to the Doctor Dump, that will analyze the report and using problem footprint (that usually is a stack trace) put it to a group
of exact same issues. Similar groups caused by one reason (one buggy function can be called by different callers, so stacks will differ) form a <em>problem</em> that is fixing unit. </div>
<div class="slideimg">
<img src="Images/demo-crash.jpg" id="ctl00_ctl00_MainContent_MainContent_Img1" style="margin-top: 1px" alt="Crash report">
</div>
</div>
<div data-slidr="slide2" class="slide" style="display: block; visibility: hidden; position: absolute; opacity: 0; z-index: 0; pointer-events: none; backface-visibility: hidden; transform-style: preserve-3d;">
<div class="slidetext"> After the crash report has been uploaded user may be directed to a customized web page about that problem where may exist some information, for example a link to a version where this bug has been fixed or some
workaround. Or default page may be shown, where user can see the state of the bug and ID of his report which he can use when communicate with support.
<a href="UploadedReport.aspx?DumpID=52" id="ctl00_ctl00_MainContent_MainContent_A2" target="_blank">Open that page</a>
</div>
<div class="slideimg">
<a href="UploadedReport.aspx?DumpID=52">
<img src="Images/demo-report-uploaded.png" id="ctl00_ctl00_MainContent_MainContent_Img2" style="margin-top: 1px" alt="Crash report uploaded page"></a>
</div>
</div>
<div data-slidr="slide3" class="slide" style="display: block; visibility: hidden; position: absolute; opacity: 0; z-index: 0; pointer-events: none; backface-visibility: hidden; transform-style: preserve-3d;">
<div class="slidetext"> In the main dashboard of your application you can see overall crash statistics. <a href="AppVersion.aspx?AppVersionID=2&Login=guest" id="ctl00_ctl00_MainContent_MainContent_A3" target="_blank">Open that page</a>
</div>
<div class="slideimg">
<a href="AppVersion.aspx?AppVersionID=2&Login=guest">
<img src="Images/demo-app-window.png" id="ctl00_ctl00_MainContent_MainContent_Img3" style="margin-top: 1px" alt="Application main page"></a>
</div>
</div>
<div data-slidr="slide4" class="slide" style="display: block; visibility: hidden; position: absolute; opacity: 0; z-index: 0; pointer-events: none; backface-visibility: hidden; transform-style: preserve-3d;">
<div class="slidetext"> Each problem is a collection of similar memory dump groups and a memory dump group is a collection of the reports with same stack.
<a href="Problem.aspx?ProblemID=10&Login=guest" id="ctl00_ctl00_MainContent_MainContent_A4" target="_blank">Open that page</a>
</div>
<div class="slideimg">
<a href="Problem.aspx?ProblemID=10&Login=guest" id="ctl00_ctl00_MainContent_MainContent_A6" target="_blank">
<img src="Images/demo-problem-window.png" id="ctl00_ctl00_MainContent_MainContent_Img4" style="margin-top: 1px" alt="Problem main page"></a>
</div>
</div>
<div data-slidr="slide5" class="slide" style="display: block; visibility: hidden; position: absolute; opacity: 0; z-index: 0; pointer-events: none; backface-visibility: hidden; transform-style: preserve-3d;">
<div class="slidetext"> You can see some details about each error report. <a href="DumpGroup.aspx?DumpGroupID=13&Login=guest" id="ctl00_ctl00_MainContent_MainContent_A5" target="_blank">Open that page</a>
</div>
<div class="slideimg">
<a href="DumpGroup.aspx?DumpGroupID=13&Login=guest" id="ctl00_ctl00_MainContent_MainContent_A7" target="_blank">
<img src="Images/demo-dumpgroup-window.png" id="ctl00_ctl00_MainContent_MainContent_Img5" style="margin-top: 1px" alt="Dump group main page"></a>
</div>
</div>
<div data-slidr="slide6" class="slide" style="display: block; visibility: hidden; position: absolute; opacity: 0; z-index: 0; pointer-events: none; backface-visibility: hidden; transform-style: preserve-3d;">
<div class="slidetext"> Besides stack a <a href="http://en.wikipedia.org/wiki/Core_dump" target="_blank">memory
dump</a> is available for each crash report, which can significantly help to investigate and fix a bug. <strong>Analyzing a memory dump</strong> is similar to debugging an application that was paused in a breakpoint. Difference
is that you cannot continue execution and due to optimization extracting local variables is not so easy. You can <a href="http://msdn.microsoft.com/en-us/library/d5zhxt22.aspx" target="_blank">
analyze the memory dumps in Visual Studio</a> exactly the same way as you debug an application. But it is recommended to use <a href="http://en.wikipedia.org/wiki/WinDbg" target="_blank">WinDbg</a> since there are a lot of tools to
dissect a dump. </div>
<div class="slideimg">
<a href="Images/demo-dump-full.png" target="_blank">
<img src="Images/demo-dump.png" id="ctl00_ctl00_MainContent_MainContent_Img6" style="margin-top: 1px" alt="Learning dump in WinDBG"></a>
</div>
</div>
<div data-slidr="slide7" class="slide" style="display: block; visibility: hidden; position: absolute; opacity: 0; z-index: 0; pointer-events: none; backface-visibility: hidden; transform-style: preserve-3d;">
<div class="slidetext"> You can reproduce all steps above yourself. Just run <a href="https://drdump.com/public/SampleApp/SampleAppSetup.msi" target="_blank">Sample Application</a> to generate crash reports and visit <a href="Applications.aspx?ClientID=sample&Login=guest" id="ctl00_ctl00_MainContent_MainContent_A8">Doctor Dump
Sample App project</a> under Guest account and browse the problems and crash reports. </div>
<div class="slideimg">
<a href="Applications.aspx?ClientID=sample&Login=guest" id="ctl00_ctl00_MainContent_MainContent_A9" target="_blank">
<img src="Images/final-slide.jpg" id="ctl00_ctl00_MainContent_MainContent_Img7" style="margin-top: 1px" alt="Demo tour"></a>
</div>
</div>
<aside id="how_it_works-breadcrumbs" class="" style="opacity: 1; z-index: 3; pointer-events: none; visibility: visible; animation: 0.4s ease-out 0s 1 normal none running slidr-fade-in;">
<ul class="slidr-breadcrumbs">
<li class="normal active" data-slidr-breadcrumbs="slide1"></li>
<li class="normal" data-slidr-breadcrumbs="slide2"></li>
<li class="normal" data-slidr-breadcrumbs="slide3"></li>
<li class="normal" data-slidr-breadcrumbs="slide4"></li>
<li class="normal" data-slidr-breadcrumbs="slide5"></li>
<li class="normal" data-slidr-breadcrumbs="slide6"></li>
<li class="normal" data-slidr-breadcrumbs="slide7"></li>
</ul>
</aside>
<aside id="how_it_works-control" class="border breadcrumbs" style="opacity: 1; z-index: 2; visibility: visible; pointer-events: none; animation: 0.4s ease-out 0s 1 normal none running slidr-fade-in;">
<div class="slidr-control up disabled" data-slidr-control="up"></div>
<div class="slidr-control down disabled" data-slidr-control="down"></div>
<div class="slidr-control left disabled" data-slidr-control="left"></div>
<div class="slidr-control right" data-slidr-control="right"></div>
</aside>
</div>
<h2> Features</h2>
<p> Here is the list of Doctor Dump <strong>crash reporting system</strong> supported features:</p>
<ul>
<li>Uploads, parses and stores your <strong>crash reports</strong></li>
<li>Provides <strong>full memory dump</strong> for difficult bugs debugging</li>
<li>Effectively groups similar reports into problems</li>
<li>It is possible to set an URL for each bug that will be opened when that report will be uploaded</li>
<li>Supports multiple applications and their versions</li>
<li><strong>Crash statistics</strong></li>
<li>Problems search</li>
<li>May integrate with your bug tracking system</li>
<li>Role based security model</li>
<li>Channel secured by SSL protocol</li>
<li>Effective for huge applications, millions of end users and millions of reports</li>
<li>Cloud based service - fast setup and zero maintence cost</li>
</ul>
<h3> Supported platforms</h3>
<ul>
<li><strong>Microsoft Windows</strong> XP and above, native x86/x64 code, compiled with debug symbol information in .PDB or .DBG file format (Microsoft <strong>C++</strong> Compiler, Intel C++ Compiler, MASM).</li>
<li>Managed <strong>Microsoft .NET Framework</strong> code is planned.</li>
</ul>
<div class="text-center">
<a href="/integrate-crash-reporting-to-windows-cpp-application" class="btn btn-lg btn-primary" style="color: White">Integrate your application with Doctor Dump crash reporting system</a>
</div> <script type="text/javascript" src="/Scripts/slidr.min.js"></script>
<script type="text/javascript">
slidr.create('how_it_works', {
breadcrumbs: true,
//controls: 'corner',
//fade: true,
keyboard: true,
overflow: true,
pause: false,
theme: '#222',
touch: true,
}).add('h', ['slide1', 'slide2', 'slide3', 'slide4', 'slide5', 'slide6', 'slide7'], 'fade').start();
</script>
</div>
</div>
<aside>
<div id="contactModal" class="modal fade">
<div class="modal-dialog">
<div class="modal-content">
<div class="modal-header">
<button type="button" class="close" data-dismiss="modal" aria-hidden="true"> ×</button>
<h4 class="modal-title">Contact</h4>
</div>
<div class="modal-body">
<div class="form-horizontal">
<div class="form-group">
<label for="ctl00_ctl00_ContactFrom" id="ctl00_ctl00_ContactFromLabel" class="control-label col-xs-2">From</label>
<div class="col-xs-10">
<input name="ctl00$ctl00$ContactFrom" type="text" id="ctl00_ctl00_ContactFrom" class="form-control" placeholder="John Smith">
</div>
</div>
</div>
<div class="form-horizontal">
<div class="form-group">
<label for="ctl00_ctl00_ContactEmail" id="ctl00_ctl00_ContactEmailLabel" class="control-label col-xs-2">Email</label>
<div class="col-xs-10">
<input name="ctl00$ctl00$ContactEmail" type="text" id="ctl00_ctl00_ContactEmail" class="form-control" placeholder="John.Smith@company.com">
</div>
</div>
</div>
<div class="form-horizontal">
<div class="form-group">
<label class="control-label col-xs-2"> To</label>
<div class="col-xs-10">
<p class="form-control-static">
<a href="mailto:info@drdump.com">info@drdump.com</a>
</p>
</div>
</div>
</div>
<div class="form-horizontal">
<div class="form-group">
<label for="ctl00_ctl00_ContactMessage" id="ctl00_ctl00_ContactMessageLabel" class="control-label col-xs-2">Message</label>
<div class="col-xs-10">
<textarea name="ctl00$ctl00$ContactMessage" id="ctl00_ctl00_ContactMessage" class="form-control" rows="10" cols="100" placeholder="Message"></textarea>
<span id="ctl00_ctl00_ContactMessageRequiredValidator" class="help-block" style="color:Red;display:none;">Please enter some message</span>
</div>
</div>
</div>
<div class="form-horizontal">
<div class="form-group">
<div class="col-xs-2"></div>
<div class="col-xs-10">
<input id="MainPrivacyPolicyCheckBox" type="checkbox" name="ctl00$ctl00$MainPrivacyPolicyCheckBox">I have read and accept <a href="/privacy-policy" target="_blank">Privacy Policy</a>
</div>
</div>
</div>
<input type="hidden" name="ctl00$ctl00$HiddenDate" id="ctl00_ctl00_HiddenDate" value="638684838138125438">
<input type="hidden" name="ctl00$ctl00$HiddenAgent" id="ctl00_ctl00_HiddenAgent" value="1947017104">
<input type="hidden" name="ctl00$ctl00$IsWebdriver" id="ctl00_ctl00_IsWebdriver" value="0">
</div>
<div class="modal-footer">
<button type="button" class="btn btn-default" data-dismiss="modal"> Close</button>
<input type="submit" name="ctl00$ctl00$ContactSubmit" value="Submit" id="ContactSubmit" disabled="disabled" class="btn btn-primary">
</div>
</div>
</div>
</div>
</aside>
<div class="push-footer">
</div>
<script type="text/javascript">
//<![CDATA[
var Page_Validators = new Array(document.getElementById("ctl00_ctl00_ContactMessageRequiredValidator"));
//]]>
</script>
<script type="text/javascript">
//<![CDATA[
var ctl00_ctl00_ContactMessageRequiredValidator = document.all ? document.all["ctl00_ctl00_ContactMessageRequiredValidator"] : document.getElementById("ctl00_ctl00_ContactMessageRequiredValidator");
ctl00_ctl00_ContactMessageRequiredValidator.controltovalidate = "ctl00_ctl00_ContactMessage";
ctl00_ctl00_ContactMessageRequiredValidator.errormessage = "Please enter some message";
ctl00_ctl00_ContactMessageRequiredValidator.display = "Dynamic";
ctl00_ctl00_ContactMessageRequiredValidator.validationGroup = "ContactForm";
ctl00_ctl00_ContactMessageRequiredValidator.evaluationfunction = "RequiredFieldValidatorEvaluateIsValid";
ctl00_ctl00_ContactMessageRequiredValidator.initialvalue = "";
//]]>
</script>
<script type="text/javascript">
//<![CDATA[
var Page_ValidationActive = false;
if (typeof(ValidatorOnLoad) == "function") {
ValidatorOnLoad();
}
function ValidatorOnSubmit() {
if (Page_ValidationActive) {
return ValidatorCommonOnSubmit();
} else {
return true;
}
}
//]]>
</script>
</form>Text Content
Doctor Dump By Idol Software Toggle navigation * Features * Integration * Testimonials * Demo tour * Login * Signup ABOUT DOCTOR DUMP CRASH REPORTING SYSTEM Doctor Dump is a free crash reporting and memory dump analyzing service. It collects, organizes and stores crash reports from your customers, gives you all necessary data to fix the bug and provides your users with solution/workaround to the problem immediately after the crash. HOW IT WORKS First of all you need to integrate the Doctor Dump crash reporting library into your Windows C++ application. After that when a crash or unhandled exception occurs it will be caught and a report about the bug will be sent to the Doctor Dump, that will analyze the report and using problem footprint (that usually is a stack trace) put it to a group of exact same issues. Similar groups caused by one reason (one buggy function can be called by different callers, so stacks will differ) form a problem that is fixing unit. After the crash report has been uploaded user may be directed to a customized web page about that problem where may exist some information, for example a link to a version where this bug has been fixed or some workaround. Or default page may be shown, where user can see the state of the bug and ID of his report which he can use when communicate with support. Open that page In the main dashboard of your application you can see overall crash statistics. Open that page Each problem is a collection of similar memory dump groups and a memory dump group is a collection of the reports with same stack. Open that page You can see some details about each error report. Open that page Besides stack a memory dump is available for each crash report, which can significantly help to investigate and fix a bug. Analyzing a memory dump is similar to debugging an application that was paused in a breakpoint. Difference is that you cannot continue execution and due to optimization extracting local variables is not so easy. You can analyze the memory dumps in Visual Studio exactly the same way as you debug an application. But it is recommended to use WinDbg since there are a lot of tools to dissect a dump. You can reproduce all steps above yourself. Just run Sample Application to generate crash reports and visit Doctor Dump Sample App project under Guest account and browse the problems and crash reports. * * * * * * * FEATURES Here is the list of Doctor Dump crash reporting system supported features: * Uploads, parses and stores your crash reports * Provides full memory dump for difficult bugs debugging * Effectively groups similar reports into problems * It is possible to set an URL for each bug that will be opened when that report will be uploaded * Supports multiple applications and their versions * Crash statistics * Problems search * May integrate with your bug tracking system * Role based security model * Channel secured by SSL protocol * Effective for huge applications, millions of end users and millions of reports * Cloud based service - fast setup and zero maintence cost SUPPORTED PLATFORMS * Microsoft Windows XP and above, native x86/x64 code, compiled with debug symbol information in .PDB or .DBG file format (Microsoft C++ Compiler, Intel C++ Compiler, MASM). * Managed Microsoft .NET Framework code is planned. Integrate your application with Doctor Dump crash reporting system × CONTACT From Email To info@drdump.com Message Please enter some message I have read and accept Privacy Policy Close About | Contact | Privacy Policy