[Bug remote/21852] New: Remote run without specifying a local binary crashes GDB

["simon.marchi at ericsson dot com" <sourceware-bugzilla at sourceware dot org>]

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

            Bug ID: 21852
           Summary: Remote run without specifying a local binary crashes
                    GDB
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: remote
          Assignee: unassigned at sourceware dot org
          Reporter: simon.marchi at ericsson dot com
  Target Milestone: ---

Start gdbserver:

$ ./gdbserver/gdbserver --once --multi :1234

And start gdb like this:

$ ./gdb -nx -q --data-directory=data-directory -ex "tar ext :1234" -ex "set
remote exec-file /bin/ls" -ex r
Remote debugging using :1234
Starting program:  
Reading /bin/ls from remote target...
warning: File transfers from remote targets can be slow. Use "set sysroot" to
access files locally instead.
Reading /bin/ls from remote target...
Reading symbols from target:/bin/ls...Reading
/bin/bc0fb9b3f60f72bbad3c5a1d24c9e2a1fde775.debug from remote target...
Reading /bin/.debug/bc0fb9b3f60f72bbad3c5a1d24c9e2a1fde775.debug from remote
target...
(no debugging symbols found)...done.
/home/emaisin/src/binutils-gdb/gdb/thread.c:1609: internal-error:
scoped_restore_current_thread::scoped_restore_current_thread(): Assertion `tp
!= NULL' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n)

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