[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: solaris - segmentation fault on startup
From: |
Riccardo Mottola |
Subject: |
Re: solaris - segmentation fault on startup |
Date: |
Sun, 01 Sep 2013 11:03:36 +0200 |
User-agent: |
Mozilla/5.0 (X11; FreeBSD i386; rv:20.0) Gecko/20100101 Firefox/20.0 SeaMonkey/2.17.1 |
Fred Kiefer wrote:
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 :-(
It actually is not 0, look:
-[GSTimeZone initWithName:data:] (self=0x199d90,
_cmd=0xfe8bd5a0 <_OBJC_SELECTOR_TABLE+224>, name=0x1036e0,
data=<optimized out>) at NSTimeZone.m:3119
3119 types[i].offset = decode(ptr->offset);
(gdb) p ptr
$1 = (struct ttinfo *) 0x199d46
(gdb) p ptr->offset
$2 = "\000\000\034 "
cheking the loop information:
(gdb) p n_types
$7 = 6
(gdb) p i
$8 = 0
it means it chokes at the first run through.
I peeked at the data:
(gdb) po name
Europe/Rome
(gdb) po data
<545a6966 00000000 00000000 00000000 00000000 00000006 00000006 00000000
000000a
But honestly, I don't too have a clue about what the function really
does and the time zone format. Although
http://en.wikipedia.org/wiki/Tz_database
Proved an interesting lecture :)
Riccardo
riccardo_mottola.vcf
Description: Vcard
- Re: solaris - segmentation fault on startup,
Riccardo Mottola <=