Re: Segfault: latest Path and Utilities issues

[Richard Frith-Macdonald]

> On 15 Feb 2016, at 10:58, Riccardo Mottola <address@hidden> wrote:
> 
> Hi,
> 
> right now all GS applications crash for me on startup:
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to LWP 1]
> 0xbb396986 in NSUserName () at NSPathUtilities.m:1638
> 1638    {
> (gdb) bt
> #0  0xbb396986 in NSUserName () at NSPathUtilities.m:1638
> #1  0xbb428e87 in -[NSUserDefaults init] (self=0xb8ab5090,
>    _cmd=0xbb6700b8 <_OBJC_SELECTOR_TABLE+472>) at NSUserDefaults.m:1179
> #2  0xbb4298a4 in +[NSUserDefaults standardUserDefaults] (
>    self=0xbb670380 <_OBJC_Class_NSUserDefaults>,
>    _cmd=0xbb670098 <_OBJC_SELECTOR_TABLE+440>) at NSUserDefaults.m:847
> #3  0xbb42bb8e in GSPrivateDefaultsFlag (address@hidden)
>    at NSUserDefaults.m:2208
> #4  0xbb378a1e in _NSLog_standard_printf_handler (
>    message=0xbb64b060 <_OBJC_INSTANCE_1>) at NSLog.m:184
> #5  0xbb3b928a in +[NSProcessInfo processInfo] (
>    self=0xbb64ac80 <_OBJC_Class_NSProcessInfo>,
>    _cmd=0xbb642770 <_OBJC_SELECTOR_TABLE+400>) at NSProcessInfo.m:1015

Actually, looking at the source code at this line, it’s trying to print an 
error to say it can’t get process info.
That’s then caused a problem because it tried to use a function that needs 
NSProcessInfo to do the logging.
I’ve change that code to just write to stderr, so you will see the error 
message … better than crashing :-)

But it looks like you have some configure-time problem such that the wrong 
nsprocessinfo options are being configured.