public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "olsajiri at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/3924] New: LD_AUDIT implementation causing process segfaulting
Date: Thu, 25 Jan 2007 21:49:00 -0000	[thread overview]
Message-ID: <20070125214904.3924.olsajiri@gmail.com> (raw)

There's a bug in the sysdeps/i386/dl-trampoline.S _dl_runtime_profile function
making process segfaulting. Under some conditions the 'edi' and 'esi' registers
are restored to wrong values. IMHO this could be fixed like this:

Index: sysdeps/i386/dl-trampoline.S
===================================================================
RCS file: /cvs/glibc/libc/sysdeps/i386/dl-trampoline.S,v
retrieving revision 1.2
diff -r1.2 dl-trampoline.S
116d115
<       andl $0xfffffff0, %edi  # Align stack

edi and esi registers are pushed on stack before it is alligned. In case it is
really aligned those register wont be restored properly. I tried the fix and it
is working for me. I dont know the reason for alligning the stack here, so
hopefully I'm not missing something... :)

I'm running the 2.4 version, but seems it is an issue in current sources as well.

regards
Jiri Olsa

-- 
           Summary: LD_AUDIT implementation causing process segfaulting
           Product: glibc
           Version: 2.4
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: libc
        AssignedTo: drepper at redhat dot com
        ReportedBy: olsajiri at gmail dot com
                CC: glibc-bugs at sources dot redhat dot com


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

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


             reply	other threads:[~2007-01-25 21:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-25 21:49 olsajiri at gmail dot com [this message]
2007-01-25 22:17 ` [Bug libc/3924] " olsajiri at gmail dot com
2007-02-17  7:18 ` drepper at redhat dot com
2007-04-17 21:05 ` olsajiri at gmail dot com
2007-05-16 17:36 ` olsajiri at gmail dot com
2007-08-09 20:05 ` olsajiri at gmail dot com
2007-08-14 19:17 ` olsajiri at gmail dot com
2007-08-24  2:58 ` drepper at redhat dot com
2007-08-27 20:20 ` olsajiri at gmail dot com
2007-10-07  5:32 ` drepper 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=20070125214904.3924.olsajiri@gmail.com \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).