Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Kris Warkentin" <kewarken@qnx.com>
To: "Gdb-Patches@Sources.Redhat.Com" <gdb-patches@sources.redhat.com>
Subject: [patch ob] update comment in solib.c
Date: Tue, 03 Jun 2003 19:16:00 -0000	[thread overview]
Message-ID: <04d501c32a04$b4fde600$0202040a@catdog> (raw)

Applied as obvious to reflect change I made many moons ago.

2003-06-03  Kris Warkentin  <kewarken@qnx.com>

 * solib.c (solib_open): Update comment to reflect actual search order.

Index: solib.c
===================================================================
RCS file: /cvs/src/src/gdb/solib.c,v
retrieving revision 1.55
diff -c -r1.55 solib.c
*** solib.c     24 Feb 2003 19:11:04 -0000      1.55
--- solib.c     3 Jun 2003 19:12:16 -0000
***************
*** 91,96 ****
--- 91,97 ----
     * If path is absolute, look in SOLIB_ABSOLUTE_PREFIX.
     * If path is absolute or relative, look for it literally (unmodified).
     * Look in SOLIB_SEARCH_PATH.
+    * If available, use target defined search function.
     * Look in inferior's $PATH.
     * Look in inferior's $LD_LIBRARY_PATH.



                 reply	other threads:[~2003-06-03 19:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='04d501c32a04$b4fde600$0202040a@catdog' \
    --to=kewarken@qnx.com \
    --cc=gdb-patches@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