public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "siddhesh at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/15465] LD_DEBUG=symbols crashes when program name is not available
Date: Wed, 29 May 2013 16:06:00 -0000	[thread overview]
Message-ID: <bug-15465-131-WzDGgKI930@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15465-131@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=15465

Siddhesh Poyarekar <siddhesh at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #1 from Siddhesh Poyarekar <siddhesh at redhat dot com> ---
Fixed in master:

commit b937534868c8d7aec3b6d645bf5fd657bbfccd42
Author: Siddhesh Poyarekar <siddhesh@redhat.com>
Date:   Wed May 29 21:30:20 2013 +0530

    Avoid crashing in LD_DEBUG when program name is unavailable

    Resolves: #15465

    The program name may be unavailable if the user application tampers
    with argc and argv[].  Some parts of the dynamic linker caters for
    this while others don't, so this patch consolidates the check and
    fallback into a single macro and updates all users.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2013-05-29 16:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-14  9:52 [Bug dynamic-link/15465] New: " siddhesh at redhat dot com
2013-05-14  9:57 ` [Bug dynamic-link/15465] " siddhesh at redhat dot com
2013-05-29 16:06 ` siddhesh at redhat dot com [this message]
2014-06-13 17:49 ` fweimer at redhat dot com

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=bug-15465-131-WzDGgKI930@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).