New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 841362 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug
Build-Toolchain



Sign in to add a comment

gdb: internal-error when using gdbserver --multi

Project Member Reported by rrangel@chromium.org, May 9 2018

Issue description

DEBUG: Running: ['x86_64-cros-linux-gnu-gdb', '--quiet', '--eval-command=set sysroot /build/grunt', '--eval-command=set solib-absolute-prefix /build/grunt', '--eval-command=set solib-search-path /build/grunt', '--eval-command=set debug-file-directory /build/grunt/usr/lib/debug', '--eval-command=set prompt (grunt-gdb) ', '--eval-command=target extended-remote | ssh -p 22 -oBatchMode=yes -oProtocol=2 -oConnectTimeout=30 -oLogLevel=QUIET -oServerAliveCountMax=3 -oServerAliveInterval=10 -oConnectionAttempts=4 -oCheckHostIP=no -oUserKnownHostsFile=/dev/null -oStrictHostKeyChecking=no -oNumberOfPasswordPrompts=0 -oIdentitiesOnly=yes -i /tmp/ssh-tmpEM_x3l/testing_rsa root@100.107.108.187 -- gdbserver --multi stdio']
GNU gdb (Chromium OS 8.0.1.20180501 vanilla) 8.0.1
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "--host=x86_64-pc-linux-gnu --target=x86_64-cros-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://crbug.com/new>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
Remote debugging using | ssh -p 22 -oBatchMode=yes -oProtocol=2 -oConnectTimeout=30 -oLogLevel=QUIET -oServerAliveCountMax=3 -oServerAliveInterval=10 -oConnectionAttempts=4 -oCheckHostIP=no -oUserKnownHostsFile=/dev/null -oStrictHostKeyChecking=no -oNumberOfPasswordPrompts=0 -oIdentitiesOnly=yes -i /tmp/ssh-tmpEM_x3l/testing_rsa root@100.107.108.187 -- gdbserver --multi stdio
Remote debugging using stdio
(grunt-gdb) set remote exec-file /bin/bash
(grunt-gdb) run
Starting program:  
Process /bin/bash created; pid = 14564
stdin/stdout redirected
Reading symbols from /build/grunt/bin/bash...(no debugging symbols found)...done.
thread.c:1005: internal-error: int is_thread_state(ptid_t, enum thread_state): Assertion `tp' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) y

This is a bug, please report it.  For instructions, see:
<http://crbug.com/new>.

thread.c:1005: internal-error: int is_thread_state(ptid_t, enum thread_state): Assertion `tp' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) y
Aborted



Not actually sure if this is a cros issue, but it told me to file a bug :)
 
Cc: cmt...@chromium.org yunlian@chromium.org
Caroline, Yunlian, can you take a look.

Owner: ----
rrangel@, thanks for filing.

can you clarify what the impact for you is? is P3 the right priority?
I think P3 is fine, I just noticed it when testing.
Owner: cmt...@chromium.org
Status: Assigned (was: Unconfirmed)

Comment 5 by cmt...@chromium.org, May 10 2018

To reproduce/debug this issue it would be very helpful if you gave me the complete set of commands you gave that got you to this point.
It's in the first line. You will need to change the ip address and change grunt with what ever board you have available.

    'x86_64-cros-linux-gnu-gdb' '--quiet' '--eval-command=set sysroot /build/grunt' '--eval-command=set solib-absolute-prefix /build/grunt' '--eval-command=set solib-search-path /build/grunt' '--eval-command=set debug-file-directory /build/grunt/usr/lib/debug' '--eval-command=set prompt (grunt-gdb) ' '--eval-command=target extended-remote | ssh -p 22 -oBatchMode=yes -oProtocol=2 -oConnectTimeout=30 -oLogLevel=QUIET -oServerAliveCountMax=3 -oServerAliveInterval=10 -oConnectionAttempts=4 -oCheckHostIP=no -oUserKnownHostsFile=/dev/null -oStrictHostKeyChecking=no -oNumberOfPasswordPrompts=0 -oIdentitiesOnly=yes -i /tmp/ssh-tmpEM_x3l/testing_rsa root@100.107.108.187 -- gdbserver --multi stdio'

(grunt-gdb) set remote exec-file /bin/bash
(grunt-gdb) run

Sign in to add a comment