From: Daniel Jacobowitz <drow@false.org>
To: Robert Norton <rnorton@broadcom.com>
Cc: gdb@sourceware.org
Subject: Re: Loading a Core File
Date: Fri, 06 Jul 2007 12:03:00 -0000 [thread overview]
Message-ID: <20070706120347.GC10648@caradoc.them.org> (raw)
In-Reply-To: <B0D822BFECD50F4991F2516EA50F273C01E4DFEA@NT-IRVA-0752.brcm.ad.broadcom.com>
On Fri, Jul 06, 2007 at 04:26:19AM -0700, Robert Norton wrote:
> But it's not a complete solution. What is the 'proper' way of doing core
> files in gdb? What is involved in getting it to work via 'target core'?
Take a look at any cross debugging target which supports core files.
Use corelow.o in TDEPFILES, then implement regset_from_core_section.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-07-06 12:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-06 11:26 Robert Norton
2007-07-06 12:03 ` Daniel Jacobowitz [this message]
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=20070706120347.GC10648@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=rnorton@broadcom.com \
/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