From: Daniel Jacobowitz <drow@false.org>
To: Jon Ringle <jon.ringle@comdial.com>
Cc: gdb@sources.redhat.com
Subject: Re: arm core analysis on x86 host
Date: Tue, 29 Mar 2005 04:57:00 -0000 [thread overview]
Message-ID: <20050329045853.GA11420@nevyn.them.org> (raw)
In-Reply-To: <200503282317.15105.jon.ringle@comdial.com>
On Mon, Mar 28, 2005 at 11:17:14PM -0500, Jon Ringle wrote:
> I am now using as an example ppc-linux-tdep.c, however it still seems that a
> call to deprecated_add_core_fns() is needed. When I use a 'target
> core /path/to/core' command, core_open() gets called which calls
> sniff_core_bfd(). sniff_core_bfd() has a loop to iterate over core_file_fns,
> which as far as I can tell gets populated via deprecated_add_core_fns(). I
> don't see how else core_file_fns gets populated. Am I misunderstanding the
> use of 'deprecated' here? My understanding of the word is that use is no
> longer desired in favor of a (hopefully) better solution or archetecture.
Look harder :-) sniff_core_bfd is disabled if you provide the new
mechanism. It should be all you need.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-03-29 4:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-28 23:29 Jon Ringle
2005-03-28 23:56 ` Daniel Jacobowitz
2005-03-29 0:48 ` Jon Ringle
2005-03-29 1:31 ` Daniel Jacobowitz
2005-03-29 4:17 ` Jon Ringle
2005-03-29 4:57 ` Daniel Jacobowitz [this message]
2005-03-29 16:19 ` Jon Ringle
2005-03-29 16:33 ` Daniel Jacobowitz
2005-03-29 16:39 ` Jon Ringle
2005-03-29 16:52 ` Daniel Jacobowitz
2005-03-29 17:18 ` Jon Ringle
2005-03-29 19:35 ` Jon Ringle
2005-03-30 2:07 ` Jon Ringle
2005-03-30 4:51 ` Daniel Jacobowitz
2005-03-30 14:42 ` Jon Ringle
2005-03-30 15:15 ` M.M. Kettenis
2005-03-30 15:25 ` Daniel Jacobowitz
2005-03-30 18:02 ` Mark Kettenis
2005-03-30 18:18 ` Daniel Jacobowitz
2005-03-31 14:08 ` Jon Ringle
2005-03-31 14:28 ` Daniel Jacobowitz
2005-03-31 14:35 ` Jon Ringle
2005-04-06 22:16 ` Jon Ringle
2005-04-06 22:27 ` Daniel Jacobowitz
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=20050329045853.GA11420@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=jon.ringle@comdial.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).