Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Aleksandar Ristovski <aristovski@qnx.com>
Subject: Re: ptid from core section
Date: Fri, 05 Jun 2009 14:39:00 -0000	[thread overview]
Message-ID: <200906051539.46280.pedro@codesourcery.com> (raw)
In-Reply-To: <h0b8l4$udu$1@ger.gmane.org>

On Friday 05 June 2009 15:04:19, Aleksandar Ristovski wrote:

> What are the circumstances under which core_gdbarch would 
> not be found? If we are opening a core from a system gdb was 
> not configured for?

E.g., we still have targets using the deprecated_add_core_fns
mechanism, and AFAICS, usually those don't usually install
gdbarch sniffers for the core bfd's they handle.  E.g., 

gdb/alpha-nat.c:

/* Register that we are able to handle alpha core file formats. */

static struct core_fns alpha_osf_core_fns =
{
  /* This really is bfd_target_unknown_flavour.  */

  bfd_target_unknown_flavour,           /* core_flavour */
  default_check_format,                 /* check_format */
  default_core_sniffer,                 /* core_sniffer */
  fetch_osf_core_registers,             /* core_read_registers */
  NULL                                  /* next */
};

gdb/alpha-nat.c is pulled in by:

src/gdb/config/alpha/alpha-osf3.mh

while src/gdb/configure.tgt, indicates that alpha*-*-osf*
pulls in:

alpha*-*-osf*)
        # Target: Little-endian Alpha running OSF/1
        gdb_target_obs="alpha-tdep.o alpha-osf1-tdep.o alpha-mdebug-tdep.o"
        ;;

and, I don't see any sniffer for osf core's in alpha-osf1-tdep.c.

There may be other cores supported by bfd that end
up with similar situations, on some not-so-common configurations.

>cd bfd/
>ls *core*
aix386-core.c   corefile.c     elf32-score7.c  hppabsd-core.c  netbsd-core.c  ptrace-core.c
aix5ppc-core.c  cpu-mcore.c    elf32-score.c   hpux-core.c     osf-core.c     rs6000-core.c
cisco-core.c    cpu-score.c    elf32-score.h   irix-core.c     pei-mcore.c    sco5-core.c
coff-mcore.c    elf32-mcore.c  elfcore.h       lynx-core.c     pe-mcore.c     trad-core.c

-- 
Pedro Alves


  reply	other threads:[~2009-06-05 14:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-01 15:56 Aleksandar Ristovski
2009-06-03 14:41 ` Pedro Alves
2009-06-03 16:59   ` Aleksandar Ristovski
2009-06-03 18:41     ` Pedro Alves
2009-06-04 18:32       ` Aleksandar Ristovski
2009-06-05 13:43         ` Pedro Alves
2009-06-05 14:04           ` Aleksandar Ristovski
2009-06-05 14:39             ` Pedro Alves [this message]
2009-06-05 14:53               ` Aleksandar Ristovski
2009-06-05 16:26                 ` Pedro Alves
2009-06-05 17:54                   ` Aleksandar Ristovski
2009-06-05 19:00                     ` Pedro Alves
2009-06-05 19:03                       ` Aleksandar Ristovski

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=200906051539.46280.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=aristovski@qnx.com \
    --cc=gdb-patches@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