From: Daniel Jacobowitz <drow@mvista.com>
To: Mark Kettenis <kettenis@chello.nl>
Cc: ac131313@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [i386newframe/PATCH] New i386newframe branch
Date: Sat, 03 May 2003 22:27:00 -0000 [thread overview]
Message-ID: <20030503222655.GA20680@nevyn.them.org> (raw)
In-Reply-To: <200305032053.h43KrA2U015073@elgar.kettenis.dyndns.org>
On Sat, May 03, 2003 at 10:53:10PM +0200, Mark Kettenis wrote:
> Date: Sat, 03 May 2003 15:36:25 -0400
> From: Andrew Cagney <ac131313@redhat.com>
>
>
> > I might have something else for you to toy with. I've a prototype of
> > a DWARF2 CFI unwinder ready, which is working fine in my i386newframe
> > branch. I still need to clean up several hacks, but I might be able
> > to check it in soon.
>
> Using dwarf2expr? I'd not be suprized if it makes dwarf2cfi redundant.
>
> Yes, well, my current implentation doesn't handle
> DW_CFA_def_cfa_expression yet (GCC seems not to generate it for the
> i386), but my intention is to use the code from dwarf2expr.c for it.
>
> My new implementation will replace dwarf2cfi.c. There was too much
> code in there that I didn't understand, and too many bugs. For one
> thing, dwarf2expr.c is massively leaking memory.
Wait, is dwarf2cfi.c or dwarf2expr.c leaking memory? dwarf2expr.c
shouldn't be allocating, only its clients.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-05-03 22:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-19 16:51 Mark Kettenis
2003-04-29 1:50 ` Andrew Cagney
2003-05-01 20:54 ` Mark Kettenis
2003-05-01 21:21 ` Andrew Cagney
2003-05-02 9:29 ` Mark Kettenis
2003-05-03 19:36 ` Andrew Cagney
2003-05-03 20:53 ` Mark Kettenis
2003-05-03 22:27 ` Daniel Jacobowitz [this message]
2003-05-04 0:28 ` Andrew Cagney
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=20030503222655.GA20680@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@chello.nl \
/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