public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "dominik.b.czarnota+bugzilla at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug remote/18772] gdb does not respond to CTRL-C
Date: Sun, 14 Aug 2022 21:25:58 +0000 [thread overview]
Message-ID: <bug-18772-4717-ejm7olgVMm@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18772-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=18772
Disconnect3d <dominik.b.czarnota+bugzilla at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dominik.b.czarnota+bugzilla
| |@gmail.com
--- Comment #14 from Disconnect3d <dominik.b.czarnota+bugzilla at gmail dot com> ---
(In reply to Pedro Alves from comment #13)
> Once I'm done with my current priorities, my next project will be going back
> to this:
>
> [PATCH v2 00/16] Interrupting programs that block/ignore SIGINT
> https://pi.simark.ca/gdb-patches/20210614212410.1612666-1-pedro@palves.net/
>
> That redesigns how SIGINT is handled when native debugging, such that GDB
> _always_ gets the SIGINT first instead of relying on the inferior getting
> it, so I suspect it will fix Andrew's testcase when native debugging (though
> I haven't tried it). As for remote debugging with gdbserver, I will take a
> look at it too, once I resume work on that series.
Hey,
Any progress on it?
I just stumbled on it when debugging an AARCH64 target [0] run via QEMU user
emulation [1]. I wonder if that it is a bug in the QEMU user emulation layer
here or if comes from GDB?
[0]
https://github.com/perfectblue/ctf-writeups/tree/master/2019/insomnihack-teaser-2019/nyanc/challenge
[1] Via command `qemu-aarch64 -g 1234 ./nyanc`, but I first used patchelf to
set interpreter and libc:
```
patchelf --set-interpreter ./ld-linux-aarch64.so.1 ./nyanc
patchelf --replace-needed libc.so.6 ./libc.so.6 ./nyanc
```
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-08-14 21:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 11:32 [Bug remote/18772] New: " moorel at ntlworld dot com
2020-04-20 8:55 ` [Bug remote/18772] " massimo.b at gmx dot net
2020-08-18 2:45 ` paul at sourceware dot m.darkrain42.org
2020-10-10 15:49 ` rarul at rarul dot com
2020-10-12 6:15 ` matic.kres at isystem dot si
2022-04-16 14:02 ` aburgess at redhat dot com
2022-04-19 10:26 ` moorel at ntlworld dot com
2022-04-24 22:08 ` richsurgenor at gmail dot com
2022-04-24 22:27 ` richsurgenor at gmail dot com
2022-04-25 13:22 ` aburgess at redhat dot com
2022-04-26 14:59 ` aburgess at redhat dot com
2022-06-22 10:52 ` ghjghj530-bubu at yahoo dot de
2022-06-22 16:42 ` pedro at palves dot net
2022-08-14 21:25 ` dominik.b.czarnota+bugzilla at gmail dot com [this message]
2022-08-30 8:40 ` filip.bascarevic at siemens dot com
2022-11-27 9:31 ` cvs-commit at gcc dot gnu.org
2023-03-20 15:53 ` eldar.abusalimov at jetbrains dot com
2023-03-21 14:58 ` tromey at sourceware dot org
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-18772-4717-ejm7olgVMm@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).