This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/18274] gdb crashed when I move my mouse to a const string
- From: "palves at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Tue, 21 Apr 2015 15:28:36 +0000
- Subject: [Bug gdb/18274] gdb crashed when I move my mouse to a const string
- Auto-submitted: auto-generated
- References: <bug-18274-4717 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=18274
--- Comment #7 from Pedro Alves <palves at redhat dot com> ---
> 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.
--
You are receiving this mail because:
You are on the CC list for the bug.