Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "dpc@ucore.info" <dpc@ucore.info>
To: gdb@sourceware.org
Subject: gdb + remote qemu, Ctrl-C does not work
Date: Tue, 01 Mar 2011 14:48:00 -0000	[thread overview]
Message-ID: <AANLkTinOhM8KvC7jOwXauvgzkPOmqPRHjfBghMG1-yrd@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimvhnQs_4gTkaU_xfgjnm0G=Qkm-ZdzVYJ9nmfK@mail.gmail.com>

Hi,

I have a little problem with arm-none-eabi-gdb that I'm debugging
remote qemu-system-arm targets.

The problem is: Ctrl-C does not break qemu target, but disconnects
qemu completely.

(gdb) c
Continuing.
^CRemote communication error.  Target disconnected.: Connection reset by peer.


GDB is not offering me the Ctrl-C sequence to break execution (like my
native gdb does) so I guess I should use some different options
because what I know is (I've tried), that sending SIGINT to
arm-none-eabi-gdb process does break the execution. I see no reason
Ctrl-C could not work if sending SIGINT does.

I'm using default options and here are some relevant version strings:

$ arm-none-eabi-gdb --version
GNU gdb (Sourcery G++ Lite 2010.09-51) 7.2.50.20100908-cvs
$ uname -a
Linux mutex 2.6.35-27-generic #48-Ubuntu SMP Tue Feb 22 20:25:46 UTC
2011 x86_64 GNU/Linux

Much appreciated.

Regards,
Dawid

--
http://dpc.ucore.info


       reply	other threads:[~2011-03-01 14:48 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 [this message]
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
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=AANLkTinOhM8KvC7jOwXauvgzkPOmqPRHjfBghMG1-yrd@mail.gmail.com \
    --to=dpc@ucore.info \
    --cc=gdb@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