This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH/i386newframe/RFC] DWARF CFI frame unwinder

From: Mark Kettenis <kettenis at chello dot nl>
To: ac131313 at redhat dot com
Cc: gdb-patches at sources dot redhat dot com
Date: Mon, 5 May 2003 15:51:56 +0200 (CEST)
Subject: Re: [PATCH/i386newframe/RFC] DWARF CFI frame unwinder
References: <200305042207.h44M7gNG023734@elgar.kettenis.dyndns.org> <3EB5DBFF.6030009@redhat.com>

   Date: Sun, 04 May 2003 23:35:27 -0400
   From: Andrew Cagney <ac131313@redhat.com>

   Using the frame obstack for memory looks right.

Well, the frame obstack only gets used for the frame cache.  When
building the frame cache temporary memory for the frame state is
allocated using xmalloc().  I considered using the obstack, but
growing objects after they've been finished seems to be impossible
without ugly hacks.

Memory for the CIE's and FDE's when reading the debug info is
allocated from the object's psymtab obstack.

Mark

Follow-Ups:
- Re: [PATCH/i386newframe/RFC] DWARF CFI frame unwinder
  - From: Andrew Cagney

References:
- [PATCH/i386newframe/RFC] DWARF CFI frame unwinder
  - From: Mark Kettenis
- Re: [PATCH/i386newframe/RFC] DWARF CFI frame unwinder
  - From: Andrew Cagney

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]