[Bug gdb/16896] New: GDB crash after Set next statement and Step over (AVR8)

["vidarlsw at hotmail dot com" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=16896

            Bug ID: 16896
           Summary: GDB crash after Set next statement and Step over
                    (AVR8)
           Product: gdb
           Version: 7.7
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: vidarlsw at hotmail dot com

Created attachment 7579
  --> https://sourceware.org/bugzilla/attachment.cgi?id=7579&action=edit
Atmel Studio project for ATmega2560

Environment:
Atmel Studio 6.2 beta (6.2.993), debugging AVR8 using GDB (project - properties 
- Advanced - "Use GDB", and "Override current GDB path").

Reproduced with ATMega2560 target and simulator.

Fails with these GDB versions:
- latest version of GDB from Embecosm (updated April 24, 2014 from
https://github.com/embecosm/avr-binutils-gdb.git)
- latest version of GDB from Sourceware (updated April 24, 2014 from
gdb-7.7-branch in http://sourceware.org/git/binutils-gdb.git)

Description
Reproducible crash when debugging with GDB.

See attached ATMega2560 project, screen-dump and Atmel Studio backend log file.
Reproducible sequence:
ï    Start debugging and run to breakpoint (at line 55).
ï    Move cursor to line 56 and choose Set next statement.
==> Set next statement do not work (yellow marker for Show next statement does
not move)
ï    Press step over.
==> GDB crash
Error message from GDB:
gdb ~"../../gdb/gdb/infrun.c:1948: internal-error: resume: Assertion
`pc_in_thread_step_range (pc, tp)' failed.\nA problem internal to GDB has been
detected,\nfurther debugging may prove unreliable.\nQuit this debugging
session? "

When running Atmel Studio 6.2 beta using included GDB version (no override for
GDB path) then GDB do not crash. But also in this case Set next statement do
not work.

-- 
You are receiving this mail because:
You are on the CC list for the bug.