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: Mon, 18 Nov 2002 09:57:00 -0000 [thread overview]
Message-ID: <vt2u1ielqs7.fsf@zenia.red-bean.com> (raw)
In-Reply-To: <E13D33E9-F8DF-11D6-8CFC-00039396EEB8@apple.com>
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?
Klee Dienes <klee@apple.com> writes:
> My bad:
>
>
>
>
> On Friday, November 15, 2002, at 03:02 PM, Jim Blandy wrote:
>
> >
> > The context in your first patch hunk doesn't appear anywhere in my
> > sources. Is this diff against the current sources?
next prev parent reply other threads:[~2002-11-18 17:57 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 [this message]
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=vt2u1ielqs7.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