[Bug mi/15863] New: -var-update if the program is not running crashes gdb

["dimitar.zhekov at gmail dot com" <sourceware-bugzilla at sourceware dot org>]

http://sourceware.org/bugzilla/show_bug.cgi?id=15863

            Bug ID: 15863
           Summary: -var-update if the program is not running crashes gdb
           Product: gdb
           Version: 7.6
            Status: NEW
          Severity: normal
          Priority: P2
         Component: mi
          Assignee: unassigned at sourceware dot org
          Reporter: dimitar.zhekov at gmail dot com
              Host: Linux xos4 3.10-2-686-pae #1 SMP Debian 3.10.5-1
                    (2013-08-07) i686 GNU/Linux
            Target: Linux xos4 3.10-2-686-pae #1 SMP Debian 3.10.5-1
                    (2013-08-07) i686 GNU/Linux

Steps to reproduce:

$ gdb --interpreter=mi ~/hello
=thread-group-added,id="i1"
~"Reading symbols from /home/build/hello..."

(gdb) -var-create - * main
^done,name="var1",numchild="0",value="{int (void)} 0x80483fc <main>",type="int
(void)",has_more="0"

(gdb) -data-evaluate-expression main
^done,value="{int (void)} 0x80483fc <main>"

(gdb) -var-update *
~"/build/gdb-CewkFW/gdb-7.6/gdb/thread.c:615: internal-error: is_thread_state:
Assertion `tp' failed.\nA problem internal to GDB has been detected,\nfurther
debugging may prove unreliable.\nQuit this debugging session? "
~"(y or n) "
y
Aborted (core dumped)

--

The program doesn't matter; any C or C++ program compiled with -g will do.

Evaluating main() doesn't make much sense, but it crashes on any global symbol.

Using @ or 0 for stack frame makes no difference.

-var-update works fine _while the program is running_, and crashes again if it
has been terminated.

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