From: Juha <turboruuvi@hotmail.com>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Bare metal gdb stub/server implementation
Date: Fri, 25 Sep 2015 23:52:00 -0000 [thread overview]
Message-ID: <DUB122-W182AB837303153326D4C06DC420@phx.gbl> (raw)
In-Reply-To: <DUB122-W730C2001FD91F22F856C4DC420@phx.gbl>
I have tried to find the answer by googling, in manuals and tried asking in
freenode chat (#gdb) but haven't come up with an answer...
Where could I find the "right" way to handle things like process IDs and
thread IDs in a bare metal case, where there really are no processes or threads?
I'm trying to put together a standalone gdb stub/server for Raspberry Pi B2.
(I'm not sure what to call it: it has stub functionality, but is standalone
and as such works like a server.)
I have started with a single core, and maybe one day I'll expand to all 4 cores.
Should I fake the gdb client that there are processes or threads? If,
then which way would be better: single process with 4 threads (= cores) or
4 processes without multithreading support? Maybe there is still a better option?
Also, now, when my 'stub' starts and gdb client asks for reason for halt ('?'),
I respond that a program has finished (W 00). Is that a good choise?
-Juha Aaltonen
next parent reply other threads:[~2015-09-25 23:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DUB122-W730C2001FD91F22F856C4DC420@phx.gbl>
2015-09-25 23:52 ` Juha [this message]
2015-09-26 1:48 ` Duane Ellis
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=DUB122-W182AB837303153326D4C06DC420@phx.gbl \
--to=turboruuvi@hotmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).