[Bug gdb/34566] New: GDB cannot interrupt debuginofd until server responds, stuck waiting 1.5 min for ubuntu
k4lizen at proton dot me via Gdb-prs <[email protected]>
| Newsgroups | gmane.comp.gdb.bugs.discuss |
|---|---|
| Message-ID | <[email protected]/bugzilla/> |
https://sourceware.org/bugzilla/show_bug.cgi?id=34566
Bug ID: 34566
Summary: GDB cannot interrupt debuginofd until server responds,
stuck waiting 1.5 min for ubuntu
Product: gdb
Version: HEAD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: k4lizen at proton dot me
Target Milestone: ---
GDB: GNU gdb (GDB) 18.0.50.20260329-git
OS : Arch linux
If GDB tries to fetch debug info, and the debuginfod server simply does not
respond,
you are not able to cancel the request with Ctrl-C. You will need to wait
DEBUGINFOD_TIMEOUT (90 seconds by default) for it to finish or force-kill GDB.
Currently the https://debuginfod.ubuntu.com/ server is down, so if you're on
ubuntu,
you're not having a fun time debugging with GDB.
https://bugs.launchpad.net/ubuntu-debuginfod/+bug/2163016
LLDB also has the same bug, which is kinda of a wild coincidence:
https://github.com/llvm/llvm-project/issues/216629
More details / upstream: https://github.com/pwndbg/pwndbg/pull/4079
You can reproduce with:
```bash
DEBUGINFOD_CACHE_PATH=$(mktemp -d /tmp/lldb-debuginfod-test.XXXXXX)
DEBUGINFOD_URLS=https://debuginfod.ubuntu.com gdb --nx /bin/sh
```
(answer yes to debuginfo)
If ubuntu fixes their server, you'll be able to repro with:
In one terminal:
```bash
socat TCP-LISTEN:45678,bind=127.0.0.1,reuseaddr,fork EXEC:'sleep 120'
```
In a second terminal:
```bash
DEBUGINFOD_CACHE_PATH=$(mktemp -d /tmp/lldb-debuginfod-test.XXXXXX)
DEBUGINFOD_URLS=https://debuginfod.ubuntu.com gdb --nx /bin/sh
```
.
--
You are receiving this mail because:
You are on the CC list for the bug.