public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug gdb/16896] New: GDB crash after Set next statement and Step over (AVR8)
@ 2014-05-02 11:09 vidarlsw at hotmail dot com
  2014-05-02 11:46 ` [Bug gdb/16896] " vidarlsw at hotmail dot com
                   ` (3 more replies)
  0 siblings, 4 replies; 5+ messages in thread
From: vidarlsw at hotmail dot com @ 2014-05-02 11:09 UTC (permalink / raw)
  To: gdb-prs

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 4281 bytes --]

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.
>From gdb-prs-return-15660-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri May 02 11:45:40 2014
Return-Path: <gdb-prs-return-15660-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 11904 invoked by alias); 2 May 2014 11:45:39 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 11878 invoked by uid 48); 2 May 2014 11:45:39 -0000
From: "vidarlsw at hotmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/16896] GDB crash after Set next statement and Step over
 (AVR8)
Date: Fri, 02 May 2014 11:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: gdb
X-Bugzilla-Version: 7.7
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vidarlsw at hotmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-16896-4717-bC3zXnS50s@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-16896-4717@http.sourceware.org/bugzilla/>
References: <bug-16896-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-q2/txt/msg00166.txt.bz2
Content-length: 321

https://sourceware.org/bugzilla/show_bug.cgi?id\x16896

--- Comment #1 from vidarl <vidarlsw at hotmail dot com> ---
Created attachment 7581
  --> https://sourceware.org/bugzilla/attachment.cgi?idu81&actioníit
Atmel Studio backend logfile

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


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug gdb/16896] GDB crash after Set next statement and Step over (AVR8)
  2014-05-02 11:09 [Bug gdb/16896] New: GDB crash after Set next statement and Step over (AVR8) vidarlsw at hotmail dot com
@ 2014-05-02 11:46 ` vidarlsw at hotmail dot com
  2014-05-08 17:39 ` [Bug remote/16896] " pierre.langlois at embecosm dot com
                   ` (2 subsequent siblings)
  3 siblings, 0 replies; 5+ messages in thread
From: vidarlsw at hotmail dot com @ 2014-05-02 11:46 UTC (permalink / raw)
  To: gdb-prs

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

--- Comment #2 from vidarl <vidarlsw at hotmail dot com> ---
Created attachment 7582
  --> https://sourceware.org/bugzilla/attachment.cgi?id=7582&action=edit
Screendump from Atmel Studio

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


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug remote/16896] GDB crash after Set next statement and Step over (AVR8)
  2014-05-02 11:09 [Bug gdb/16896] New: GDB crash after Set next statement and Step over (AVR8) vidarlsw at hotmail dot com
  2014-05-02 11:46 ` [Bug gdb/16896] " vidarlsw at hotmail dot com
@ 2014-05-08 17:39 ` pierre.langlois at embecosm dot com
  2014-05-08 17:45 ` pierre.langlois at embecosm dot com
  2014-06-13 10:06 ` pierre.langlois at embecosm dot com
  3 siblings, 0 replies; 5+ messages in thread
From: pierre.langlois at embecosm dot com @ 2014-05-08 17:39 UTC (permalink / raw)
  To: gdb-prs

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

Pierre Langlois <pierre.langlois at embecosm dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Target|                            |avr
                 CC|                            |pierre.langlois at embecosm dot co
                   |                            |m
          Component|gdb                         |remote
           Assignee|unassigned at sourceware dot org   |pierre.langlois at embecosm dot co
                   |                            |m

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


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug remote/16896] GDB crash after Set next statement and Step over (AVR8)
  2014-05-02 11:09 [Bug gdb/16896] New: GDB crash after Set next statement and Step over (AVR8) vidarlsw at hotmail dot com
  2014-05-02 11:46 ` [Bug gdb/16896] " vidarlsw at hotmail dot com
  2014-05-08 17:39 ` [Bug remote/16896] " pierre.langlois at embecosm dot com
@ 2014-05-08 17:45 ` pierre.langlois at embecosm dot com
  2014-06-13 10:06 ` pierre.langlois at embecosm dot com
  3 siblings, 0 replies; 5+ messages in thread
From: pierre.langlois at embecosm dot com @ 2014-05-08 17:45 UTC (permalink / raw)
  To: gdb-prs

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

--- Comment #3 from Pierre Langlois <pierre.langlois at embecosm dot com> ---
Hello Vidar,

I was able to reproduce this bug on linux using a gdbserver that purposely
return an error packet when trying to set the program counter. As we can see
from the log you've sent:

~~~
03 59 10 273: prx gdbproxy: packet received: P22=c0010000
03 59 10 273: prx atmelgdbproxy: proxy_write_single_register(34, 0x1C0)
03 59 10 273: prx gdbproxy: sending packet: 7 bytes: $E00#a5...
~~~

I have submitted a patch in order to discuss this issue upstream:
https://sourceware.org/ml/gdb-patches/2014-05/msg00083.html

Best,

Pierre

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


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug remote/16896] GDB crash after Set next statement and Step over (AVR8)
  2014-05-02 11:09 [Bug gdb/16896] New: GDB crash after Set next statement and Step over (AVR8) vidarlsw at hotmail dot com
                   ` (2 preceding siblings ...)
  2014-05-08 17:45 ` pierre.langlois at embecosm dot com
@ 2014-06-13 10:06 ` pierre.langlois at embecosm dot com
  3 siblings, 0 replies; 5+ messages in thread
From: pierre.langlois at embecosm dot com @ 2014-06-13 10:06 UTC (permalink / raw)
  To: gdb-prs

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

Pierre Langlois <pierre.langlois at embecosm dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #4 from Pierre Langlois <pierre.langlois at embecosm dot com> ---
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commit;h=b94ade42840d1b0fbf818db49d98da9ba80c1d53

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


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2014-06-13 10:06 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-05-02 11:09 [Bug gdb/16896] New: GDB crash after Set next statement and Step over (AVR8) vidarlsw at hotmail dot com
2014-05-02 11:46 ` [Bug gdb/16896] " vidarlsw at hotmail dot com
2014-05-08 17:39 ` [Bug remote/16896] " pierre.langlois at embecosm dot com
2014-05-08 17:45 ` pierre.langlois at embecosm dot com
2014-06-13 10:06 ` pierre.langlois at embecosm dot com

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).