public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aj at suse dot de" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/13580] crash in glibc with dlopen and math functions
Date: Tue, 10 Jan 2012 10:55:00 -0000 [thread overview]
Message-ID: <bug-13580-131-71lbN8O6mB@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13580-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13580
--- Comment #1 from Andreas Jaeger <aj at suse dot de> 2012-01-10 10:54:16 UTC ---
LD_DEBUG=symbols shows:
19500: symbol=floor; lookup in file=/usr/lib64/libgmodule-2.0.so.0
[0]
19500: symbol=floor; lookup in file=/usr/lib64/libglib-2.0.so.0 [0]
19500: symbol=floor; lookup in file=/lib64/libpthread.so.0 [0]
19500: symbol=floor; lookup in file=/lib64/libc.so.6 [0]
19500: symbol=floor; lookup in file=/lib64/libdl.so.2 [0]
19500: symbol=floor; lookup in file=/lib64/libpcre.so.0 [0]
19500: symbol=floor; lookup in file=/lib64/librt.so.1 [0]
19500: symbol=floor; lookup in file=/lib64/ld-linux-x86-64.so.2 [0]
19500: symbol=floor; lookup in
file=/usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so [0]
19500: symbol=floor; lookup in file=/usr/lib64/librsvg-2.so.2 [0]
19500: symbol=floor; lookup in file=/usr/lib64/libgdk_pixbuf-2.0.so.0
[0]
19500: symbol=floor; lookup in file=/usr/lib64/libgobject-2.0.so.0
[0]
19500: symbol=floor; lookup in file=/usr/lib64/libglib-2.0.so.0 [0]
19500: symbol=floor; lookup in file=/lib64/libpthread.so.0 [0]
19500: symbol=floor; lookup in file=/lib64/libc.so.6 [0]
19500: symbol=floor; lookup in file=/usr/lib64/libgio-2.0.so.0 [0]
19500: symbol=floor; lookup in file=/usr/lib64/libpangocairo-1.0.so.0
[0]
19500: symbol=floor; lookup in file=/usr/lib64/libpango-1.0.so.0 [0]
19500: symbol=floor; lookup in file=/usr/lib64/libcairo.so.2 [0]
19500: symbol=floor; lookup in file=/usr/lib64/libcroco-0.6.so.3 [0]
19500: symbol=floor; lookup in file=/usr/lib64/libxml2.so.2 [0]
19500: symbol=floor; lookup in file=/lib64/libm.so.6 [0]
Segmentation fault
It seems that PLT is not setup yet and this call fails:
call __get_cpu_features@plt
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2012-01-10 10:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 9:49 [Bug libc/13580] New: " aj at suse dot de
2012-01-10 10:39 ` [Bug libc/13580] " allan at archlinux dot org
2012-01-10 10:55 ` aj at suse dot de [this message]
2012-01-10 12:18 ` aj at suse dot de
2012-01-10 13:30 ` idoenmez at suse dot de
2012-01-11 21:50 ` arekm at maven dot pl
2012-01-11 21:53 ` pluto at agmk dot net
2012-01-14 23:06 ` vapier at gentoo dot org
2012-01-24 12:19 ` aj at suse dot de
2014-02-16 18:27 ` jackie.rosen at hushmail dot com
2014-02-16 18:28 ` ismail at donmez dot ws
2014-05-28 19:45 ` schwab at sourceware dot org
2014-06-13 14:10 ` 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-13580-131-71lbN8O6mB@http.sourceware.org/bugzilla/ \
--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).