[Bug server/31731] New: gdbserver fails to start and seems to freeze

[Bug server/31731] New: gdbserver fails to start and seems to freeze

[beatussum at protonmail dot com]

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

            Bug ID: 31731
           Summary: gdbserver fails to start and seems to freeze
           Product: gdb
           Version: 14.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: server
          Assignee: unassigned at sourceware dot org
          Reporter: beatussum at protonmail dot com
  Target Milestone: ---

Created attachment 15517
  --> https://sourceware.org/bugzilla/attachment.cgi?id=15517&action=edit
Output of `gdbserver --debug :1234 ls`

After calling `gdbserver`, the program seems to freeze and does not output
anything except with `--debug`.

I attach the following informations if it helps:

`gdb` version: 14.2 (it is not in the list)
OS: GNU/Linux (Gentoo)
Kernel version: 6.6.30

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

[Bug server/31731] gdbserver fails to start and seems to freeze

[ssbssa at sourceware dot org]

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

Hannes Domani <ssbssa at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ssbssa at sourceware dot org

--- Comment #1 from Hannes Domani <ssbssa at sourceware dot org> ---
Please also show how you connected from gdb, and what else you tried on gdb
side.

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

[Bug server/31731] gdbserver fails to start and seems to freeze

[tromey at sourceware dot org]

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

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at sourceware dot org
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |WAITING
   Last reconfirmed|                            |2024-05-13

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

[Bug server/31731] gdbserver fails to start and seems to freeze

[beatussum at protonmail dot com]

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

--- Comment #2 from Mattéo Rossillol‑‑Laruelle <beatussum at protonmail dot com> ---
(In reply to Hannes Domani from comment #1)
> Please also show how you connected from gdb, and what else you tried on gdb
> side.

After starting gdbserver, I just run gdb and type `target remote localhost
1234`, then gdb prints "localhost:1234: Connection timed out.".

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

[Bug server/31731] gdbserver fails to start and seems to freeze

[tromey at sourceware dot org]

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

--- Comment #3 from Tom Tromey <tromey at sourceware dot org> ---
Could you cut and paste the actual commands you use?
Like, the gdb session?  What you typed isn't really the
command you used -- that syntax is wrong.

Also can you try "target remote :1234" -- i.e., omit the
"localhost"?  I feel like this has been the cause of
issues before.

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

[Bug server/31731] gdbserver fails to start and seems to freeze

[beatussum at protonmail dot com]

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

--- Comment #4 from Mattéo Rossillol‑‑Laruelle <beatussum at protonmail dot com> ---
(In reply to Tom Tromey from comment #3)
> Could you cut and paste the actual commands you use?
> Like, the gdb session?  What you typed isn't really the
> command you used -- that syntax is wrong.
> 
> Also can you try "target remote :1234" -- i.e., omit the
> "localhost"?  I feel like this has been the cause of
> issues before.

Sorry, I forgot the colon in `target remote localhost:1234` in my previous
answer. 

With `target remote :1234`, I get:

Remote debugging using :1234
Ignoring packet error, continuing...
warning: unrecognized item "timeout" in "qSupported" response
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Remote replied unexpectedly to 'vMustReplyEmpty': timeout

On server side, I run `gdbserver --debug :1234 /usr/bin/ls`.

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

[Bug server/31731] gdbserver fails to start and seems to freeze

[tromey at sourceware dot org]

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

--- Comment #5 from Tom Tromey <tromey at sourceware dot org> ---
Ok, please try this.

In one terminal, "gdbserver :1234 /bin/ls"
Don't use --debug

In another terminal, start "gdb -nx /bin/ls".
Then "set remotelogfile /tmp/log".
Then "target remote :1234"

After it fails, attach the log file to this bug.
Maybe that will tell us something, not sure.

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

[Bug server/31731] gdbserver fails to start and seems to freeze

[beatussum at protonmail dot com]

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

--- Comment #6 from Mattéo Rossillol‑‑Laruelle <beatussum at protonmail dot com> ---
Created attachment 15522
  --> https://sourceware.org/bugzilla/attachment.cgi?id=15522&action=edit
Log file

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

[Bug server/31731] gdbserver fails to start and seems to freeze

[beatussum at protonmail dot com]

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

--- Comment #7 from Mattéo Rossillol‑‑Laruelle <beatussum at protonmail dot com> ---
(In reply to Tom Tromey from comment #5)
> Ok, please try this.
> 
> In one terminal, "gdbserver :1234 /bin/ls"
> Don't use --debug
> 
> In another terminal, start "gdb -nx /bin/ls".
> Then "set remotelogfile /tmp/log".
> Then "target remote :1234"
> 
> After it fails, attach the log file to this bug.
> Maybe that will tell us something, not sure.

Normally, I've just attached the log file.

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