Link Details

Link 1105649 thumbnail
User 454796 avatar

By Andrey_Karpov_2009
Submitted: Feb 03 2014 / 01:15

It is quite common to have a program stopped in the debugger due to a crash or assertion caused by an object being in a bad state, and to track down the problem, you need to figure out how it got that way. In many cases, the call stack of the object's creation can provide valuable clues, but trying to get that call stack can be a significant chore. The most obvious technique, setting a breakpoint at the object's constructor, can become cumbersome when you have a large number of objects of the same type being created, only one of which, has a problem.
  • 1
  • 0
  • 39
  • 47

Add your comment

Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Voters For This Link (1)

Voters Against This Link (0)

    Java EE7
    Written by: Andrew Lee Rubinger
    Featured Refcardz: Top Refcardz:
    1. Design Patterns
    2. OO JS
    3. Cont. Delivery
    4. CI Patterns
    5. CI Tools
    1. Spring Integration
    2. Git
    3. Regex
    4. Java
    5. REST