Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "dpc@ucore.info" <dpc@ucore.info>
To: Tristan Gingold <gingold@adacore.com>
Cc: Pedro Alves <pedro@codesourcery.com>,
	gdb@sourceware.org, 	Mike Frysinger <vapier@gentoo.org>
Subject: Re: gdb + remote qemu, Ctrl-C does not work
Date: Wed, 02 Mar 2011 14:26:00 -0000	[thread overview]
Message-ID: <AANLkTimJFgP3_bjSQ78=sziy1q1t1e1VKUTS=fLfnNiK@mail.gmail.com> (raw)
In-Reply-To: <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


  parent reply	other threads:[~2011-03-02 14:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTimvhnQs_4gTkaU_xfgjnm0G=Qkm-ZdzVYJ9nmfK@mail.gmail.com>
2011-03-01 14:48 ` dpc
2011-03-01 18:35   ` Mike Frysinger
2011-03-01 22:52     ` dpc
2011-03-01 23:50       ` Mike Frysinger
2011-03-02  7:29         ` dpc
2011-03-02  9:45           ` Pedro Alves
2011-03-02 12:29             ` dpc
2011-03-02 12:49               ` Pedro Alves
2011-03-02 13:07                 ` Tristan Gingold
2011-03-02 14:17                   ` Pedro Alves
2011-03-02 14:24                     ` Tristan Gingold
2011-03-02 14:26                   ` dpc [this message]
2011-03-02 15:04                     ` Joel Brobecker
2011-03-02 16:12                       ` Andreas Schwab
2011-03-02 10:12           ` Andreas Schwab

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='AANLkTimJFgP3_bjSQ78=sziy1q1t1e1VKUTS=fLfnNiK@mail.gmail.com' \
    --to=dpc@ucore.info \
    --cc=gdb@sourceware.org \
    --cc=gingold@adacore.com \
    --cc=pedro@codesourcery.com \
    --cc=vapier@gentoo.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