From: Jim Blandy <jimb@redhat.com>
To: Klee Dienes <klee@apple.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Handle stack underflow in dbxread.c
Date: Fri, 15 Nov 2002 12:18:00 -0000 [thread overview]
Message-ID: <vt2znsamwim.fsf@zenia.red-bean.com> (raw)
In-Reply-To: <F747D18A-F878-11D6-ADE7-00039396EEB8@apple.com>
The context in your first patch hunk doesn't appear anywhere in my
sources. Is this diff against the current sources?
Klee Dienes <klee@apple.com> writes:
> 2002-11-15 Klee Dienes <kdienes@apple.com>
>
> * buildsym.h (pop_context): 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.
>
>
> 2002-11-15 Klee Dienes <kdienes@apple.com>
>
> * buildsym.h (pop_context): 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.
>
> Index: dbxread.c
> ===================================================================
> RCS file: /cvs/Darwin/src/live/cygnus/src/gdb/dbxread.c,v
> retrieving revision 1.38
> diff -u -r1.38 dbxread.c
> --- dbxread.c 2002/10/26 09:20:14 1.38
> +++ dbxread.c 2002/11/15 08:56:07
> @@ -2946,6 +2946,11 @@
> complain (&fun_end_outside_fun_complaint);
> break;
> }
> + if (context_stack_depth <= 0)
> + {
> + complain (&lbrac_mismatch_complaint, symnum);
> + break;
> + }
>
> saw_fun_start = 0;
> record_line (current_subfile, 0, last_function_start + valu);
> @@ -3027,6 +3032,11 @@
> valu += last_source_start_addr;
> #endif
>
> + if (context_stack_depth <= 0)
> + {
> + complain (&lbrac_mismatch_complaint, symnum);
> + break;
> + }
> new = pop_context ();
> if (desc != new->depth)
> complain (&lbrac_mismatch_complaint, symnum);
> Index: buildsym.h
> ===================================================================
> RCS file: /cvs/Darwin/src/live/cygnus/src/gdb/buildsym.h,v
> retrieving revision 1.5
> diff -u -r1.5 buildsym.h
> --- buildsym.h 2002/11/10 05:33:33 1.5
> +++ buildsym.h 2002/11/15 08:56:07
> @@ -22,6 +22,8 @@
> #if !defined (BUILDSYM_H)
> #define BUILDSYM_H 1
>
> +#include "gdb_assert.h"
> +
> /* This module provides definitions used for creating and adding to
> the symbol table. These routines are called from various symbol-
> file-reading routines.
> @@ -173,12 +175,6 @@
>
> EXTERN int context_stack_size;
>
> -/* 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]);
> -
> /* Non-zero if the context stack is empty. */
> #define outermost_context_p() (context_stack_depth == 0)
>
> @@ -271,6 +267,13 @@
> extern void buildsym_init (void);
>
> extern struct context_stack *push_context (int desc, CORE_ADDR valu);
> +
> +/* 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() \
> + (gdb_assert (context_stack_depth > 0), &context_stack[--context_stack_depth]);
>
> extern void record_line (struct subfile *subfile, int line, CORE_ADDR pc);
>
next prev parent reply other threads:[~2002-11-15 20:18 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 [this message]
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
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=vt2znsamwim.fsf@zenia.red-bean.com \
--to=jimb@redhat.com \
--cc=gdb-patches@sources.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