This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/18945] gdbserver cannot be interrupted on linux when pgid doesn't match pid
- From: "prosup at 163 dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Tue, 11 Sep 2018 06:18:49 +0000
- Subject: [Bug gdb/18945] gdbserver cannot be interrupted on linux when pgid doesn't match pid
- Auto-submitted: auto-generated
- References: <bug-18945-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=18945
--- Comment #10 from prosup <prosup at 163 dot com> ---
Created a bug before I found out this one.
If we use gdb locally,it will stop the process normally,because ctrl+c
triggered sending sigint to the program directly(?).
While using gdbserver ,it has to "translate messages" from host gdb to sigint.
I'v tried gdb gdbserver,and call kill(pid,2) directly,it worked.
I tried inspect the signal send to the attached program,call kill(pid,2) or
kill 2 pid in bash,will send sigint(2) to the "attached" pid,send sigstop(19)
to child process.
prove patch provided by Josh is the right approach.
--
You are receiving this mail because:
You are on the CC list for the bug.