------- Comment #5 from matz at gcc dot gnu dot org 2010-02-18 16:50 ------- That leaves 'c' which isn't printed, because the setup of c (a stackslot) is schedules to be part of the function call setup, the breakpoint is before that setup, and hence the location of 'c' does point to the correct one (namely its stackslot), but that one isn't initialized yet. One problem might be that there's no DEBUG_BIND insn generated for c at all. Or alternatively, once the stack slot initialization is moved down that no debug_insn is generated at it's original place to refer to the value 0.
-- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43077
