[Bug gdb/18274] gdb crashed when I move my mouse to a const string

["305128674 at qq dot com" <sourceware-bugzilla@sourceware.org>]

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

--- Comment #2 from jiangtaijin <305128674 at qq dot com> ---
(In reply to Pedro Alves from comment #1)
> On 04/17/2015 01:24 PM, 305128674 at qq dot com wrote:
> > 
> > the gdb i used is compiler by myself. here is the version infomation:
> 
> I believe this has been fixed in more recent versions of gdb.
> 
> > C:\Users\Administrator>arm-sylixos-eabi-gdb --version
> > GNU gdb (SylixOS Toolchain for ARM Embedded Processors) 7.8.0.20150304-cvs
> 
> Could you try the 7.9 branch, and/or master?
> 
> > Copyright (C) 2014 Free Software Foundation, Inc.

I tried the gdb verions 7.9， the bug remain。 gdb still crashed。

the new version information is:
D:\qtcreator-gdb-7.9-mingw32_nt-6.1-i686>gdb-arm-sylixosqt-eabi.exe --version
Python Exception <type 'exceptions.ImportError'> No module named gdb:
D:\qtcreator-gdb-7.9-mingw32_nt-6.1-i686\gdb-arm-sylixosqt-eabi.exe: warning:
Could not load the Python gdb module from `d:\usr\local\share\gdb/python'.
Limited Python support is available from the _gdb module.
Suggest passing --data-directory=/path/to/gdb/data-directory.

GNU gdb (GDB) 7.9
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "--host=i686-pc-mingw32
--target=arm-sylixosqt-eabi".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-17888-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Apr 21 08:01:08 2015
Return-Path: <gdb-prs-return-17888-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 115634 invoked by alias); 21 Apr 2015 08:01:08 -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 114264 invoked by uid 48); 21 Apr 2015 08:01:07 -0000
From: "palves at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/18274] gdb crashed when I move my mouse to a const string
Date: Tue, 21 Apr 2015 08:01: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.8
X-Bugzilla-Keywords:
X-Bugzilla-Severity: critical
X-Bugzilla-Who: palves at redhat dot com
X-Bugzilla-Status: WAITING
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc
Message-ID: <bug-18274-4717-BL7YbITiPz@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-18274-4717@http.sourceware.org/bugzilla/>
References: <bug-18274-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: 2015-q2/txt/msg00082.txt.bz2
Content-length: 818

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

Pedro Alves <palves at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |WAITING
                 CC|                            |palves at redhat dot com

--- Comment #3 from Pedro Alves <palves at redhat dot com> ---
OK, thanks.

In order to understand what's going on, we'll need:

- "set debug infrun 1 + set debug remote 1" logs (both enabled at the same
time).

- ideally, get eclipse out of the equation, and to reproduce this with gdb
alone.  Enable Eclipse gdb logging, to find the MI traffic between Eclipse and
gdb.

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