public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bugmenot at yopmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug malloc/18391] New: 0xf749c01f __memcpy_sse2_unaligned+0x2f() in libc.so.6 (0x1c3a0bd0) Date: Sat, 09 May 2015 03:50:00 -0000 [thread overview] Message-ID: <bug-18391-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=18391 Bug ID: 18391 Summary: 0xf749c01f __memcpy_sse2_unaligned+0x2f() in libc.so.6 (0x1c3a0bd0) Product: glibc Version: 2.21 Status: NEW Severity: normal Priority: P2 Component: malloc Assignee: unassigned at sourceware dot org Reporter: bugmenot at yopmail dot com Target Milestone: --- Created attachment 8306 --> https://sourceware.org/bugzilla/attachment.cgi?id=8306&action=edit wine crash showing libc.6.so There is a bug when I attempt to play Portal 2 in wine with "firejail" (sandbox) that is the result of libc.so.6, attached is the backtrace showing the bug in libc. Version libc-2.21-3 (Arch build) -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2015-05-09 3:50 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-05-09 3:50 bugmenot at yopmail dot com [this message] 2015-05-09 3:57 ` [Bug malloc/18391] " bugmenot at yopmail dot com 2015-05-09 7:26 ` schwab@linux-m68k.org
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-18391-131@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).