This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
RE: Core file support for ARM none (again)
- From: Matthew Fortune <Matthew dot Fortune at imgtec dot com>
- To: Fredrik Hederstierna <fredrik dot hederstierna at verisure dot com>, "gdb at sourceware dot org" <gdb at sourceware dot org>
- Date: Mon, 1 Sep 2014 12:53:21 +0000
- Subject: RE: Core file support for ARM none (again)
- Authentication-results: sourceware.org; auth=none
- References: <OF771C01C5 dot 15C9D4D4-ON00257D46 dot 0041A543-00257D46 dot 0041A548 at notes dot na dot collabserv dot 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