From: Andrew Cagney <ac131313@redhat.com>
To: Kris Warkentin <kewarken@qnx.com>
Cc: binutils@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: Adding QNX core-file support to bfd
Date: Mon, 27 Jan 2003 17:19:00 -0000 [thread overview]
Message-ID: <3E356A0E.5080902@redhat.com> (raw)
In-Reply-To: <0eba01c2c32b$aedcef40$0202040a@catdog>
A technical objective of GDB is to selectively support multiple core
file formats simultaneously. I don't know that adding #ifdef's to BFD
is in line with that objective. I think the first thing to do is
investigate what BFD changes are neededed to eliminate these #ifdef's.
> (Posted to both binutils and gdb since there is overlap on who supports core
> files)
>
> Our core files require special support and I was hoping that someone might
> be able to tell me a better way to do it than we currently do.
>
> Right now, we have a special elfcore_grok_qnx_note() function that is called
> in elf.c in much the same way as elfcore_grok_netbsd_note() is called (check
> the namedata for a string and call the function if it matches).
It looks like a dispatch table is needed so that both the QNX and can
have their support conditionally linked in.
> The problem with this is that all of that code and the support functions for
> reading our registers, status, etc. is wrapped in #ifdef __QNXTARGET__ which
> is defined at configure time. I believe that this is the sort of clutter
> that you want to avoid but unfortunately, we rely on some of our definitions
> and structures to extract the corefile information.
What exactly is this support code? Keep in mind that all of the support
functions et.al. will need to be included in a GDB distribution.
Andrew
next prev parent reply other threads:[~2003-01-27 17:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-23 22:06 Kris Warkentin
2003-01-24 8:51 ` Nick Clifton
2003-01-24 15:08 ` Kris Warkentin
2003-01-27 17:19 ` Andrew Cagney [this message]
2003-01-27 18:49 ` Kris Warkentin
2003-01-29 17:48 ` Kris Warkentin
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=3E356A0E.5080902@redhat.com \
--to=ac131313@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=gdb@sources.redhat.com \
--cc=kewarken@qnx.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