GNU bug report logs - #22485
M-x compile cuts off output if signal is received!

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 22485 in the body.
You can then email your comments to 22485 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
To: bug-gnu-emacs <bug-gnu-emacs <at> gnu.org>
Subject: M-x compile cuts off output if signal is received!
Date: Fri, 29 Jan 2016 03:38:46 +0800

$ cat makefile
boom:
	seq 1111; false
boom1:
	seq 1111; true
boom2:
	seq 1111; false; m=$$?; sleep 1; exit $$m

M-x compile make boom gives

...
1039
1040
10
Compilation exited abnormally with code 2 at Fri Jan 29 03:24:38

The output is cut off!

What if things looked good, except for an important message that was cut
off?!!?

make boom1 or make boom2 are fine.

Also make boom with a fresh account works fine.

Only make boom with my
http://jidanni.org/comp/configuration/ is bad.

See also #22283 .

(emacs-version)"GNU Emacs 24.5.1 (i586-pc-linux-gnu, GTK+ Version 3.18.6)
 of 2016-01-23 on x86-csail-01, modified by Debian"

Message #8 received at 22485 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
Cc: 22485 <at> debbugs.gnu.org
Subject: Re: bug#22485: M-x compile cuts off output if signal is received!
Date: Thu, 28 Jan 2016 21:57:45 +0200

> From: 積丹尼 Dan Jacobson
> 	<jidanni <at> jidanni.org>
> Date: Fri, 29 Jan 2016 03:38:46 +0800
> 
> $ cat makefile
> boom:
> 	seq 1111; false
> boom1:
> 	seq 1111; true
> boom2:
> 	seq 1111; false; m=$$?; sleep 1; exit $$m
> 
> M-x compile make boom gives
> 
> ...
> 1039
> 1040
> 10
> Compilation exited abnormally with code 2 at Fri Jan 29 03:24:38
> 
> The output is cut off!

I cannot reproduce this.

Message #11 received at 22485 <at> debbugs.gnu.org (full text, mbox):

From: Óscar Fuentes <ofv <at> wanadoo.es>
To: 22485 <at> debbugs.gnu.org
Cc: Eli Zaretskii <eliz <at> gnu.org>,
 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
Subject: Re: bug#22485: M-x compile cuts off output if signal is received!
Date: Thu, 28 Jan 2016 22:18:38 +0100

Eli Zaretskii <eliz <at> gnu.org> writes:

>> M-x compile make boom gives
>> 
>> ...
>> 1039
>> 1040
>> 10
>> Compilation exited abnormally with code 2 at Fri Jan 29 03:24:38
>> 
>> The output is cut off!
>
> I cannot reproduce this.

I cannot reproduce it with emacs -Q either, but the problem is visible
without -Q. I remember seeing something similar on very rare occassions.

To the OP: do you see the problem with `emacs -Q' ? If the answer is
negative, can you bisect your configuration file to find the setting
that causes this bug?

For the record, I'm using

GNU Emacs 25.0.50.29 (x86_64-unknown-linux-gnu, X toolkit) of 2016-01-21

Message #14 received at 22485 <at> debbugs.gnu.org (full text, mbox):

From: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
To: Óscar Fuentes <ofv <at> wanadoo.es>
Cc: 22485 <at> debbugs.gnu.org, Eli Zaretskii <eliz <at> gnu.org>
Subject: Re: bug#22485: M-x compile cuts off output if signal is received!
Date: Fri, 29 Jan 2016 06:09:47 +0800

>>>>> "ÓF" == Óscar Fuentes <ofv <at> wanadoo.es> writes:

ÓF> I cannot reproduce it with emacs -Q either, but the problem is visible
ÓF> without -Q. I remember seeing something similar on very rare occassions.

ÓF> To the OP: do you see the problem with `emacs -Q' ? If the answer is
ÓF> negative, can you bisect your configuration file to find the setting
ÓF> that causes this bug?

Yes, something in my big mess http://jidanni.org/comp/configuration/.emacs is
triggering it.

But also in your .emacs too!

Perhaps you can see what we both do, which must trigger it. (You are
probably more of an expert than me to dig out the cause.)

For others: you also probably need a slower machine to trigger it too.

Message #17 received at 22485 <at> debbugs.gnu.org (full text, mbox):

From: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
To: Óscar Fuentes <ofv <at> wanadoo.es>
Cc: 22485 <at> debbugs.gnu.org, Eli Zaretskii <eliz <at> gnu.org>
Subject: Re: bug#22485: M-x compile cuts off output if signal is received!
Date: Wed, 02 Mar 2016 08:08:16 +0800

(compile "seq 1111; false" nil) does not have the problem.
(compile "make" nil) with the mentioned makefile does have the problem!
Interleaving runs of the above two commands showed only the latter has
the problem (here on my slow #2 machine).

But not always! Sometimes even the latter doesn't have the problem.

Yes it must be something in my configuration files I mentioned, as it
doesn't happen with emacs -Q. But what?

Message #22 received at 22485-done <at> debbugs.gnu.org (full text, mbox):

From: Glenn Morris <rgm <at> gnu.org>
To: 22485-done <at> debbugs.gnu.org
Subject: Re: bug#22485: M-x compile cuts off output if signal is received!
Date: Wed, 07 Dec 2016 15:20:15 -0500

> Yes it must be something in my configuration files I mentioned, as it
> doesn't happen with emacs -Q. But what?

You can reopen this if you ever find out.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.