[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] Fix unset PATH crash
|
From: |
Masamichi HOSODA |
|
Subject: |
Re: [PATCH] Fix unset PATH crash |
|
Date: |
Tue, 03 Mar 2015 20:36:09 +0900 (JST) |
> On 2015-03-01 02:07 AM, Masamichi HOSODA wrote:
>> On Windows, lilypond crashes when the environment variable PATH is not
>> set.
>>
>> ```
>> C:\tmp\lilypond-2.19.16-0.mingw\$_OUTDIR\usr\bin>set PATH=
>>
>> C:\tmp\lilypond-2.19.16-0.mingw\$_OUTDIR\usr\bin>lilypond
>> GNU LilyPond 2.19.16
>> terminate called after throwing an instance of 'std::logic_error'
>> what(): basic_string::_S_construct null not valid
>>
>> This application has requested the Runtime to terminate it in an
>> unusual way.
>> Please contact the application's support team for more information.
>>
>> C:\tmp\lilypond-2.19.16-0.mingw\$_OUTDIR\usr\bin>
>> ```
>>
>> Even in the case of linux, this issue is a possible crash.
>> A patch file is attached.
>>
>
> Should this be added to Issue 1948
> <https://code.google.com/p/lilypond/issues/detail?id=1948>: Windows
> install clobbered system PATH and the issued be re-opened?
It seems that that issue is about Windows installer and has been fixed.
This issue that I've reported is not about Windows installer,
is about lilypond itself.
On Windows, this issue can be easily crash lilypond,
as shown in the above example.
Even linux, it is possible to crash lilypond like following commands.
```
$ cd /home/gub/gub/target/linux-64/root/usr/bin
$ unset PATH
$ lilypond
GNU LilyPond 2.19.16
terminate called after throwing an instance of 'std::logic_error'
what(): basic_string::_S_construct null not valid
Aborted (core dumped)
$
```