public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com
Subject: Re: Macro code crasher on re-run
Date: Mon, 03 Nov 2003 21:00:00 -0000	[thread overview]
Message-ID: <vt2u15luq0y.fsf@zenia.home> (raw)
In-Reply-To: <20031103045601.GA32557@nevyn.them.org>


Daniel Jacobowitz <drow@mvista.com> writes:
> > I don't follow.  All default_macro_scope's callers check for null
> > return; it's documented to return zero at times.  So you must be
> > talking about that code in sal_macro_scope itself.  Line 39 refers to
> > sal.symtab, initialized by line 115, so you must be talking about line
> > 40.  But sal.symtab must be non-zero, or else we wouldn't reach the
> > right operand of the ||.
> > 
> > Or should I sleep and try again?
> > 
> 
> Right.  sal.symtab is nonzero.  sal.symtab->macro_table, however, is
> uninitialized.  The short-circuit if on line 40 does not trigger, but
> the remainder of sal_macro_scope assumes that sal.symtab->macro_table
> is valid.
> 
> In my case it happens to be 0xB.

Every symtab's macro_table field should be initialized, at least to
zero.  Which symtab is it?  Who creates it?

  reply	other threads:[~2003-11-03 21:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-03  4:07 Daniel Jacobowitz
2003-11-03  4:48 ` Jim Blandy
2003-11-03  4:56   ` Daniel Jacobowitz
2003-11-03 21:00     ` Jim Blandy [this message]
2003-11-03 21:04       ` Daniel Jacobowitz
2003-11-03 21:34         ` Jim Blandy
2003-11-03 21:37           ` Daniel Jacobowitz
2003-11-03 23:51             ` Jim Blandy
2003-11-07 16:29               ` Daniel Jacobowitz
2003-11-10 23:38                 ` Jim Blandy
2003-11-03 21:46           ` David Carlton
2003-11-03 22:01           ` Andrew Cagney

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=vt2u15luq0y.fsf@zenia.home \
    --to=jimb@redhat.com \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).