Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@arm.com>
To: msnyder@redhat.com, gdb@sources.redhat.com
Cc: Richard.Earnshaw@arm.com
Subject: GDB arm-netbsd build failure.
Date: Wed, 09 Jan 2002 11:45:00 -0000	[thread overview]
Message-ID: <200201091944.TAA22678@cam-mail2.cambridge.arm.com> (raw)


Michael,

Your latest patch

2002-01-03  Michael Snyder  <msnyder@redhat.com>

        Implement a "generate-core-file" command in gdb, save target state.

breaks any target that doesn't use ELF, since it calls a BFD function that 
is only compiled in for ELF support.

Specifically, it directly uses elfcore_write_prpsinfo which is in bfd/elf.c

Isn't there supposed to be a way of wrapping such calls through a BFD 
layer to make them format independent.  If not, then this call should only 
be made if we know that we are using ELF.

R.


             reply	other threads:[~2002-01-09 19:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-09 11:45 Richard Earnshaw [this message]
2002-01-09 12:43 ` Michael Snyder
2002-01-10  6:21   ` Richard Earnshaw
2002-01-10  6:30     ` Richard Earnshaw
2002-01-10  9:25       ` Michael Snyder

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=200201091944.TAA22678@cam-mail2.cambridge.arm.com \
    --to=rearnsha@arm.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=gdb@sources.redhat.com \
    --cc=msnyder@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