public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "fredrik.hederstierna@securitas-direct.com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug corefiles/14383] New: Corefile support for arm-elf-none targets
Date: Sun, 22 Jul 2012 06:32:00 -0000 [thread overview]
Message-ID: <bug-14383-4717@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=14383
Bug #: 14383
Summary: Corefile support for arm-elf-none targets
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: corefiles
AssignedTo: unassigned@sourceware.org
ReportedBy: fredrik.hederstierna@securitas-direct.com
Classification: Unclassified
Today corefiles are only supported by Linux targets for ARM.
It would be great to have the possibility to have basic corefiles also for
non-Linux ARM targets.
The ideal would be to be able to eg. run remote serial GDB to target dev-board
and eg. put breakpoints in exception handler, then run 'generate-core-file' to
be able to debug it later off-line using core-files from disk.
Possibly the existing code for corefiles in in 'arm-linux-tdep.c'.
Could this be moved to the more generic 'arm-tdep.c' to enable a
default-corefile support that could be overridden when calling osabi_init() ?
I submit a patch that seems to work, but more as an example how it could be
done perhaps, any other suggestions for solutions are ofcourse welcome.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2012-07-22 6:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-22 6:32 fredrik.hederstierna@securitas-direct.com [this message]
2012-07-22 7:02 ` [Bug corefiles/14383] " fredrik.hederstierna@securitas-direct.com
2012-11-05 9:55 ` fredrik.hederstierna@securitas-direct.com
2012-11-05 9:56 ` fredrik.hederstierna@securitas-direct.com
2012-11-05 9:57 ` fredrik.hederstierna@securitas-direct.com
2012-11-05 10:03 ` fredrik.hederstierna@securitas-direct.com
2013-10-29 22:49 ` will.newton at gmail dot com
2014-11-10 12:27 ` Mail at Robitzki dot com
2014-11-10 12:31 ` Mail at Robitzki dot com
2020-10-16 23:38 ` fredrik.hederstierna@securitas-direct.com
2020-10-16 23:40 ` fredrik.hederstierna@securitas-direct.com
2020-10-20 11:31 ` fredrik.hederstierna@securitas-direct.com
2021-06-01 8:58 ` cvs-commit at gcc dot gnu.org
2021-11-06 8:46 ` fredrik.hederstierna@securitas-direct.com
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=bug-14383-4717@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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).