From: Joshua Varner <jlvarner@gmail.com>
Subject: reproducible but very odd make-mode crash
Date: Tue, 24 May 2005 16:33:39 -0500 [thread overview]
Message-ID: <92a5eb47050524143311fc0d86@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 819 bytes --]
I found a file that would consitently cause the problem from my last
e-mail - same stack trace and everything. So, i updated to CVS Head
and verified the bug is still there. I then tried to strip that file
down to a minimal test case and had some very strange results. While
trying to take out anything internal to the company I started just
replacing names with the string "stuff" and discovered that the text
was mainly irrelevant, then someone suggested i change all the text to
x's so i did that and the looping continued. For some reason the loop
is more sensitive to the length of the text and whitespace changes
than to any of the actual characters in the file.
I've attached the two makefiles that cause this problem on my system.
If they seem odd, that's because at this point they are.
Josh
[-- Attachment #2: test.mk --]
[-- Type: application/octet-stream, Size: 674 bytes --]
# $Header: SSTUFFSTUFSTUFFFSTUFFSTUFFSTFSTUFFSTFSTUFFSTFSTUFFFFFstuffstuffstuffstuffstuffstuffstu $
default: all
STUFF=../../..
include $(STUFF)/stuff
STUFF = \
stuffstuffstuffstuffs \
# stuff
# stuff
# stuff
# stuff
# stuffstuffstuffs \
# stuffstuffstuffs \
## End PRGS
stuff-stuff:
stuffstuffstuffstuffstuffstuffstuffstuffstuffstuffstuffstuffstuffstuffstuff
stuffstuffstuffstuffstuffstuffstuffstuffstuffstuffstuffstuffstuffstuffstuffstuffstuffstuffstuffs
stuffstuffstuffstuffstuffstuffstuf
stuffstuffstuffstuffstuffstuffstuffstuffstuffstuffstuffstuffstuffstuffstuffstu
stuffstuffstuffstuffstuffstuffstuffstuffstuffstuffstuffstuffstuffstuffstuffstuffstuffstuffs
[-- Attachment #3: test1.mk --]
[-- Type: application/octet-stream, Size: 674 bytes --]
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxx
xxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxx
xxxxxxxxxxxxxxxxxxxxxxxx
x xxxxx
x xxxxx
x xxxxx
x xxxxx
x xxxxxxxxxxxxxxxxxx
x xxxxxxxxxxxxxxxxxx
xx xxxxxxxx
xxxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
[-- Attachment #4: Type: text/plain, Size: 142 bytes --]
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
next reply other threads:[~2005-05-24 21:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-24 21:33 Joshua Varner [this message]
2005-05-25 21:32 ` reproducible but very odd make-mode crash Joshua Varner
2005-05-25 22:49 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=92a5eb47050524143311fc0d86@mail.gmail.com \
--to=jlvarner@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).