Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: David Carlton <carlton@math.stanford.edu>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb <gdb@sources.redhat.com>
Subject: Re: struct environment
Date: Wed, 11 Sep 2002 11:33:00 -0000	[thread overview]
Message-ID: <ro1wups74wr.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <ro14rd3c5gx.fsf@jackfruit.Stanford.EDU>

On 06 Sep 2002 11:56:14 -0700, David Carlton
<carlton@math.Stanford.EDU> said:

> At some point, I'll give it a look: ALL_BLOCK_SYMBOLS is only used
> in 29 places, so it should be tractable to survey them by hand.

And of course it turns out that, in at least one place,
ALL_BLOCK_SYMBOLS calls a function that, in turn, calls
ALL_BLOCK_SYMBOLS over the exact same block.  Oops.

But I think I was making too much of the memory-management
difficulties: I'll do iterators correctly (so you can have as many of
them active as you want), and just write an ALL_ENV_SYMBOLS macro that
allocates them on the stack using alloca().

David Carlton
carlton@math.stanford.edu


  parent reply	other threads:[~2002-09-11 18:33 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-05 13:50 David Carlton
2002-09-06  8:06 ` Daniel Jacobowitz
2002-09-06 10:20   ` David Carlton
2002-09-06 10:57     ` Daniel Jacobowitz
2002-09-06 11:56       ` David Carlton
2002-09-06 12:34         ` Daniel Berlin
2002-09-06 12:41           ` Daniel Jacobowitz
2002-09-06 12:55             ` Daniel Berlin
2002-09-11 11:33         ` David Carlton [this message]
2002-09-11 11:36           ` Daniel Jacobowitz
2002-09-11 12:27             ` David Carlton
2002-09-06 14:43   ` David Carlton
2002-09-06 14:46     ` Daniel Jacobowitz
2002-09-06 14:57       ` mdebugread.c (was Re: struct environment) David Carlton
2002-09-06 15:35         ` Daniel Jacobowitz
2002-09-10 17:25   ` struct environment David Carlton
2002-09-10 17:31     ` Daniel Jacobowitz
2002-09-11 10:29       ` David Carlton
2002-09-11 10:55         ` Daniel Jacobowitz
2002-09-11 12:33         ` Daniel Berlin
2002-09-10 17:36     ` David Carlton
2002-09-16 22:03   ` Andrew Cagney
2002-09-06 15:00 ` David Carlton
2002-09-06 16:37   ` Tom Tromey
2002-09-06 17:19     ` David Carlton
2002-09-07 10:26       ` Per Bothner
2002-09-07 10:32         ` Daniel Jacobowitz
2002-09-09 11:18           ` David Carlton
2002-09-12 12:26 ` Andrew Cagney
2002-09-13  9:44   ` David Carlton
2002-09-17  0:48 ` Andrew Cagney
2002-09-17  6:41   ` Daniel Jacobowitz
2002-09-17  8:59     ` Andrew Cagney
2002-09-17  9:07       ` Daniel Jacobowitz
2002-09-17 10:54         ` Andrew Cagney
2002-09-17 11:02           ` Daniel Jacobowitz
2002-09-17 12:37             ` Andrew Cagney
2002-09-17 12:41               ` Daniel Jacobowitz
2002-09-18  8:13                 ` Andrew Cagney
2002-09-17 12:52             ` Daniel Berlin
2002-09-17 13:34               ` Daniel Jacobowitz
2002-09-17 21:51                 ` Daniel Berlin
2002-09-18  7:26                   ` Daniel Jacobowitz
2002-09-18  9:08                   ` David Carlton
2002-09-17 12:18     ` David Carlton
2002-09-17 10:29   ` David Carlton
2002-09-17 12:50     ` Daniel Berlin
2002-09-17 13:24       ` David Carlton
2002-09-18 22:26 ` Eli Zaretskii

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=ro1wups74wr.fsf@jackfruit.Stanford.EDU \
    --to=carlton@math.stanford.edu \
    --cc=drow@mvista.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