From: Kaushik Phatak <Kaushik.Phatak@kpitcummins.com>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: RE: GDB and gdbserver for CR16 target
Date: Fri, 27 Jan 2012 03:17:00 -0000 [thread overview]
Message-ID: <C6CA53A2A46BA7469348BDBD663AB658272E5568@KCHJEXMB01.kpit.com> (raw)
Hi,
Making further progress with the gdbserver for CR16 target, it seems that the
PTRACE_CONT is killing the debugee with SIGKILL,
"Child terminated with signal = 9"
The ATTACH and other ptrace calls seem to work OK. Our Kernel is 2.6.19 (uClinux)
I did read in some discussions lists, issues related to PTRACE_CONT, however
could not conclude much from it.
The PTRACE_CONT implementation in the kernel is very similar to other targets like SH.
Any inputs in this regard would be highly appreciated.
Thanks,
Kaushik
next reply other threads:[~2012-01-27 3:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 3:17 Kaushik Phatak [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-01-30 4:33 Kaushik Phatak
2011-12-22 13:07 Kaushik Phatak
2011-12-19 11:56 Kaushik Phatak
2011-12-13 12:56 Kaushik Phatak
2011-12-13 13:17 ` Yao Qi
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=C6CA53A2A46BA7469348BDBD663AB658272E5568@KCHJEXMB01.kpit.com \
--to=kaushik.phatak@kpitcummins.com \
--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