From: Andreas Schwab <schwab@redhat.com>
To: libc-hacker@sourceware.org
Subject: [PATCH] Don't leave empty element in rpath when skipping an element
Date: Mon, 14 Mar 2011 10:38:00 -0000 [thread overview]
Message-ID: <m3sjuww4vw.fsf@redhat.com> (raw)
2011-03-09 Andreas Schwab <schwab@redhat.com>
* elf/dl-load.c (_dl_dst_substitute): When skipping a path element
also skip the colon.
---
elf/dl-load.c | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/elf/dl-load.c b/elf/dl-load.c
index b19f72a..a474a0c 100644
--- a/elf/dl-load.c
+++ b/elf/dl-load.c
@@ -284,6 +284,8 @@ _dl_dst_substitute (struct link_map *l, const char *name, char *result,
name += len;
while (*name != '\0' && (!is_path || *name != ':'))
++name;
+ if (is_path && *name == ':')
+ ++name;
}
else
/* No DST we recognize. */
--
1.7.4
--
Andreas Schwab, schwab@redhat.com
GPG Key fingerprint = D4E8 DBE3 3813 BB5D FA84 5EC7 45C6 250E 6F00 984E
"And now for something completely different."
next reply other threads:[~2011-03-09 18:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 10:38 Andreas Schwab [this message]
2011-03-30 11:44 ` Andreas Schwab
2011-03-30 13:31 ` Andreas Schwab
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=m3sjuww4vw.fsf@redhat.com \
--to=schwab@redhat.com \
--cc=libc-hacker@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).