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] gdb crashed when I move my mouse to a const string
Date: Wed, 22 Apr 2015 07:25:00 -0000 [thread overview]
Message-ID: <bug-18274-4717-8TQXKuTq9P@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18274-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=18274
--- Comment #8 from jiangtaijin <305128674 at qq dot com> ---
(In reply to Pedro Alves from comment #7)
> > ok, I will try to run gdb alone.
> > but i don't kown what command to you use to simulate the mouse move to a const
> > string.
> > print is ok.
> > i use --interpretor mi to send the same cmd as eclipse, it show error also.
>
> I'd debug gdb, and put a breakpoint in call_function_by_hand. Then in the
> inferior gdb, issue the MI commands that trigger the bug. You'll probably
> find the backtrace shows value_allocate_space_in_inferior. I suspect that
> something around:
>
> (gdb) print "foo" + 1
>
> triggers the issue too. I'd try explict inferior function calls too:
>
> (gdb) print foo()
>
> And there's the possibility that bug really is MI varobj specific too.
>
> I'd run gdb under valgrind as well, in case this is caused by gdb memory
> corruption.
So, do you have some idea to avoid this issue, or i need to wait for a newer
gdb version?
i need to use gdb with eclipse.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2015-04-22 7:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 12:24 [Bug gdb/18274] New: gdb crashed when I move my mouse point " 305128674 at qq dot com
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 [this message]
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-8TQXKuTq9P@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).