This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug testsuite/18704] Don't run bigcore test by default on make check


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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]