Re: solaris - segmentation fault on startup

[Fred Kiefer]

Could you please print out the value of ptr->offset ?
I expect that this is 0 in your case, which would break the  calculation
in the inline function decode().
If this is the case we might just add a  zero test to the function or
try to find out why this is the case for you.
If the value isn't zero, we need to take a closer look at that function.
I must admit I don't understand what it actually does :-(

Fred


On 31.08.2013 13:25, Riccardo Mottola wrote:
> I compiled all current SVN core with GCC 4.8 on solaris 10, when I try
> to start Ink as a test, I get a segmentation fault.
> 
> GDB reveals:
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 1 (LWP 1)]
> -[GSTimeZone initWithName:data:] (self=0x19a690,
>     _cmd=0xfe8bd5a0 <_OBJC_SELECTOR_TABLE+224>, name=0x1037c0,
>     data=<optimized out>) at NSTimeZone.m:3119
> 3119              types[i].offset = decode(ptr->offset);
> 
> (gdb) bt
> #0  -[GSTimeZone initWithName:data:] (self=0x19a690,
>     _cmd=0xfe8bd5a0 <_OBJC_SELECTOR_TABLE+224>, name=0x1037c0,
>     data=<optimized out>) at NSTimeZone.m:3119
> #1  0xfe6818fc in -[GSPlaceholderTimeZone initWithName:data:]
> (self=0x6da90,
>     _cmd=<optimized out>, name=0x1037c0, data=0x199ad0) at NSTimeZone.m:554
> #2  0xfe681054 in -[NSTimeZone initWithName:] (self=0x6da90,
>     _cmd=0xfe8bd7a8 <_OBJC_SELECTOR_TABLE+744>, name=0x1037c0)
>     at NSTimeZone.m:2083
> #3  0xfe6851e8 in +[NSTimeZone systemTimeZone] (
>     self=0xfe8bddfc <_OBJC_Class_NSTimeZone>, _cmd=<optimized out>)
>     at NSTimeZone.m:1657
> #4  0xfe680b80 in +[NSTimeZone defaultTimeZone] (
>     self=0xfe8bddfc <_OBJC_Class_NSTimeZone>,
>     _cmd=0xfe8bd5a8 <_OBJC_SELECTOR_TABLE+232>) at NSTimeZone.m:1315
> #5  0xfe680668 in -[NSLocalTimeZone secondsFromGMTForDate:] (self=0x6dad8,
>     _cmd=0xfe89bde8 <_OBJC_SELECTOR_TABLE>, aDate=0x15d118) at
> NSTimeZone.m:637
> #6  0xfe53f3c0 in offset (d=0x15d118, tz=0x6dad8) at NSCalendarDate.m:111
> #7  -[NSCalendarDate descriptionWithCalendarFormat:locale:] (self=0x15d118,
>     _cmd=0xfe89bf78 <_OBJC_SELECTOR_TABLE+400>,
>     format=0xfe8ac9d4 <_OBJC_INSTANCE_3>, locale=0x192cb0)
>     at NSCalendarDate.m:2433
> #8  0xfe538904 in -[NSCalendarDate descriptionWithCalendarFormat:] (
>     self=0x15d118, _cmd=0xfe8ac954 <_OBJC_SELECTOR_TABLE+80>,
> ---Type <return> to continue, or q <return> to quit---
>     format=0xfe8ac9d4 <_OBJC_INSTANCE_3>) at NSCalendarDate.m:1838
> #9  0xfe5f8434 in NSLogv (format=format@entry=0xfc40de94
> <_OBJC_INSTANCE_17>,
>     args=args@entry=0xffbff2c8) at NSLog.m:375
> #10 0xfe5f87ec in NSLog (format=0xfc40de94 <_OBJC_INSTANCE_17>) at
> NSLog.m:291
> #11 0xfc3c84cc in -[XIMInputServer ximStyleInit] (self=0x18ced0,
>     _cmd=0xfc40db60 <_OBJC_SELECTOR_TABLE+176>) at XIMInputServer.m:285
> #12 0xfc3c81d4 in -[XIMInputServer ximInit:] (self=0x18ced0,
>     _cmd=0xfc40dae8 <_OBJC_SELECTOR_TABLE+56>, dpy=0x12af08)
>     at XIMInputServer.m:221
> #13 0xfc3c7d34 in -[XIMInputServer initWithDelegate:display:name:] (
>     self=0x18ced0, _cmd=<optimized out>, aDelegate=0x0, dpy=0x12af08,
>     name=<optimized out>) at XIMInputServer.m:85
> #14 0xfc3b47bc in -[XGServer _initXContext] (self=0x1717a0,
>     _cmd=<optimized out>) at XGServer.m:464
> #15 0xfc3b3c50 in -[XGServer initWithAttributes:] (self=0x1717a0,
>     _cmd=0xff09674c <_OBJC_SELECTOR_TABLE+96>, info=0x0) at XGServer.m:475
> #16 0xfeedc994 in +[GSDisplayServer serverWithAttributes:] (
>     self=0xff0968c4 <_OBJC_Class_GSDisplayServer>,
>     _cmd=0xff0506f8 <_OBJC_SELECTOR_TABLE+1672>, attributes=0x0)
>     at GSDisplayServer.m:189
> #17 0xfed3acd4 in -[NSApplication _init] (self=0x15f8b0,
>     _cmd=0xff050750 <_OBJC_SELECTOR_TABLE+1760>) at NSApplication.m:884
> #18 0xfe60fbd8 in -[NSObject performSelector:withObject:] (self=0x15f8b0,
> 
> the name of the data is:
> (gdb) po name
> Europe/Rome
> 
> Which sounds sensible. What could be going wrong?
> 
> Riccardo