public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bob.eric.nelson at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/15845] glibc-2.18 (32-bit) segfault with i7-3770K CPU Date: Sun, 18 Aug 2013 03:46:00 -0000 [thread overview] Message-ID: <bug-15845-131-WNvXqoClpW@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-15845-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=15845 --- Comment #2 from re_nelson <bob.eric.nelson at gmail dot com> --- Further exploration of the 32-bit glibc-2.18 segfault, this time using Arch Linux as the platform on the hardware cited in the initial post, revealed the following with "--host=i686-pc-linux-gnu" passed to the configure script. 1). Using "-O3" optimization is a fix for the segfault described in the post. In the attached tarball, see "strace_glibc-2.18-i686.ok" when the 32-bit acroread application is invoked with the library built with "-O3" optimzation. The program runs to completion with no errors. 2). With CFLAGS unset, which during the build default to "-O2", the segfault occurs as shown in "trace_glibc-2.18-i686.fail", also in the attached tarball. The trace also shows the kernel's general protection error at the end, taken from dmesg. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2013-08-18 3:46 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-08-16 19:15 [Bug libc/15845] New: " bob.eric.nelson at gmail dot com 2013-08-16 19:17 ` [Bug libc/15845] " bob.eric.nelson at gmail dot com 2013-08-16 19:18 ` bob.eric.nelson at gmail dot com 2013-08-16 19:30 ` bob.eric.nelson at gmail dot com 2013-08-16 19:32 ` bob.eric.nelson at gmail dot com 2013-08-18 3:45 ` bob.eric.nelson at gmail dot com 2013-08-18 3:46 ` bob.eric.nelson at gmail dot com [this message] 2013-08-18 4:06 ` allan at archlinux dot org 2013-08-18 17:26 ` bob.eric.nelson at gmail dot com 2014-02-07 2:46 ` jsm28 at gcc dot gnu.org 2014-06-13 13:11 ` 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-15845-131-WNvXqoClpW@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: linkBe 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).