This is the mail archive of the
mailing list for the GDB project.
Re: DWARF is_stmt flag (revisited)
On Tue, Jun 16, 2009 at 11:39:05AM -0700, Cary Coutant wrote:
> Longer term, I think that gdb will need to record the is_stmt flag
> with each line table row, so that it can provide accurate pc -> line
> number mappings for optimized code, while still ignoring !is_stmt
> lines when setting breakpoints and single-stepping. The compiler will
> eventually need to start using the is_stmt flag when scheduling causes
> the line number to hop around, so that we don't stop multiple times on
> one line of code.
> Tested on x86_64. No new regressions with a compiler that does not set
> is_stmt == 0. OK for trunk?
> * dwarf2read.c (dwarf_decode_lines): Ignore rows where is_stmt is 0.
> Set basic_block to 0 after a special opcode.