Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro_alves@portugalmail.pt>
To: gdb-patches@sourceware.org
Cc: Aleksandar Ristovski <aristovski@qnx.com>,
	 gdb-patches@sources.redhat.com
Subject: Re: How to fix solib path name?
Date: Wed, 08 Jul 2009 15:57:00 -0000	[thread overview]
Message-ID: <200907081649.41971.pedro@codesourcery.com> (raw)
Message-ID: <20090708155700.BoAFS5aB5Z2onnZxd9bnaBlszV7xvtzlwF_JDZEDjGs@z> (raw)
In-Reply-To: <h32efs$252$1@ger.gmane.org>

On Wednesday 08 July 2009 16:37:31, Aleksandar Ristovski wrote:

> >> What would you do differently?
> > 
> > Use "(gdb) set sysroot".
> > 
> 
> That is for absolute paths. For relative paths 
> find_and_open_solib is still a way to go IMHO - if you 
> disagree I would like to hear your rationale.

Where would this look?  What benefit does this have over
solib-search-path?  Windows dlls can be everywhere on
the filesystem.

-- 
Pedro Alves


  reply	other threads:[~2009-07-08 15:49 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-08 14:34 Danny Backx
2009-07-08 14:45 ` Aleksandar Ristovski
2009-07-08 14:51   ` Pedro Alves
2009-07-08 15:15     ` Aleksandar Ristovski
2009-07-08 15:21       ` Pedro Alves
2009-07-08 15:38         ` Aleksandar Ristovski
2009-07-08 15:49           ` Pedro Alves [this message]
2009-07-08 15:57             ` Pedro Alves
2009-07-08 17:19             ` Aleksandar Ristovski
2009-07-08 18:24               ` Pedro Alves
2009-07-08 18:30                 ` Pedro Alves
2009-07-08 14:56 ` Pedro Alves
2009-07-08 15:07   ` Pedro Alves
2009-07-08 15:31     ` Danny Backx
2009-07-08 15:45       ` Pedro Alves
2009-07-08 15:45       ` Danny Backx
2009-07-08 16:19         ` Pedro Alves
2009-07-08 16:30           ` Danny Backx
2009-07-08 16:42             ` Pedro Alves
2009-07-08 17:15   ` Pedro Alves
2009-07-08 20:46     ` Danny Backx

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=200907081649.41971.pedro@codesourcery.com \
    --to=pedro_alves@portugalmail.pt \
    --cc=aristovski@qnx.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=gdb-patches@sourceware.org \
    /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