public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/65479] sanitizer stack trace missing frames past #0 on powerpc64 Date: Fri, 10 Apr 2015 15:31:00 -0000 [thread overview] Message-ID: <bug-65479-4-hJa3SuO2lF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65479-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65479 --- Comment #5 from Martin Sebor <msebor at gcc dot gnu.org> --- Created attachment 35289 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35289&action=edit Test case demonstrating stability problem with backtrace_qsort. Attached is a demo program showing the stability bug in the backtrace_qsort function. The output shows the result of the current implementation (Unstable) and the expected result (Stable). A better test case wouldn't rely on the knowledge of the line_compare function and instead arrange to construct a DWARF line program with similar properties that would then cause the backtrace line problem. I suspect that would take quite a bit of effort to put together, especially if we wanted it to be reproducible across targets. I plan to work on the fast unwinding but I don't expect it to be ready in time for the 5.0 release. In the meantime, I'll post a patch to fix the test failures and maintain stability to be considered for 5.0.
next prev parent reply other threads:[~2015-04-10 15:31 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-19 23:02 [Bug sanitizer/65479] New: " msebor at gcc dot gnu.org 2015-03-20 2:49 ` [Bug sanitizer/65479] " msebor at gcc dot gnu.org 2015-04-01 1:14 ` msebor at gcc dot gnu.org 2015-04-10 2:14 ` msebor at gcc dot gnu.org 2015-04-10 6:27 ` jakub at gcc dot gnu.org 2015-04-10 15:31 ` msebor at gcc dot gnu.org [this message] 2015-04-10 15:39 ` jakub at gcc dot gnu.org 2015-04-12 23:46 ` msebor at gcc dot gnu.org 2015-04-13 18:32 ` msebor at gcc dot gnu.org 2015-04-20 1:38 ` msebor at gcc dot gnu.org 2015-06-12 0:02 ` msebor at gcc dot gnu.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-65479-4-hJa3SuO2lF@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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).