Search
Company
Management
How we work
Our Skills
Project Flow
Development
QA
QA process
QA process with lack of documentation
Quality Control
Security
Services
Software development
Quality assurance
Mobile software development
Web services for small businesses
Consulting
Case Studies
Alphabetically
3D Landscape Visualization
Comprehensive Organizer for PalmOS
Advanced SMS delivery system
ASP.NET Visual Permission Manager
Automatic System Update Software
BugSnapshort
FireFox Add-on "FoxFind"
FileMD Project
Geo IP
GeoRSS
Social Network Portal
Mobile Inventory
Public City Library Registry Manager
Switch Testing Framework Library
The PocketPC developer framework
Building industry intranet portal
Estate agency portal on Sharepoint 2007
Web Cast
Voice Cast
Investor's Portal
Change Manager
Ecora web site
PCDB
PM
RC
Mobile Call Manager
Mobile Learning Portal
Insurance company internet office on Sharepoint CMS
Call-center Software for Collection Agency
Software Development
3D Landscape Visualization
Investor's Portal
Advanced SMS delivery system
ASP.NET Visual Permission Manager
Automatic System Update Software
BugSnapshort
Call-center Software for Collection Agency
FireFox Add-on "FoxFind"
FileMD Project
Geo IP
GeoRSS
Social Network Portal
Mobile Inventory
Public City Library Registry Manager
The PocketPC developer framework
Voice Cast
Web Cast
Building industry intranet portal
Estate agency portal on Sharepoint 2007
Mobile Call Manager
Mobile Learning Portal
Insurance company internet office on Sharepoint CMS
Comprehensive Organizer for PalmOS
Quality Assurance
Change Manager
Ecora web site
PCDB
PM
RC
Switch Testing Framework Library
Careers
Contact
How we work
Our Skills
Project Flow
Quality Control
Security
See Also
Company
Services
BugSnapshort
BugSnapshort is a tool used to analyze what caused exceptions in your application. It helps you to find and analyze the reason of your application fault without asking a user a huge number of questions. By supporting (reading) dmp-files, BugSnapshort allows you to work with files which were created by the system.
Features available in BugSnapshort
Reads dmp-files and displays their contents;
Displays exception stack;
Displays stack for each thread;
Points you to the place in code where exception occurred;
Displays information about user's machine environment;
Supports reading of debug information;
Supports reading of exported functions;
Displays information about modules that were loaded into the applications address space when it raised exception.
Support for 32-bit Windows applications compiled with
Microsoft Visual C++ (v. 5, 6, 7.0 and 7.1)
Microsoft Visual FoxPro 6.0
Microsoft Visual Basic 6.0
Borland Delphi (v. 4, 5, 6 and 7)
Borland C++Builder (v. 4, 5 and 6)
Borland C++ (v. 4.5 and 5.x)
Intel C++
What is the difference between BugSnapshort and testing tools? Testing tools check the base functionality of the application, which allows a developer to identify the root cause of errors during the development process. BugSnapshort helps you to find and analyze the cause of the application's fault when minimum information about failure is available (i.e. no exact steps to reproduce the problem exist, specific conditions and specific data are unknown). Tests allow checking how the application works at the developer's office. BugSnapshort provides information on what happened to the application when a user was working with it.
In the fast developing world of programming it is vitally important to have complete information about the application's fault, but no tool can present this information. Usually a support team asks a lot of questions to a customer to get all the information needed to reproduce the application's fault and this takes a lot of time. BugSnapshort can be your primary tool to find, locate and fix the application's fault cause.
BugSnapshort can answer large number of questions your support team would ask clients when application failure is reported. Some of them are:
How did my application fail on the target user's machine?
What was happening to the application when the exception occurred?
What was the state of application at the time the exception has been raised?
What is the exception stack?
What module raised the exception?
What was machine environment when the exception occurred?
What is hardware configuration on a target user's machine?
Company
|
How we work
|
Services
|
Case studies
|
Carreers
|
Contact
Copyright 2000-2010 Smartech. All right reserved.