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/9893] New: LD_AUDIT - misaligned _dl_call_pltexit parameter causing crash in audit library
Date: Tue, 24 Feb 2009 20:08:00 -0000 [thread overview]
Message-ID: <20090224200809.9893.olsajiri@gmail.com> (raw)
The outregs parameter (struct La_x86_64_retval pointer) of _dl_call_pltexit
function is not aligned to 16. This is causing crash in the audit library.
When the audit library touches the lrv_xmm0 (or lrv_xmm1) member of the
La_x86_64_retval, gcc will emit 'movaps' instructions which expect a
parameter aligned to 16, otherwise it segfaults.
In email discussion H.J. Lu mentioned: "According to x86-64 psABI,
La_x86_64_retval should be aligned at 16byte"
(http://gcc.gnu.org/ml/gcc/2009-02/msg00346.html)
The issue can be reproduced by using attached audit.c as the audit library.
Here is the gdb session record showing the issue:
> ...
> (gdb) b _dl_call_pltexit
> Function "_dl_call_pltexit" not defined.
> Make breakpoint pending on future shared library load? (y or [n]) y
> Breakpoint 1 (_dl_call_pltexit) pending.
> (gdb) r
> Starting program: /opt/crash
> symbol __libc_start_main
> symbol printf
>
> Breakpoint 1, _dl_call_pltexit (l=0x7ffff7ffd000, reloc_offset=0,
> inregs=0x7fffffffe418, outregs=0x7fffffffe3c8) at dl-runtime.c:408
> 408 {
> (gdb)
--
Summary: LD_AUDIT - misaligned _dl_call_pltexit parameter causing
crash in audit library
Product: glibc
Version: 2.8
Status: NEW
Severity: normal
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
GCC build triplet: x86_64-*-linux-gnu
GCC host triplet: x86_64-*-linux-gnu
GCC target triplet: x86_64-*-linux-gnu
http://sourceware.org/bugzilla/show_bug.cgi?id=9893
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2009-02-24 20:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 20:08 olsajiri at gmail dot com [this message]
2009-02-24 20:10 ` [Bug libc/9893] " olsajiri at gmail dot com
2009-02-24 20:35 ` hjl dot tools at gmail dot com
2009-03-10 19:39 ` olsajiri at gmail dot com
2009-03-14 23:58 ` 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=20090224200809.9893.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).