This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: gdb + remote qemu, Ctrl-C does not work

From: "dpc at ucore dot info" <dpc at ucore dot info>
To: Tristan Gingold <gingold at adacore dot com>
Cc: Pedro Alves <pedro at codesourcery dot com>, gdb at sourceware dot org, Mike Frysinger <vapier at gentoo dot org>
Date: Wed, 2 Mar 2011 15:25:57 +0100
Subject: Re: gdb + remote qemu, Ctrl-C does not work
References: <AANLkTimvhnQs_4gTkaU_xfgjnm0G=Qkm-ZdzVYJ9nmfK@mail.gmail.com> <201103020945.11471.pedro@codesourcery.com> <AANLkTi=1y6RLZakkA3A=xTnqWNKhCg2s7Ka9nzLsjQE-@mail.gmail.com> <201103021249.34558.pedro@codesourcery.com> <0EA5A1E3-9098-457F-9334-74476345C908@adacore.com>

On Wed, Mar 2, 2011 at 2:07 PM, Tristan Gingold <gingold@adacore.com> wrote:
>> Your ctrl-c is reaching qemu as well, which is making it
>> commit suicide.
>
> Usually background processes don't get C-c.

I am not sure, but I'd guess so. But what Pedro Alves says would
explained everything perfectly.

I'm planing to use internal bash "trap" command to handle ctrl-c myself.

But I'll try the trick with a pipe too.
-- 
http://dpc.ucore.info

Follow-Ups:
- Re: gdb + remote qemu, Ctrl-C does not work
  - From: Joel Brobecker

References:
- Re: gdb + remote qemu, Ctrl-C does not work
  - From: Pedro Alves
- Re: gdb + remote qemu, Ctrl-C does not work
  - From: dpc at ucore dot info
- Re: gdb + remote qemu, Ctrl-C does not work
  - From: Pedro Alves
- Re: gdb + remote qemu, Ctrl-C does not work
  - From: Tristan Gingold

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]