[Bug mi/19087] New: "-data-read-memory-byte --thread X..." does not restore the current thread

[Bug mi/19087] New: "-data-read-memory-byte --thread X..." does not restore the current thread

[simon.marchi at ericsson dot com]

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

            Bug ID: 19087
           Summary: "-data-read-memory-byte --thread X..." does not
                    restore the current thread
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: mi
          Assignee: unassigned at sourceware dot org
          Reporter: simon.marchi at ericsson dot com
  Target Milestone: ---

Thread 1 is selected initially. "-data-read-memory-bytes --thread 2..." is
issued. Thread 2 is now selected, whereas thread 1 should still be the current
thread.


(gdb) 
info threads
&"info threads\n"
~"  Id   Target Id         Frame \n"
~"  6    Thread 0x7fffd9df5700 (LWP 25030) \"pool\"
pthread_cond_timedwait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238\n"
~"  4    Thread 0x7fffdadf7700 (LWP 25028) \"gmain\" 0x00007ffff5b8512d in poll
() at ../sysdeps/unix/syscall-template.S:81\n"
~"  3    Thread 0x7fffeec4d700 (LWP 25027) \"gdbus\" 0x00007ffff5b8512d in poll
() at ../sysdeps/unix/syscall-template.S:81\n"
~"  2    Thread 0x7fffef44e700 (LWP 25026) \"dconf worker\" 0x00007ffff5b8512d
in poll () at ../sysdeps/unix/syscall-template.S:81\n"
~"* 1    Thread 0x7ffff7fb19c0 (LWP 25022) \"gnome-calculato\"
0x00007ffff5b8512d in poll () at ../sysdeps/unix/syscall-template.S:81\n"
^done
(gdb) 
-data-read-memory-bytes --thread 2 0x400400 10
^done,memory=[{begin="0x0000000000400400",offset="0x0000000000000000",end="0x000000000040040a",contents="97a343224411081e88b8"}]
(gdb) 
info thread
&"info thread\n"
~"  Id   Target Id         Frame \n"
~"  6    Thread 0x7fffd9df5700 (LWP 25030) \"pool\"
pthread_cond_timedwait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238\n"
~"  4    Thread 0x7fffdadf7700 (LWP 25028) \"gmain\" 0x00007ffff5b8512d in poll
() at ../sysdeps/unix/syscall-template.S:81\n"
~"  3    Thread 0x7fffeec4d700 (LWP 25027) \"gdbus\" 0x00007ffff5b8512d in poll
() at ../sysdeps/unix/syscall-template.S:81\n"
~"* 2    Thread 0x7fffef44e700 (LWP 25026) \"dconf worker\" 0x00007ffff5b8512d
in poll () at ../sysdeps/unix/syscall-template.S:81\n"
~"  1    Thread 0x7ffff7fb19c0 (LWP 25022) \"gnome-calculato\"
0x00007ffff5b8512d in poll () at ../sysdeps/unix/syscall-template.S:81\n"
^done
(gdb)

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

[Bug mi/19087] "-data-read-memory-byte --thread X..." does not restore the current thread

[simon.marchi at ericsson dot com]

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

--- Comment #1 from Simon Marchi <simon.marchi at ericsson dot com> ---
Actually, all MI commands that specify --thread or --thread-group do not
restore the current inferior/thread.  Is it by design?  I guess not, that would
be a strange side-effect...

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

[Bug mi/19087] "-data-read-memory-byte --thread X..." does not restore the current thread

[ssbssa at sourceware dot org]

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

Hannes Domani <ssbssa at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ssbssa at sourceware dot org
         Resolution|---                         |DUPLICATE
             Status|NEW                         |RESOLVED

--- Comment #2 from Hannes Domani <ssbssa at sourceware dot org> ---
Dup.

*** This bug has been marked as a duplicate of bug 20684 ***

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