From: Matthew Fortune <Matthew.Fortune@imgtec.com>
To: Fredrik Hederstierna <fredrik.hederstierna@verisure.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: RE: Core file support for ARM none (again)
Date: Mon, 01 Sep 2014 12:53:00 -0000 [thread overview]
Message-ID: <6D39441BF12EF246A7ABCE6654B0235320EFE07D@LEMAIL01.le.imgtec.org> (raw)
In-Reply-To: <OF771C01C5.15C9D4D4-ON00257D46.0041A543-00257D46.0041A548@notes.na.collabserv.com>
Fredrik Hederstierna <fredrik.hederstierna@verisure.com> writes:
> I just post these lines again, since its slightly frustrating to not get
> any response nor feedback at all.
> Is it just me thinking that having core file support also for non-Linux
> ARM EABI targets would be great?
> Any feedback is most welcome, good or bad!
While I don't have any particular need to work with bare metal ARM systems
the general concept seems relatively useful for RTOS or no-OS developers.
There is the question of how helpful this is in the general case as the
proposal requires custom client side support. I.e. A user would have to
deal with at least these three problems for the GDB support to be useful.
* The scenarios where the target has failed in some way but is still
capable of executing code.
* Implementations of the target side stub in something like freertos or
semi-hosting style code.
* Where to store the core file
Perhaps what I'm suggesting is that the idea may need an example target
side implementation in some free software to gain interest.
(I have no say in what is and is not suitable for GDB, these are just
some thoughts)
Regards,
Matthew
next prev parent reply other threads:[~2014-09-01 12:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-01 11:57 Fredrik Hederstierna
2014-09-01 12:53 ` Matthew Fortune [this message]
2014-09-01 14:05 ` Fredrik Hederstierna
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=6D39441BF12EF246A7ABCE6654B0235320EFE07D@LEMAIL01.le.imgtec.org \
--to=matthew.fortune@imgtec.com \
--cc=fredrik.hederstierna@verisure.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