public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "mliska at suse dot cz" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug cli/29582] New: Usability improvement: CTRL+C when debugindod client is downloading a file
Date: Sun, 18 Sep 2022 08:20:39 +0000 [thread overview]
Message-ID: <bug-29582-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29582
Bug ID: 29582
Summary: Usability improvement: CTRL+C when debugindod client
is downloading a file
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: cli
Assignee: unassigned at sourceware dot org
Reporter: mliska at suse dot cz
CC: fchen0000 at gmail dot com, vries at gcc dot gnu.org
Target Milestone: ---
Let's imagine you're debugging a binary with many shared libs and you're in the
middle of downloading debuginfo of the shared libs, you press CTRL+C.
At that point, the running downloading is terminated and gdb continues
downloading the next debug info. I would expect to be asked if I want to
terminate all future downloading or not. Having that one can easily exit a
debugging session instead of waiting for the cancelation of all the downloading
stuff.
Example:
[
]^CCancelling download of separate debug info for
/lib64/libzypp.so.1722...
Downloading 13.35 MB separate debug info for /lib64/libstdc++.so.6
[###
]^CCancelling download of separate debug info for
/lib64/libstdc++.so.6...
Downloading 0.37 MB separate debug info for /lib64/libgcc_s.so.1
[#############################################################
]^CCancelling download of separate debug info for
/lib64/libgcc_s.so.1...
Downloading 5.93 MB separate debug info for /lib64/libc.so.6
[##
]^CCancelling download of separate debug info for
/lib64/libc.so.6...
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
^CCancelling download of separate debug info for /lib64/librpm.so.9...
^CCancelling download of separate debug info for /lib64/libz.so.1...
^CCancelling download of separate debug info for
/lib64/libboost_thread.so.1.80.0...
^C^CCancelling download of separate debug info for /lib64/libglib-2.0.so.0...
^CCancelling download of separate debug info for /lib64/libcrypto.so.1.1...
^CCancelling download of separate debug info for /lib64/libsigc-2.0.so.0...
^CCancelling download of separate debug info for /lib64/libzstd.so.1...
^CCancelling download of separate debug info for /lib64/libzck.so.1...
^CCancelling download of separate debug info for /lib64/libtinfo.so.6...
^CCancelling download of separate debug info for /lib64/libfa.so.1...
^CCancelling download of separate debug info for /lib64/liblzma.so.5...
^CCancelling download of separate debug info for /lib64/libm.so.6...
^CCancelling download of separate debug info for /lib64/librpmio.so.9...
^CCancelling download of separate debug info for /lib64/libpopt.so.0...
^CCancelling download of separate debug info for /lib64/libcap.so.2...
^CCancelling download of separate debug info for /lib64/libacl.so.1...
^CCancelling download of separate debug info for /lib64/libassuan.so.0...
^CCancelling download of separate debug info for /lib64/libgpg-error.so.0...
^CCancelling download of separate debug info for /lib64/libnghttp2.so.14...
^CCancelling download of separate debug info for /lib64/libidn2.so.0...
^CCancelling download of separate debug info for /lib64/libssh.so.4...
^CCancelling download of separate debug info for /lib64/libpsl.so.5...
^CCancelling download of separate debug info for /lib64/libssl.so.1.1...
^CCancelling download of separate debug info for /lib64/libgssapi_krb5.so.2...
^CCancelling download of separate debug info for /lib64/libldap.so.2...
^CCancelling download of separate debug info for /lib64/liblber.so.2...
^CCancelling download of separate debug info for /lib64/libbrotlidec.so.1...
^CCancelling download of separate debug info for /lib64/libpcre.so.1...
^CCancelling download of separate debug info for /lib64/libgcrypt.so.20...
^CCancelling download of separate debug info for /lib64/libbz2.so.1...
^CCancelling download of separate debug info for /lib64/liblua5.4.so.5...
^CCancelling download of separate debug info for /lib64/libunistring.so.2...
^CCancelling download of separate debug info for /lib64/libkrb5.so.3...
^CCancelling download of separate debug info for /lib64/libk5crypto.so.3...
^CCancelling download of separate debug info for /lib64/libcom_err.so.2...
^CCancelling download of separate debug info for /lib64/libkrb5support.so.0...
^CCancelling download of separate debug info for /lib64/libsasl2.so.3...
^CCancelling download of separate debug info for /lib64/libbrotlicommon.so.1...
^CCancelling download of separate debug info for /lib64/libkeyutils.so.1...
^CCancelling download of separate debug info for /lib64/libresolv.so.2...
^CCancelling download of separate debug info for /lib64/libselinux.so.1...
^CCancelling download of separate debug info for /lib64/libpcre2-8.so.0...
[New Thread 0x7ffff60c76c0 (LWP 22188)]
^C
Thread 1 "Zypp-main" received signal SIGINT, Interrupt.
0x00007ffff7307c1e in fstatat64 () from /lib64/libc.so.6
Missing separate debuginfos, use: zypper install
zypper-debuginfo-1.14.56-1.1.x86_64
(gdb) Quit(gdb) Quit
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-09-18 8:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-18 8:20 mliska at suse dot cz [this message]
2022-09-18 8:34 ` [Bug cli/29582] " vries at gcc dot gnu.org
2022-09-20 11:28 ` vries at gcc dot gnu.org
2022-09-20 13:59 ` vries at gcc dot gnu.org
2022-09-20 15:36 ` mliska at suse dot cz
2022-09-22 0:16 ` amerey at redhat dot com
2022-09-28 15:09 ` vries at gcc dot gnu.org
2022-09-28 15:09 ` vries at gcc dot gnu.org
2022-09-29 2:23 ` amerey at redhat dot com
2022-09-29 8:26 ` vries at gcc dot gnu.org
2024-01-10 17:09 ` ssbssa at sourceware dot org
2024-02-22 22:28 ` amerey at redhat dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-29582-4717@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).