From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2744 invoked by alias); 27 Jan 2003 17:19:13 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 2732 invoked from network); 27 Jan 2003 17:19:13 -0000 Received: from unknown (HELO localhost.redhat.com) (66.30.197.194) by 172.16.49.205 with SMTP; 27 Jan 2003 17:19:13 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 7EAF8406A; Mon, 27 Jan 2003 12:19:10 -0500 (EST) Message-ID: <3E356A0E.5080902@redhat.com> Date: Mon, 27 Jan 2003 17:19:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.1) Gecko/20021211 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Warkentin Cc: binutils@sources.redhat.com, gdb@sources.redhat.com Subject: Re: Adding QNX core-file support to bfd References: <0eba01c2c32b$aedcef40$0202040a@catdog> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-01/txt/msg00433.txt.bz2 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