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

; "bo...@kolpackov.net" ; "bug-make@gnu.org" Sent: Tuesday, August 21, 2018 5:34 AM Subject: Re: [bug #54529] [Makefile:5: foobar] Segmentation fault On Tue, 2018-08-21 at 06:32 +, Mark Galeck wrote: > Then why does the error say "make: ***" ?  Shouldn't Ma

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

On Tue, 2018-08-21 at 06:32 +, Mark Galeck wrote: > Then why does the error say "make: ***" ? Shouldn't Make be more > robust and assertive in such a case, if a child crashes, to inform > the user that it is not Make code? That's the format that make uses when it shows that the recipe of a

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

On Aug 21 2018, Mark Galeck wrote: >> Then why does the error say "make: ***" ? Andreas Schwab (21 August 2018 09:42) replied: > Because it's the messenger. Indeed. It remains that the message is apt to confuse a user. If the message included (at least the name of) the command that failed,

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

On Aug 21 2018, Mark Galeck wrote: > Then why does the error say "make: ***" ? Because it's the messenger. Andreas. -- Andreas Schwab, SUSE Labs, sch...@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different."

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

e bug".   From: Paul D. Smith To: Henrik Carlqvist ; Mark Galeck ; Paul D. Smith ; Martin Dorey ; bo...@kolpackov.net; bug-make@gnu.org Sent: Monday, August 20, 2018 11:33 AM Subject: [bug #54529] [Makefile:5: foobar] Segmentation fault Update of bug #54529 (project make):              

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

Update of bug #54529 (project make): Status:None => Not A Bug Open/Closed:Open => Closed ___ Follow-up Comment #4: This message: $

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

On Aug 17 2018, Mark Galeck wrote: > For this Makefile: > > ROOT := ${shell echo > /home/mgaleck/ws/mgaleck_build/mgaleck_build_refactor2/target | sed s/t/t/} > export LD_LIBRARY_PATH := ${ROOT}/usr/lib64:${LD_LIBRARY_PATH} > > foobar: > touch $@ > > > and file foobar missing, then on

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

t ; Mark Galeck ; Martin Dorey ; Paul D. Smith ; Boris Kolpackov ; bug-make Sent: Saturday, August 18, 2018 2:05 PM Subject: Re: [bug #54529] [Makefile:5: foobar] Segmentation fault I forgot to finish before hitting send. I'm unable to reproduce this in RHEL6 with make 4.1 or Solaris 10 wit

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

I forgot to finish before hitting send. I'm unable to reproduce this in RHEL6 with make 4.1 or Solaris 10 with make 4.2.1. Generally it's considered a bad idea / poor form to use LD_LIBRARY_PATH. This could easily explain why we cannot reproduce it. If you have something in that path that

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

> 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

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

Follow-up Comment #3, bug #54529 (project make): 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

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

Follow-up Comment #2, bug #54529 (project make): "Segmentation fault (core dumped)" means that you got a core file to analyze. A first simple step might be to see what generated that core file, it could be done with something like "file core". Next you might want to open the core file in a

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

Follow-up Comment #1, bug #54529 (project make): Easily put back but I think the bug reporting thing has eaten a tab. Using a semicolon rather than newline and tab would avoid that. I can't reproduce the crash. I'm using the latest from git. If I were you, I'd run it under valgrind, then

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

URL: Summary: [Makefile:5: foobar] Segmentation fault Project: make Submitted by: mark_galeck0 Submitted on: Fri 17 Aug 2018 02:46:42 PM UTC Severity: 3 - Normal Item