Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Siva Chandra <sivachandra@google.com>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches <gdb-patches@sourceware.org>,
	Jan Kratochvil <jan.kratochvil@redhat.com>
Subject: Re: [PATCH] Fix regression introduced by 6c659fc2c7cd2da6d2b9a3d7c38597ad3821832a
Date: Sat, 29 Nov 2014 23:52:00 -0000	[thread overview]
Message-ID: <CAGyQ6gxPdg+Ljyq4qKuhjyGuCSuharr2pZPb_aJqo+936sOfJQ@mail.gmail.com> (raw)
In-Reply-To: <201411292127.sATLRu0w027720@d03av02.boulder.ibm.com>

On Sat, Nov 29, 2014 at 1:27 PM, Ulrich Weigand <uweigand@de.ibm.com> wrote:
>> 2014-11-29  Siva Chandra Reddy  <sivachandra@google.com>
>>
>>         * eval.c (evaluate_subexp): Check that thread stack temporaries
>>         are not already enabled before enabling them.
>
> This is OK.  Good catch!

Thank you. I have now pushed it as 18ac6ffc9b119c8d55a1cd0339d47998076faf2b.


      reply	other threads:[~2014-11-29 23:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-29 18:08 Siva Chandra
2014-11-29 21:28 ` Ulrich Weigand
2014-11-29 23:52   ` Siva Chandra [this message]

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=CAGyQ6gxPdg+Ljyq4qKuhjyGuCSuharr2pZPb_aJqo+936sOfJQ@mail.gmail.com \
    --to=sivachandra@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=uweigand@de.ibm.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