Although a large number of different debugging tools are available, very few CS students use them in programming courses. Instead, they try to understand and correct their code by adding countless print statements. We identified several reasons for these observations: (1) novice programmers find the standard debugging tools too complicated, especially the representation of the current program state, (2) they find it difficult to trace a problem back to its origin, and (3) it is not yet possible to provide them with a visualization of data structures that corresponds to the representation used in the classroom. We address these problems with BugVis, an alternative debugging approach. We describe the concept and basic ideas below, since BugVis has not yet been fully realized.