From: Daniel Jacobowitz <drow@false.org>
To: Pedro Alves <pedro_alves@portugalmail.pt>
Cc: gdb@sourceware.org
Subject: Re: gdb on arm-wince-pe
Date: Wed, 22 Feb 2006 06:23:00 -0000 [thread overview]
Message-ID: <20060222044009.GB10442@nevyn.them.org> (raw)
In-Reply-To: <43FB7B0C.2010703@portugalmail.pt>
On Tue, Feb 21, 2006 at 08:41:48PM +0000, Pedro Alves wrote:
> Where should I start looking for/what is needed to implement it (ctrl_c
> breaking)?
> I tried debugging arm-wince-pe-gdb on gdb itself, putting some
> breakpoints in the signal handling,
> and issuing kill -INT signals to see what happens there, and I see that
> ultimatly, quit (void) is called.
> Is there some target_op that I should implement, or should I provide my
> own signal handling?
Take a look at remote.c, which installs its own signal handler. You'll
want to do something similar.
Really, if possible, I would recommend using remote.c to talk to your
target over the standard GDB remote protocol instead of the
WinCE-specific protocol that wince-stub.c implements. That's much
better supported.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-02-22 4:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-21 21:42 Pedro Alves
2006-02-22 6:23 ` Daniel Jacobowitz [this message]
2006-02-22 14:29 ` Christopher Faylor
2006-02-23 4:29 ` Pedro Alves
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=20060222044009.GB10442@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=pedro_alves@portugalmail.pt \
/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