From: David Carlton <carlton@math.stanford.edu>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com,
Elena Zannoni <ezannoni@redhat.com>, Jim Blandy <jimb@redhat.com>
Subject: Re: [rfc] block.{h,c}
Date: Wed, 19 Feb 2003 17:05:00 -0000 [thread overview]
Message-ID: <ro1fzqk9p6p.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <3E537F1B.2010601@redhat.com>
On Wed, 19 Feb 2003 07:56:59 -0500, Andrew Cagney <ac131313@redhat.com> said:
> Can it eventually contain the few remaining scraps of block* code
> found in blockframe.c (hint, hint :-)?
I don't see why not. The functions in blockframe.c that start with
block_* or blockvector_* are:
struct blockvector *
blockvector_for_pc_sect (register CORE_ADDR pc, struct sec *section,
int *pindex, struct symtab *symtab)
struct blockvector *
blockvector_for_pc (register CORE_ADDR pc, int *pindex)
struct block *
block_for_pc_sect (register CORE_ADDR pc, struct sec *section)
struct block *
block_for_pc (register CORE_ADDR pc)
struct frame_info *
block_innermost_frame (const struct block *block)
All of those seem like reasonable candidates for block.{c,h}.
> I think it is consistent with GDB's current overall direction - more
> modular with *.[hc] relating to specific objects or sets of objects.
That's my feeling, too.
David Carlton
carlton@math.stanford.edu
next prev parent reply other threads:[~2003-02-19 17:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-18 22:41 David Carlton
2003-02-19 12:52 ` Andrew Cagney
2003-02-19 17:05 ` David Carlton [this message]
2003-02-19 21:21 ` Jim Blandy
2003-02-19 21:40 ` David Carlton
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=ro1fzqk9p6p.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--cc=ac131313@redhat.com \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@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