Re: arm core analysis on x86 host

[Daniel Jacobowitz <drow@false.org>]

On Tue, Mar 29, 2005 at 11:39:15AM -0500, Jon Ringle wrote:
> 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().

Trace through the gdbarch initialization to see what's going on, then.
The core file may not be recognized as a Linux object.  This has
happened on other platforms; I don't know what was done about it, but
maybe Mark remembers.

-- 
Daniel Jacobowitz
CodeSourcery, LLC