Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: jan.kratochvil@redhat.com (Jan Kratochvil)
Cc: vinay@linux.vnet.ibm.com (Vinay Sridhar), gdb-patches@sources.redhat.com
Subject: Re: [patch] Re: Accessing tls variables across files causes a bug
Date: Mon, 04 Aug 2008 19:40:00 -0000	[thread overview]
Message-ID: <200808041939.m74JdIe8024034@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20080802171807.GA2755@host0.dyn.jankratochvil.net> from "Jan Kratochvil" at Aug 02, 2008 07:18:07 PM

Jan Kratochvil wrote:

> +	if (SYMBOL_CLASS (sym) != LOC_UNRESOLVED
> +	    && SYMBOL_CLASS (sym) != LOC_OPTIMIZED_OUT)
> +	  break;

I can see why this might be correct for LOC_UNRESOLVED,
but why for LOC_OPTIMIZED_OUT?

Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


  parent reply	other threads:[~2008-08-04 19:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1217480020.4755.1.camel@vinaysridhar.in.ibm.com>
2008-08-02 17:18 ` Jan Kratochvil
2008-08-04 19:36   ` Luis Machado
2008-08-05 13:26     ` [patch] Finish removing <bug-gdb@prep.ai.mit.edu> (PR gdb/1543) Jan Kratochvil
2008-08-06 12:13       ` Daniel Jacobowitz
2008-08-04 19:40   ` Ulrich Weigand [this message]
2008-08-05  8:39   ` [patch] Re: Accessing tls variables across files causes a bug Vinay Sridhar
2008-08-05 12:22     ` Daniel Jacobowitz
2008-08-06 11:16       ` Vinay Sridhar
2008-08-06 11:25         ` Daniel Jacobowitz
2008-08-06 11:43         ` Jan Kratochvil
2008-08-06 15:20           ` Jan Kratochvil
2008-08-27  4:37             ` Vinay Sridhar
2009-06-12 17:06             ` [resolved] " Jan Kratochvil

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=200808041939.m74JdIe8024034@d12av02.megacenter.de.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jan.kratochvil@redhat.com \
    --cc=vinay@linux.vnet.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