From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23983 invoked by alias); 16 Nov 2005 15:43:56 -0000 Received: (qmail 23898 invoked by uid 22791); 16 Nov 2005 15:43:52 -0000 Received: from ip127.bb146.pacific.net.hk (HELO stl.com.hk) (202.64.146.127) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Wed, 16 Nov 2005 15:43:52 +0000 Received: from 241.206.17.210.dyn.pacific.net.hk ([210.17.206.241] helo=[192.168.1.10]) by stl.com.hk with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.50) id 1EcPOG-0001sj-DF for gdb@sources.redhat.com; Wed, 16 Nov 2005 23:40:04 +0800 Message-ID: <437B53B4.5000906@tausq.org> Date: Wed, 16 Nov 2005 15:43:00 -0000 From: Randolph Chung User-Agent: Debian Thunderbird 1.0.2 (X11/20050331) MIME-Version: 1.0 To: gdb@sources.redhat.com Subject: Question about ELF core file sections Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2005-11/txt/msg00318.txt.bz2 I'm trying to get core file support working on hppa64-hp-hpux11.11. I'm trying to reuse the infrastructure from corelow.c and the "new" regset_from_core_section() interface, but I'm a bit confused about how it's supposed to work. corelow.c:get_core_registers() is hardcoded to look for registers in sections ".reg", ".reg2", ".reg-xfp" -- are these section names somehow standard? I don't find these documented in the ELF specs. I see that on Linux variants, this ".reg" section is actually synthesized by bfd. This all seems to be a bit convoluted :( On HPUX, there is a program header type HP_CORE_PROC that points to a datastructure with the register info. Is there anyway to use the existing interface to get to this info? If not, it looks like I can get it to work using core_vec, but that uses an interface that is marked deprecated.... Any hints and help appreciated... randolph