Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Jiri Smid <smid@suse.cz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC/RFA] use of dwarf2 unwind informations
Date: Thu, 06 Dec 2001 15:26:00 -0000	[thread overview]
Message-ID: <20011206182624.A27183@nevyn.them.org> (raw)
In-Reply-To: <s8vk7ylt15f.fsf@naga.suse.cz>

On Thu, Sep 27, 2001 at 11:48:28AM +0200, Jiri Smid wrote:
> Hello,
> 
>   This is code which allows gdb to use dwarf2 frame informations for
> stack unwinding.
> 
> Index: gdb/ChangeLog
> from  Jiri Smid  <smid@suse.cz>
> 
> 	* dwarf2cfi.c: New file.
> 	* dwarf2cfi.h: New file.
> 	* dwarf2read.c (dwarf_frame_offset, dwarf_frame_size): New
> 	variables.
> 	(dwarf2_read_section): Change to non static.
> 	(dwarf2_locate_sections): Add frame section recognition.
> 	* elfread.c (elf_symfile_read): Add call of frame informations build.
> 	* frame.h (frame_info): Add pointer to unwind_context.
> 	* symfile.h (dwarf2_build_frame_info): Add declaration.
> 	* gdbarch.sh (DWARF2_BUILD_FRAME_INFO): Add.
> 	* gdbarch.h, gdbarch.c: Regenerate.
> 	(FRAME_SECTION): New define.
> 	* Makefile.in: Add dwarf2cfi_h, dwarf2cfi.o, update dependencies.

I see that Jim B approved this in October, but it doesn't look like it
was ever committed.  What's the status?

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


      parent reply	other threads:[~2001-12-06 23:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-27  2:48 Jiri Smid
2001-10-02 11:12 ` Jim Blandy
2001-10-17  9:08 ` Jim Blandy
2001-10-17  9:19   ` Daniel Berlin
2001-10-17  9:26     ` Daniel Berlin
2001-12-06 15:26 ` Daniel Jacobowitz [this message]

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=20011206182624.A27183@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=smid@suse.cz \
    /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