From: Pedro Alves <pedro_alves@portugalmail.pt>
To: gdb@sourceware.org
Subject: gdb on arm-wince-pe
Date: Tue, 21 Feb 2006 21:42:00 -0000 [thread overview]
Message-ID: <43FB7B0C.2010703@portugalmail.pt> (raw)
Hi all!
I have gdb built for target arm-wince-pe on a cygwin host.
This if for I new project I am developing to bring gnu tools for
arm-wince-pe up to speed.
Check out cegcc if you're interested.
(http://developer.berlios.de/projects/cegcc/)
I am now looking into gdb to implement a few missing things and trying
to remove a few quirks here and there.
I have been looking through the code for a few hours to get a grasp on
gdb internals.
With some patches the gdb/wince-stub.c is now working ok. Not perfect
yet, but working.
I now want to implement CTRL_c breaking into the remote app.
It currently does nothing when the target program is being debugged, and
prints "Quit" when there is no program being debugged.
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?
Cheers,
Pedro Alves
P.S. Please add me to the cc list, as I am not (yet) on this mailing list.
next reply other threads:[~2006-02-21 20:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-21 21:42 Pedro Alves [this message]
2006-02-22 6:23 ` Daniel Jacobowitz
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=43FB7B0C.2010703@portugalmail.pt \
--to=pedro_alves@portugalmail.pt \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).