This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: Upcoming DWARF 3 and FORTRAN95 patches for 5.1.1 or 5.2?
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: Jim Blandy <jimb at zwingli dot cygnus dot com>
- Cc: Petr Sorfa <petrs at caldera dot com>, Daniel Berlin <dan at dberlin dot org>,gdb at sources dot redhat dot com
- Date: Wed, 23 Jan 2002 19:35:10 -0500
- Subject: Re: Upcoming DWARF 3 and FORTRAN95 patches for 5.1.1 or 5.2?
- References: <Pine.LNX.4.44.0201181449580.25029-100000@dberlin.org> <npu1tcbply.fsf@zwingli.cygnus.com>
On Wed, Jan 23, 2002 at 06:43:21PM -0500, Jim Blandy wrote:
> Another approach occurred to me just now that I wish I had thought of
> when Daniel B.'s patch first appeared. If the core of GDB could
> define a structure of functions (resembling `struct cp_abi_ops',
> `struct target_ops', etc.) that allowed a debug reader to provide its
> own set of functions for finding variables, describing their locations
> in English, and everything else we do with `enum address_class' now,
> then that would make it easy and clean to use straight Dwarf 2
> location expressions, without any translation into an allegedly
> "neutral" representation, and without contaminating the core of GDB.
>
> (This would also allow us to move some odd HP-UX-specific stuff like
> LOC_THREAD_LOCAL_STATIC out of the GDB core and into an HP-specific
> module.)
Yes! Yes yes yes yes yes yes yes!
(I like it. A lot. We should discuss details of this.)
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer