public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "305128674 at qq dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/18274] New: gdb crashed when I move my mouse point to a const string
Date: Fri, 17 Apr 2015 12:24:00 -0000	[thread overview]
Message-ID: <bug-18274-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 18274
           Summary: gdb crashed when I move my mouse point to a const
                    string
           Product: gdb
           Version: 7.8
            Status: NEW
          Severity: critical
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: 305128674 at qq dot com

Hello, I'm debugging remote program with eclipse and gdb. when i move my mouse
pointer on an const string like "hello world"(some thing like char a[]="hello
world"), then gdb crashed.

the gdb i used is compiler by myself. here is the version infomation:
C:\Users\Administrator>arm-sylixos-eabi-gdb --version
GNU gdb (SylixOS Toolchain for ARM Embedded Processors) 7.8.0.20150304-cvs
Copyright (C) 2014 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-w64-mingw32 --target=arm-sylixos-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".

gdb error is:
/home/user/toolchain/gcc-arm-sylixos-eabi-4_9-2015q2-20150411/src/gdb/gdb/infrun.c:6229:
internal-error: normal_stop: Assertion `get_frame_type (frame) == DUMMY_FRAME'
failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) [answered Y; input not from terminal]
/home/user/toolchain/gcc-arm-sylixos-eabi-4_9-2015q2-20150411/src/gdb/gdb/infrun.c:6229:
internal-error: normal_stop: Assertion `get_frame_type (frame) == DUMMY_FRAME'
failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.


I open the remote debug log, it output:
Sending packet: $Pe=748201c0#bb...Ack
Packet received: 
Packet P (set-register) is NOT supported
Sending packet:
$G0100000014706b24707908c0748201c0a84f03c0c0e0d62050a702c010736b240100000058e1d62048736b2464e0d620e44f03c058e0d620748201c0888201c053000020#cc...Ack
Packet received: OK
Sending packet:
$G0e00000014706b24707908c0748201c0a84f03c0c0e0d62050a702c010736b240100000058e1d62048736b2464e0d620e44f03c058e0d620748201c0888201c053000020#00...Ack
Packet received: OK
Sending packet:
$G0e00000014706b24707908c0748201c0a84f03c0c0e0d62050a702c010736b240100000058e1d62048736b2464e0d620e44f03c050e0d620748201c0888201c053000020#f8...Ack
Packet received: OK
Sending packet:
$G0e00000014706b24707908c0748201c0a84f03c0c0e0d62050a702c010736b240100000058e1d62048736b2464e0d620e44f03c050e0d620748201c050bc02c053000020#49...Ack
Packet received: OK
Sending packet: $Z0,c0018274,4#df...Ack
Packet received: OK
Sending packet: $vCont;c#a8...Ack
Packet received: T05thread:4010023;
Sending packet: $g#67...Ack
Packet received:
787a08c00e000000008008c0787a08c0a84f03c0c0e0d62050a702c010736b240100000058e1d62048736b2464e0d6200400000058e0d620748201c0748201c053000020
Sending packet: $mc0018274,4#96...Ack
Packet received: fedeffe7
Sending packet: $z0,c0018274,4#ff...Ack
Packet received: 

This is a bug, please report it.  For instructions, see:
<http://www.gnu.org/software/gdb/bugs/>.


/home/user/toolchain/gcc-arm-sylixos-eabi-4_9-2015q2-20150411/src/gdb/gdb/infrun.c:6229:
internal-error: normal_stop: Assertion `get_frame_type (frame) == DUMMY_FRAME'
failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) [answered Y; input not from terminal]
/home/user/toolchain/gcc-arm-sylixos-eabi-4_9-2015q2-20150411/src/gdb/gdb/infrun.c:6229:
internal-error: normal_stop: Assertion `get_frame_type (frame) == DUMMY_FRAME'
failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
 I

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


             reply	other threads:[~2015-04-17 12:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-17 12:24 305128674 at qq dot com [this message]
2015-04-17 12:28 ` [Bug gdb/18274] " 305128674 at qq dot com
2015-04-17 12:29 ` [Bug gdb/18274] gdb crashed when I move my mouse " 305128674 at qq dot com
2015-04-20  8:55 ` palves at redhat dot com
2015-04-21  5:50 ` 305128674 at qq dot com
2015-04-21  9:30 ` 305128674 at qq dot com
2015-04-21 12:50 ` palves at redhat dot com
2015-04-21 14:48 ` 305128674 at qq dot com
2015-04-22  7:25 ` 305128674 at qq dot com
2015-04-22 10:38 ` palves at redhat dot com
2015-04-25  5:22 ` 305128674 at qq dot com
2015-04-25  5:24 ` 305128674 at qq dot com
2015-04-25  5:24 ` 305128674 at qq dot com
2015-04-25  5:34 ` 305128674 at qq dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-18274-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).