From: 刘康 <lkang0305@163.com>
To: gdb@sourceware.org
Subject: gdbserver for arm does not support multi-process debugging
Date: Thu, 17 Oct 2019 06:19:00 -0000 [thread overview]
Message-ID: <6fea79cd.5d47.16dd85f053a.Coremail.lkang0305@163.com> (raw)
Dear gdb@sourceware.org
I am researching the gdbserver's source code for ARM, what confused me is that it does not support multi-process to debug the target's child process, cause it dose not interesting in PTRACE_EVENT_FORK, I don't know whether it's a bug or it's just a feature by design.
Appreciate very much for any reply and thank you so much!
next reply other threads:[~2019-10-17 6:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 6:19 刘康 [this message]
2019-10-18 12:27 ` Luis Machado
[not found] ` <3cb2ee7c.59f4.16dfc404ae2.Coremail.lkang0305@163.com>
2019-10-24 10:38 ` Luis Machado
2019-10-28 11:13 ` 刘康
[not found] ` <1eb012d5-2fad-bd49-e5c9-6160bbfc1c0d@linaro.org>
[not found] ` <57533fd3.e9a7.16e171c601e.Coremail.lkang0305@163.com>
[not found] ` <d0d526d6-159f-5e42-8ff8-efbac3649631@linaro.org>
[not found] ` <76c18800.41ee.16e1a553723.Coremail.lkang0305@163.com>
2019-10-30 1:46 ` Luis Machado
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=6fea79cd.5d47.16dd85f053a.Coremail.lkang0305@163.com \
--to=lkang0305@163.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