Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@cygnus.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Elena Zannoni <ezannoni@cygnus.com>, gdb@sources.redhat.com
Subject: Re: symbol readers cleanup?
Date: Thu, 19 Jul 2001 12:05:00 -0000	[thread overview]
Message-ID: <15191.15634.941889.803166@krustylu.cygnus.com> (raw)
In-Reply-To: <3B572B8F.4010409@cygnus.com>

Andrew Cagney writes:
 > > As first step, I would like to get rid of the duplicate files:
 > > hpread.c and the pair hp-psymtab-read.c & hp-symtab-read.c.  These
 > > last two were introduced by the hp merge, and they are just the same
 > > as hpread.c, with a logical split with symtab vs. psymtab generation
 > > routines.
 > 
 > 
 > When you say symtab, do you mean symtab or symtab?  That is the symbol 
 > table information found in the object file or the symtab structure 
 > inside of GDB?
 > 

Yes, the symtab.

:-)

Seriously, the split was made between the routines that generate a GDB
psymtab, and those that generate a gdb symtab. I.e: hp-psymtab-read.c
has hpread_build_psymtabs() (and aux routines) while hp-symtab-read.c
has hpread_psymtab_to_symtab() (and aux routines).  They both deal
only with dntt debug symbols (I think that's the name for HP's debug
format, I can't recall), reading the object file symbol table.

 > Was the splitting of hpread.c into two parts logical or arbitrary?  I 
 > mean, did it actually achieve anything or are the two halves still 
 > totally entangled.
 > 

Actually the hp functions are quite clean. They are at least self
contained. I don't care if we keep the two halves as separate or if we
keep them in a union file. As long as we don't keep both.

 > Anyway, your call :-)
 > 
 > > And see if I can do something with that awful partial-stab.h file.
 > 
 > 
 > I've several suggestions.  However, given that most of them involve some 
 > form of physical violence using a rolled up printout of that file, I'd 
 > better not mention them here :-)
 > 

Where is sac when you need him [1]? Maybe we can take a poll? The most
creative idea wins. :-) (no, please, don't do that! I am just joking!)


[1] http://sources.redhat.com/ml/gdb/2001-05/msg00196.html

 > 	Andrew

Elena


  reply	other threads:[~2001-07-19 12:05 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 [this message]
2001-07-19 11:52 ` Daniel Berlin
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=15191.15634.941889.803166@krustylu.cygnus.com \
    --to=ezannoni@cygnus.com \
    --cc=ac131313@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