Bug#225687: tetex-bin: LaTeX segfaults when run by auctex on filename with space
>> On Sun Jan 4 11:08:10 2004 -0500, Frank Küster <frank@kuesterei.ch> wrote:
F> Matt Swift <swift@alum.mit.edu> schrieb:
>> Package: tetex-bin
>> Version: 2.0.2-5.1
>> Severity: normal
>>
>> This invocation of LaTeX segfaults:
>>
>> latex --src-specials '\nonstopmode\input{foo bar.tex}'
>>
>> (AucTeX invokes LaTeX this way.)
>>
>> If you remove the --src-specials or the space in the filename, or you
>> invoke it by
>>
>> latex 'foo bar.tex'
>>
>> it behaves as expected.
F> Yes, indeed. But what I expect (and what happens on my system) is the
F> following error:
F> And this error is a limitation of TeX's \input primitive, which reads
Right.
F> But I think spaces in filenames should be avoided in any case
F> (how do you know whether there's one space or two in a row?).
IMHO, the only reason to avoid spaces is the fact that TeX does not
understand them. In Windows, most people (myself included) use spaces
in almost all filenames without any confusion over doubled spaces.
F> So let's sort things:
F> - There is a built-in TeX limitation which could be regarded as a
F> wishlist bug. And it seems possible that this can be fixed.
Though I think it would be an improvement, I am not interested in
having TeX on Linux work with spaces in filenames. I agree that would
be a wishlist upstream bug.
F> - There is a bug in the src-specials implementation that leads to a
F> segfault instead of a TeX error
This is the bug I intended to describe.
F> Both are in principle upstream issues
How do you know the problem causing the segfault is in upstream code
rather than in Debian code?
Reply to: