From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21580 invoked by alias); 20 Feb 2004 23:44:23 -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 21426 invoked from network); 20 Feb 2004 23:44:20 -0000 Received: from unknown (HELO walton.kettenis.dyndns.org) (213.93.115.144) by sources.redhat.com with SMTP; 20 Feb 2004 23:44:20 -0000 Received: from elgar.kettenis.dyndns.org (elgar.kettenis.dyndns.org [192.168.0.2]) by walton.kettenis.dyndns.org (8.12.6p3/8.12.6) with ESMTP id i1KNiEt6000931; Sat, 21 Feb 2004 00:44:14 +0100 (CET) (envelope-from kettenis@elgar.kettenis.dyndns.org) Received: from elgar.kettenis.dyndns.org (localhost [127.0.0.1]) by elgar.kettenis.dyndns.org (8.12.6p3/8.12.6) with ESMTP id i1KNiDL8027155; Sat, 21 Feb 2004 00:44:13 +0100 (CET) (envelope-from kettenis@elgar.kettenis.dyndns.org) Received: (from kettenis@localhost) by elgar.kettenis.dyndns.org (8.12.6p3/8.12.6/Submit) id i1KNiDQC027152; Sat, 21 Feb 2004 00:44:13 +0100 (CET) Date: Fri, 20 Feb 2004 23:44:00 -0000 Message-Id: <200402202344.i1KNiDQC027152@elgar.kettenis.dyndns.org> From: Mark Kettenis To: cagney@gnu.org CC: gdb@sources.redhat.com In-reply-to: <403676EB.2070803@gnu.org> (message from Andrew Cagney on Fri, 20 Feb 2004 16:06:51 -0500) Subject: Re: 32-bit gcore on amd64 References: <403542D6.2070603@gnu.org> <200402201958.i1KJwxW4000681@elgar.kettenis.dyndns.org> <403676EB.2070803@gnu.org> X-SW-Source: 2004-02/txt/msg00300.txt.bz2 Date: Fri, 20 Feb 2004 16:06:51 -0500 From: Andrew Cagney > Well, it can determine the target from ABFD. It certainly can make > the distinction between a 32-bit and a 64-bit BFD. However, some > targets, most notably ELF, are shared by various OSes. So in theory. Wonder if this is something better handled directly by GDB - who, other than gdb wants to create corefiles? Why shouldn't objdump be able to write a core file? ;-) But seriously, yes I think we should let GDB handle the gory details. BFD should only provide the basic, generic functionality. For ELF this means we'd keep the generic functionality to write core file notes (i.e. elfcore_write_note()) in BFD, but move the functions that create the OS-specific data structure inside those notes (i.e. elfcore_write_prpsinfo() and elfcore_write_prstatus()) into GDB. Mark