From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-18367-listarch-gdb=sources.redhat.com@sources.redhat.com>
Received: (qmail 18987 invoked by alias); 21 Jun 2004 08:44:34 -0000
Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 18974 invoked from network); 21 Jun 2004 08:44:33 -0000
Received: from unknown (HELO mx1.redhat.com) (66.187.233.31)
  by sourceware.org with SMTP; 21 Jun 2004 08:44:33 -0000
Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254])
	by mx1.redhat.com (8.12.10/8.12.10) with ESMTP id i5L8iXe1004679
	for <gdb@sources.redhat.com>; Mon, 21 Jun 2004 04:44:33 -0400
Received: from zenia.home.redhat.com (porkchop.devel.redhat.com [172.16.58.2])
	by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i5L8iV017531;
	Mon, 21 Jun 2004 04:44:32 -0400
To: Michael Mueller <m.mueller99@kay-mueller.de>
Cc: Andrew Cagney <cagney@gnu.org>, gdb@sources.redhat.com
Subject: Re: Post GDB 6.2, require new frame code
References: <40D34274.50803@gnu.org> <40D69400.6090500@kay-mueller.de>
From: Jim Blandy <jimb@redhat.com>
Date: Mon, 21 Jun 2004 08:44:00 -0000
In-Reply-To: <40D69400.6090500@kay-mueller.de>
Message-ID: <vt2y8mhpagm.fsf@zenia.home>
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-SW-Source: 2004-06/txt/msg00205.txt.bz2


Michael Mueller <m.mueller99@kay-mueller.de> writes:
> The new frame infrastructure is dwarf2 based if I understand that
> correctly. Does that mean that all stabs support will go away after
> 6.2?

No --- "GDB's new frame infrastructure" is not the same as "Dwarf 2
Call Frame Information".  The latter is just one frame unwinding
mechanism that can be plugged into the former.  "Whatever GDB always
used to do to unwind frames before Dwarf 2 CFI came along" is another
thing you can plug into the new frame infrastructure.

So, STABS support will not go away.  (STABS doesn't actually provide
unwinding information, the way Dwarf 2 does.)  But using the new frame
infrastructure means that it's trivial to make your target support
Dwarf 2 CFI when it happens to be available.

What Andrew wants to get rid of is targets that are still using
set_gdbarch_deprecated_mumble in their *_gdbarch_init and *_init_abi
functions.  STABS-based targets can be readily upgraded to leave
behind the deprecated interfaces.