From: Andrew Cagney <ac131313@redhat.com>
To: Klee Dienes <klee@apple.com>
Cc: Jim Blandy <jimb@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Handle stack underflow in dbxread.c
Date: Mon, 18 Nov 2002 12:42:00 -0000 [thread overview]
Message-ID: <3DD950C1.6090405@redhat.com> (raw)
In-Reply-To: <3908551A-FB2A-11D6-84AF-00039396EEB8@apple.com>
> On Monday, November 18, 2002, at 12:40 PM, Jim Blandy wrote:
>
>
> Okay, that looks like a good change to me --- please commit it.
>
> But rather than making pop_context a hairy macro, could you make it a
> function in buildsym.c, right after push_context?
>
>
> Gladly. Committed the following:
>
>
>
> 2002-11-18 Klee Dienes <kdienes@apple.com>
>
> * buildsym.h (pop_context): Convert to function, defined in
> buildsym.c.
> * buildsym.c: Include gdb_assert.h.
> (pop_context): Implement as C function. Add check for stack
> underflow.
> * dbxread.c (process_one_symbol): Complain and stop processing
> that symbol if we are already at the top of the context stack for
> a function-end N_FUN (this would imply an umatched RBRAC). Ditto
> when processing N_RBRAC.
BTW, can you please put some sort of equivalent comment back?
> -/* Macro "function" for popping contexts from the stack. Pushing is
> - done by a real function, push_context. This returns a pointer to a
> - struct context_stack. */
> -
> -#define pop_context() (&context_stack[--context_stack_depth]);
Andrew
next prev parent reply other threads:[~2002-11-18 20:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-15 1:02 Klee Dienes
2002-11-15 12:18 ` Jim Blandy
2002-11-15 13:19 ` Klee Dienes
2002-11-18 9:57 ` Jim Blandy
2002-11-18 11:16 ` Klee Dienes
2002-11-18 12:42 ` Andrew Cagney [this message]
2002-11-18 13:06 ` Klee Dienes
2002-11-18 13:18 ` Andrew Cagney
2002-11-18 13:43 ` Klee Dienes
2002-11-18 13:18 ` Jim Blandy
2002-11-18 13:53 ` Klee Dienes
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=3DD950C1.6090405@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@redhat.com \
--cc=klee@apple.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