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: Mike Frysinger <vapier at gentoo dot org>
Cc: gdb at sourceware dot org
Date: Wed, 2 Mar 2011 08:29:38 +0100
Subject: Re: gdb + remote qemu, Ctrl-C does not work
References: <AANLkTimvhnQs_4gTkaU_xfgjnm0G=Qkm-ZdzVYJ9nmfK@mail.gmail.com> <201103011335.06278.vapier@gentoo.org> <AANLkTikHLAX4GDw37GV3hpMQxf-i3s-KUBGYbt0rckp4@mail.gmail.com> <201103011850.29526.vapier@gentoo.org>

On Wed, Mar 2, 2011 at 12:50 AM, Mike Frysinger <vapier@gentoo.org> wrote:
>> Clearly the gdb has some way to break gdb if sending SIGINT to gdb
>> works.
>
> if the remote stub does things wrong, there's nothing the gdb client should be
> doing to work around it. Âfix the remote stub.

That's the possibility as well. Someone / I could try fix qemu sources.

However I don't understand why gdb is doing something different on
SIGINT and something different on Ctrl-C.

-- 
http://dpc.ucore.info

Follow-Ups:
- Re: gdb + remote qemu, Ctrl-C does not work
  - From: Pedro Alves
- Re: gdb + remote qemu, Ctrl-C does not work
  - From: Andreas Schwab

References:
- Re: gdb + remote qemu, Ctrl-C does not work
  - From: Mike Frysinger
- 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: Mike Frysinger

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