public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "ciro.santilli at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug testsuite/18704] Don't run bigcore test by default on make check Date: Thu, 23 Jul 2015 14:57:00 -0000 [thread overview] Message-ID: <bug-18704-4717-IcFzw7ABfp@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-18704-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=18704 --- Comment #4 from Ciro Santilli <ciro.santilli at gmail dot com> --- Ah, there is even an opt-out check on the test OSes that don't support it, I should have read it better... Ubuntu 14.04 here, kernel 3.13 here. I think I've found the culprit: cat /proc/sys/kernel/core_pattern gives: |/usr/share/apport/apport %p %s %c %P which uses apport to deal with the core. If I do: echo | sudo tee /proc/sys/kernel/core_pattern compile and run `bigcore.c`, the problem is gone, and I get a sparse core. Fedora does not use apport although it was considered: https://fedoraproject.org/wiki/Features/CrashHandling I don't know if it is technically feasible for apport to generate the sparse dump. What pointed me in this direction: https://news.ycombinator.com/item?id=7679307 I propose either of: - don't run bigcore.exp on `make check`, and remove the OS checks of the file. They are ugly anyways. Require some extra option to run it like `make check BIGCORE=true`, or `make check-bigcore` or something. - add another check: "is this linux and does core_pattern start with | ?" Ugly and brittle. How long until another system breaks this check in a different way? :-) I'll patch if you agree to those possibilities or see a better one. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2015-07-23 14:57 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-07-22 9:17 [Bug testsuite/18704] New: " ciro.santilli at gmail dot com 2015-07-22 9:32 ` [Bug testsuite/18704] " ciro.santilli at gmail dot com 2015-07-22 9:53 ` ciro.santilli at gmail dot com 2015-07-22 10:18 ` ciro.santilli at gmail dot com 2015-07-23 9:22 ` palves at redhat dot com 2015-07-23 14:57 ` ciro.santilli at gmail dot com [this message] 2015-07-31 11:44 ` ciro.santilli at gmail dot com 2015-08-02 0:44 ` xdje42 at gmail dot com 2015-08-02 13:56 ` palves at redhat dot com 2021-01-08 16:37 ` simark at simark dot ca
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-18704-4717-IcFzw7ABfp@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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).