From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21611 invoked by alias); 23 Jan 2003 22:06:48 -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 21570 invoked from network); 23 Jan 2003 22:06:48 -0000 Received: from unknown (HELO hub.ott.qnx.com) (209.226.137.76) by 172.16.49.205 with SMTP; 23 Jan 2003 22:06:48 -0000 Received: from smtp.ott.qnx.com (smtp.ott.qnx.com [10.0.2.158]) by hub.ott.qnx.com (8.9.3/8.9.3) with ESMTP id QAA27709; Thu, 23 Jan 2003 16:57:29 -0500 Received: from catdog ([10.4.2.2]) by smtp.ott.qnx.com (8.8.8/8.6.12) with SMTP id RAA04985; Thu, 23 Jan 2003 17:06:47 -0500 Message-ID: <0eba01c2c32b$aedcef40$0202040a@catdog> From: "Kris Warkentin" To: , Subject: Adding QNX core-file support to bfd Date: Thu, 23 Jan 2003 22:06:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-SW-Source: 2003-01/txt/msg00410.txt.bz2 (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). 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. Can anyone offer any suggestions for a more elegant way to add this support? cheers, Kris