From: Daniel Berlin <dan@cgsoftware.com>
To: Elena Zannoni <ezannoni@cygnus.com>
Cc: gdb@sources.redhat.com
Subject: Re: symbol readers cleanup?
Date: Thu, 19 Jul 2001 11:52:00 -0000 [thread overview]
Message-ID: <87hew8agzd.fsf@cgsoftware.com> (raw)
In-Reply-To: <15191.8714.904809.561064@krustylu.cygnus.com>
Elena Zannoni <ezannoni@cygnus.com> writes:
> Hi,
>
> I am in the process of trying to clean up the intefaces between the
> various modules that deal with reading object file formats, debugging
> symbols, and the like.
>
> It seems that gdb has come to a state of really high entropy in this
> area (if you thought that wait_for_inferior was mess, try looking at
> this code!).
>
> There are files that should deal with object files formats
> dbxread.c -- aout
> xcoffread.c -- xcoff
> coffread.c -- coff
> somread.c -- som
> nlmread.c -- NetWare
> dstread.c -- Apollo
> mipsread.c -- ecoff
> os9kread.c -- os9k
> elfread.c -- elf
>
> And files that should deal with debug formats:
> stabsread.c
> mdebugread.c
> hpread.c
> dwarfread.c
> dwarf2read.c
>
> The distinction however is fuzzy. The interfaces are not clean.
> Several cases refer to stabs functions even though stab is not the
> debug format in use, etc. Some platform specific files are all self
> contained, like nlm and dst. In all this mess there is partial-stab.h
> as well.
>
>
> Mind if I clean up a bit?
>
Please, do.
mdebugread, for instance, still hasn't changed since before the
interfaces to build partial symbols and symbol blocks moved into
buildsym.
It still makes them by hand.
> Elena
--
"You know how it is when you're reading a book and falling
asleep, you're reading, reading... And all of a sudden you
notice your eyes are closed? I'm like that all the time.
"-Steven Wright
next prev parent reply other threads:[~2001-07-19 11:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-19 10:09 Elena Zannoni
2001-07-19 11:48 ` Andrew Cagney
2001-07-19 12:05 ` Elena Zannoni
2001-07-19 11:52 ` Daniel Berlin [this message]
2001-07-19 15:12 ` Jim Blandy
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=87hew8agzd.fsf@cgsoftware.com \
--to=dan@cgsoftware.com \
--cc=ezannoni@cygnus.com \
--cc=gdb@sources.redhat.com \
/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