Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb@sources.redhat.com
Subject: Re: optind
Date: Thu, 11 Dec 2003 14:10:00 -0000	[thread overview]
Message-ID: <20031211141008.GA26315@nevyn.them.org> (raw)
In-Reply-To: <20031210173730.GP23712@ata.cs.hacettepe.edu.tr>

On Wed, Dec 10, 2003 at 07:37:32PM +0200, Baurjan Ismagulov wrote:
> Hello, Daniel and Ian!
> 
> On Wed, Dec 10, 2003 at 12:17:15PM -0500, Daniel Jacobowitz wrote:
> > > This will
> > > normally be true, but will fail in cases where the library is
> > > controlling visibility in any of various different ways.
> > For global variables the sensible default is to use the one in the
> > executable.  This gets much more fun, of course, for function
> > addresses.
> 
> Could you please enlighten me regarding the following, too:
> 
> 1. How can the visibility of a symbol be controlled by the library?

Look of visibility in the GNU ld manual.

> 2. Why does this get much more fun for function addresses?

Because the rules on resolving symbols are much more general than the
case of copy relocations, which is quite simple.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-12-11 14:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-10 14:20 optind Baurjan Ismagulov
2003-12-10 14:49 ` optind Daniel Jacobowitz
2003-12-10 16:09   ` optind Baurjan Ismagulov
2003-12-10 16:16     ` optind Andreas Schwab
2003-12-10 16:53       ` optind Baurjan Ismagulov
2003-12-10 17:04         ` optind Ian Lance Taylor
2003-12-10 17:17           ` optind Daniel Jacobowitz
2003-12-10 17:37             ` optind Baurjan Ismagulov
2003-12-11 14:10               ` Daniel Jacobowitz [this message]
2003-12-11 15:11                 ` optind Baurjan Ismagulov

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=20031211141008.GA26315@nevyn.them.org \
    --to=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