Support:How To Get Toolpack Crash Dump: Difference between revisions
(Created page with 'When a Toolpack application (release 2.5 and up) crashes, it automatically generates a debug dump that can be sent to TelcoBridges for analysis. These dumps are located here: <br…') |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
When a Toolpack application (release 2.5 and up) crashes, it automatically generates a debug dump that can be sent to TelcoBridges for analysis. These dumps are located here: | When a Toolpack application (release 2.5 and up) crashes, it automatically generates a debug dump that can be sent to TelcoBridges for analysis. These dumps are located here: | ||
''/lib/tb/toolpack/setup/12358/2.5/apps/[crashed application]/dumps/*.dmp'' | |||
(Note: "12358" may vary on your setup, as well as "2.5" if you're running more recent release such as 2.6, for example) | |||
Please provide any .dmp file found in that folder (or at least the most recent) to TelcoBridges. We will be able, from this dump, to get the call stack of the crashed thread, and the file/line where the crash occurred, which greatly helps debugging. | Please provide any .dmp file found in that folder (or at least the most recent) to TelcoBridges. We will be able, from this dump, to get the call stack of the crashed thread, and the file/line where the crash occurred, which greatly helps debugging. | ||
Latest revision as of 08:05, 17 December 2010
When a Toolpack application (release 2.5 and up) crashes, it automatically generates a debug dump that can be sent to TelcoBridges for analysis. These dumps are located here:
/lib/tb/toolpack/setup/12358/2.5/apps/[crashed application]/dumps/*.dmp (Note: "12358" may vary on your setup, as well as "2.5" if you're running more recent release such as 2.6, for example)
Please provide any .dmp file found in that folder (or at least the most recent) to TelcoBridges. We will be able, from this dump, to get the call stack of the crashed thread, and the file/line where the crash occurred, which greatly helps debugging.