From: Jim Blandy <jimb@redhat.com>
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
Date: Mon, 21 Jun 2004 08:44:00 -0000 [thread overview]
Message-ID: <vt2y8mhpagm.fsf@zenia.home> (raw)
In-Reply-To: <40D69400.6090500@kay-mueller.de>
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.
next prev parent reply other threads:[~2004-06-21 8:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-18 19:29 Andrew Cagney
2004-06-21 7:06 ` Jim Blandy
2004-06-21 13:30 ` Andrew Cagney
2004-06-21 7:54 ` Michael Mueller
2004-06-21 8:44 ` Jim Blandy [this message]
2004-06-23 7:41 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vt2y8mhpagm.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=cagney@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=m.mueller99@kay-mueller.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox