[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug #54529] [Makefile:5: foobar] Segmentation fault

From: Brian Vandenberg
Subject: Re: [bug #54529] [Makefile:5: foobar] Segmentation fault
Date: Sat, 18 Aug 2018 14:52:06 -0600

> OK, the only system for which this bugs actually shows up, is work build
> server, and unfortunately, the IT guy does not know where the cores are, and
> gdb is not working.  Let me talk to him about fixing gdb and I will get back
> to you what I find from it.

This may depend on the distribution, but:

cat /proc/sys/kernel/core_pattern

The default tends contain the single word "core" with no extra frills
(though if I'm wrong look in "man -s5 core" for info on deciphering
the pattern it contains).  Assuming it just says "core" then it should
dump to whatever the current working directory is for the process
that's dying.

Additionally, the default is usually to have coredumps disabled.  You
can enable it in bash with:

ulimit -c unlimited

> The above Makefile is SSCCE for me - if I delete any elements from the above,
> even just one letter from the echo string, does not happen.

... to include spaces, tabs and newlines?  What about changing the
path that was being printed inside $(shell)?

You may want to see if you can come up with a variant on this crash
that doesn't involve characters that may change in an email.  For
example, this looks strange:

(...) | sed s/t/t}

... and makes me suspect something was lost in transliteration.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]