Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jon Ringle <jon.ringle@comdial.com>
To: gdb@sources.redhat.com
Subject: Re: arm core analysis on x86 host
Date: Tue, 29 Mar 2005 16:39:00 -0000	[thread overview]
Message-ID: <200503291139.15566.jon.ringle@comdial.com> (raw)
In-Reply-To: <20050329163326.GA8753@nevyn.them.org>

On Tuesday 29 March 2005 11:33, Daniel Jacobowitz wrote:
> On Tue, Mar 29, 2005 at 11:13:53AM -0500, Jon Ringle wrote:
> > On Monday 28 March 2005 23:58, Daniel Jacobowitz wrote:
> > > Look harder :-)  sniff_core_bfd is disabled if you provide the new
> > > mechanism.  It should be all you need.
> >
> > I assume that you are refering to the test that is done at the beginning
> > of sniff_core_bfd():
> >   /* Don't sniff if we have support for register sets in CORE_GDBARCH. 
> > */ if (core_gdbarch && gdbarch_regset_from_core_section_p (core_gdbarch))
> > return NULL;
> >
> > Howerver, the value of core_gdbarch is not the same as the gdbarch that
> > was used for the set_gdbarch_regset_from_core_section() causing the test
> > to fail and fall through to the core_file_fns loop.
>
> The two being different is not a problem; however, the question is why
> they are so different that they do not both pass through wherever you
> are calling set_gdbarch_regset_from_core_section.
>
> At least two gdbarches will be constructed before the core file is
> opened, but you only show one call to
> set_gdbarch_regset_from_core_section.
>
> Where did you put it?

I put a call to set_gdbarch_regset_from_core_section at the end of 
arm_linux_init_abi(), just like ppc_linux_init_abi().


  reply	other threads:[~2005-03-29 16:39 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
2005-03-29 16:19       ` Jon Ringle
2005-03-29 16:33         ` Daniel Jacobowitz
2005-03-29 16:39           ` Jon Ringle [this message]
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=200503291139.15566.jon.ringle@comdial.com \
    --to=jon.ringle@comdial.com \
    --cc=gdb@sources.redhat.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