From: David Carlton <carlton@math.stanford.edu>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: gdb-patches@sources.redhat.com, Jim Blandy <jimb@redhat.com>
Subject: Re: [rfa] struct dictionary
Date: Tue, 10 Jun 2003 18:47:00 -0000 [thread overview]
Message-ID: <ro1wuft4vns.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <16102.9919.32103.991732@localhost.redhat.com>
On Tue, 10 Jun 2003 14:43:11 -0400, Elena Zannoni <ezannoni@redhat.com> said:
>> >> -static struct block *new_block (int);
>> >> +static struct block *new_block (int function);
>>
>> > can this take an enum parameter with some meaningful names?
>>
>> Well, I'm just using it as a boolean, so it seems to me that doing an
>> enum would be a little funny. How about I rename the argument to
>> function_p, or is_function, or something like that? But if you'd
>> prefer an enum, I could do something like
>>
>> enum block_type { FUNCTION, NON_FUNCTION };
>>
>> instead.
> For me the real problem is to understand the code that does the
> call. I don't know what 1 or 0 means at that point w/o going looking
> for the function definition. And I lose my train of thoughts.
That makes sense: an enum it is, then. (And in a year or two, we can
switch GDB over to C++, and have an actual boolean type, but never
mind that.)
>> >> @@ -493,6 +495,11 @@ dump_symtab (struct objfile *objfile, st
>> >> fprintf_filtered (outfile, " under ");
>> >> gdb_print_host_address (BLOCK_SUPERBLOCK (b), outfile);
>> >> }
>> >> +#if 0
>> >> + /* NOTE: carlton/2003-04-28: If we really want to be able to
>> >> + print out something here, we'll need to add an extra
>> >> + dictionary method just for that purpose. */
>> >> +
>>
>> > Hmmm, I think we should. We don't want to change gdb's behavior.
>>
>> Well, it's for a maint command, so we can really do whatever we want
>> here. But if you think that's an important part of the info, I'll add
>> the extra method.
> thanks yes.
Will do, then.
>> I'll make those changes and commit it tomorrow afternoon (unless
>> exam grading takes longer than I expect), if nobody complains; and
>> I'll be spending all day Thursday doing GDB stuff as well, so I'll be
>> available if I accidentally break anything...
> ok, great. BTW, i have started setting up the same test framework
> that Michael Chastain uses for his tests. I have done a preliminary
> run, but I screwed up the combinations of gcc and binutils to test
> with, so I'll get back to that tomorrow, and I should be able to help
> with testing for gdb6.
Cool! I miss his test runs.
David Carlton
carlton@math.stanford.edu
next prev parent reply other threads:[~2003-06-10 18:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ro1k7dbwprh.fsf@jackfruit.Stanford.EDU>
2003-05-01 3:37 ` Eli Zaretskii
2003-05-01 21:15 ` David Carlton
2003-05-20 3:58 ` David Carlton
2003-06-09 22:39 ` Elena Zannoni
2003-06-09 22:55 ` Daniel Jacobowitz
2003-06-10 0:05 ` Joel Brobecker
2003-06-10 0:24 ` Elena Zannoni
2003-06-10 15:58 ` David Carlton
2003-06-10 16:43 ` David Carlton
2003-06-10 18:37 ` Elena Zannoni
2003-06-10 18:47 ` David Carlton [this message]
2003-06-11 1:20 ` Richard Henderson
2003-06-11 23:33 ` David Carlton
2003-06-13 0:15 ` Joel Brobecker
2003-06-13 0:52 ` 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=ro1wuft4vns.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--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