[Top][All Lists]

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

make segmentation fault

From: Edward Welbourne
Subject: make segmentation fault
Date: Wed, 13 Nov 2002 16:03:27 +0100

I'm using GNU make from within GNU emacs using M-x compile.
A (buggy) Makefile containing only: <quote src="Makefile">

PACKAPPS = simple
        echo '<dt id=$(@:pack-index-dt-%:%)>' \
                '<a href="$(@:pack-index-dt-%:%)">$(@:pack-index-dt-%:%)</a>' \
boom: $(PACKAPPS:%=pack-index-dt-%)

</quote> will seg-fault make: <quote src="M-x compile">
cd /home/eddy/work/toys/

Compilation segmentation fault at Wed Nov 13 15:52:18

The Makefile has a bug in it: I used ":" where I meant "=" in the $(@)
variable substitutions.  However, make should be giving me a syntax
error, rude message, empty value for the bogus variable reference, or
some such - not a segfault !

I'm using <quote src="make --version">

GNU Make version 3.79.1, by Richard Stallman and Roland McGrath.
Built for i386-pc-linux-gnu
Copyright (C) 1988, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 2000
        Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A

</quote> on a <quote src="uname -a">

Linux whorl 2.2.19pre17 #1 Tue Mar 13 22:37:59 EST 2001 i686 unknown

</quote> Debian GNU/Linux box with <quote src="/proc/cpuinfo">

processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 8
model name      : Pentium III (Coppermine)
stepping        : 1
cpu MHz         : 735.028
cache size      : 256 KB
fdiv_bug        : no
hlt_bug         : no
sep_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 mmx fxsr xmm
bogomips        : 1464.72


Now that I've spotted my dumb typo, it's no problem to me, but I thunk
y'all might want to know about this.

Thanks for a wonderful tool which is so robust I was astonished to see
it segfault, for the first time (I believe) in over a decade using it,


reply via email to

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