From owner-freebsd-alpha Sun Jun 30 12:53:32 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 43F9337B400; Sun, 30 Jun 2002 12:53:25 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 59EA643E26; Sun, 30 Jun 2002 12:53:24 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id PAA01592; Sun, 30 Jun 2002 15:53:23 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g5UJqrB20362; Sun, 30 Jun 2002 15:52:53 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15647.24981.880431.704585@grasshopper.cs.duke.edu> Date: Sun, 30 Jun 2002 15:52:53 -0400 (EDT) To: obrien@FreeBSD.ORG Cc: alpha@FreeBSD.ORG, mp@FreeBSD.ORG Subject: Re: gdb breaks world In-Reply-To: <20020630123742.C71518@dragon.nuxi.com> References: <15646.25960.889781.783159@grasshopper.cs.duke.edu> <20020629193514.A51177@dragon.nuxi.com> <15646.28621.258621.69134@grasshopper.cs.duke.edu> <20020629214620.A56685@dragon.nuxi.com> <15647.23464.742291.557283@grasshopper.cs.duke.edu> <20020630123742.C71518@dragon.nuxi.com> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org David O'Brien writes: > On Sun, Jun 30, 2002 at 03:27:36PM -0400, Andrew Gallatin wrote: > > What was the rationale for how the x86 kvm-fbsd.c was brought forward > > and the alpha kvm-fbsd.c was left behind? > > I begged people to try the gdb52 port, but it turns out that there wasn't > Alpha kgdb support -- only i386 support. At the point I realized Partially my fault. I was at my office in LA for the last 3 weeks and my -current alpha back in OH was powered off, so I had no way to test the port. I should have at least looked at it, though. > everything we needed wasn't part of the gdb52 port was already 1/2 into > the import. > > > Was it intended that other platforms add support via #ifdef's to > > kvm-fbsd.c, or was it just an oversight and I should just bring the > > existing alpha kvm-fbsd.c forward? > > IMO we keep doing things too differently between our arches. I would > like to see us try to do the same thing as much as possible. I thought > maybe we could share a single kvm-fbsd.c file; but after looking at it > when I made that commit I guess not. BUT I do think we can share some > things across all arches (maybe we add a few #defines to arch headers to > help). So I expect there will need to be a kvm-fbsd-{ARCH}.c file added > with just a _few_ things in it. I agree. Most of the code is duplicated, but done in slightly different ways since we (I?) derived the kvm-fbsd.c file from existing NetBSD/alpha support. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message