April 2008 - Darwin-dev - lists.apple.com

Re: strptime cannot parse date older than 1938
by Martin Costabel 24 Apr '08

24 Apr '08

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com User-agent: Thunderbird 2.0.0.12 (Macintosh/20080213) The Y2038 bug is the unix stamp time range(1970-2038)? I know that and know what difference of long between 32 and 64. But I think strptime is not relative to this issue,since the struct tm store each date parts in a int or a char*,not like the unix timestamp store as a long. Well, on the Mac it only works if you compile for a 64bit architecture. btw:The "older" word cannot be used to compare tow date? If so,I am Sorry for my bad English.. -- Martin _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.app… Surf Chen wrote: The problem appears not to be the struct tm, but the conversion routine that perhaps somewhere internally uses the type time_t. And the codes works fine on my 32bit debian. You wrote "older than 1938" which is fine in English, but you did not mean 1938, you meant 2038. If in your program you write 1938 instead of 38 and %Y instead of %y, everything is OK. If you write 2038 and %Y, you get the same problem as for 38 and %y. This email sent to site_archiver(a)lists.apple.com

1 0

Re: strptime cannot parse date older than 1938
by Surf Chen 24 Apr '08

24 Apr '08

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=m6I/1KqHpxJlXRCP06AhFE+O5wyJUtFXHEsgj+Y6GtQ=; b=N89IAjwYHIlCpRZNd+xSLWyDJa4oLQYbgzXSALFqFJR9dnuK+0jZCLXrqzxd1duDZ/ZdiYyGJI1hKgS+lhcKwktanxodoFKGcFRIhuNrsIFV2Nl3SH5kh23DqWn3eXIRm3/JOxFXsqq+fLLNM1BhLvkim+g90NYKmU8nKbDc8T4= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=OWE4aKp4ufh+EFKudEDO19JhTMDKMh1XQq2GN3dzRQweNSTX3i5gNcAqNkR7Hj7CRQPsqkloQ66T9dgNPAF2A57kTWa9xWtCA7HjGzGj5NLqeP8NNWKiKykG8PgLxDFaxwh00IK1ukZij7tsCebfgNioDkQnSELQeBLhtDhfuko= The Y2038 bug is the unix stamp time range(1970-2038)? I know that and know what difference of long between 32 and 64. But I think strptime is not relative to this issue,since the struct tm store each date parts in a int or a char*,not like the unix timestamp store as a long. And the codes works fine on my 32bit debian. btw:The "older" word cannot be used to compare tow date? If so,I am Sorry for my bad English.. On Thu, Apr 24, 2008 at 2:46 PM, Martin Costabel <costabel(a)wanadoo.fr> wrote: > Surf Chen wrote: > > > > > The manpage(man 3 strptime) says: > > > > Two-digit year values, including formats %y and %D, are now interpreted > > as beginning at 1969 per POSIX requirements. Years 69-00 are > interpreted > > in the 20th century (1969-2000), years 01-68 in the 21st century > > (2001-2068). > > > > You mean "strptime cannot parse date later than 2038". > The famous Y2038 bug. > > If you compile your program with the compiler flag "-arch x86_64" or "-arch > ppc64", you get the correct result. > > -- > Martin > > > _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.app… This email sent to site_archiver(a)lists.apple.com

1 0

Re: strptime cannot parse date older than 1938
by Surf Chen 24 Apr '08

24 Apr '08

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=/FexA7PHmYNsfHhgspFyamCYQ7+e9i/0KAhSN2SVoP4=; b=DYpeI3zFZA23z+iyuzIq0ozLdzkZV0ZDEFtNxrztZu979rW7jC9z+wgIshqTsyJ5wYQO187luuUxcU0dmKsi/Bp8qWIb3aG+XSPTIgYR48Kvzj4/SlCzQSOOEMH3HBGEurgmr2A8tgEImnx93rZWHp7h4u8DukRFN2dW0v7ByRw= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=nu1bXSV3N2YR2ZO7PM90LCQh9SwCC74I97/DAMwHMK0MIsEXwkoV+9YzSfqGqRZdV9RtGXrZwqWDGDrqgPbrBPzRkBjq3N0k/lj5GRJ+vs/VVPiwDwvvsr6Ss2FgRtGnqNJZOHv3P7RD2zA6pM4Wt55uiRlV1Rj7Ta4VabnCZW8= It is 70 ,not 69. Almost(few such as 1,Jan,2038 is parsed correctly) date strings later than 2038 is parsed as 70. On Thu, Apr 24, 2008 at 2:28 PM, Steve Checkoway <s(a)pahtak.org> wrote: > > On Apr 23, 2008, at 10:09 PM, Surf Chen wrote: > > > > > > If the parsing date > certain date,the strptime dose not work like it on > linux. > > > > On my debian box, the output is 138 > > but on Mac OSX,output is 70. > > > > I really hope you mean 69. > > > > > The manpage(man 3 strptime) says: > > > > Two-digit year values, including formats %y and %D, are now interpreted > > as beginning at 1969 per POSIX requirements. Years 69-00 are > interpreted > > in the 20th century (1969-2000), years 01-68 in the 21st century > > (2001-2068). > > > > Hmm, this seems like a bug. 69 is the number of years since 1969, but that > field should be number of years since 1900, according to the man page > ctime(3). > > -- > Steve Checkoway > > "Anyone who says that the solution is to educate the users > hasn't ever met an actual user." -- Bruce Schneier > > > > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Darwin-dev mailing list (Darwin-dev(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/darwin-dev/surfchen%40gmail.com > > This email sent to surfchen(a)gmail.com > _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.app… This email sent to site_archiver(a)lists.apple.com

1 0

Re: strptime cannot parse date older than 1938
by Martin Costabel 24 Apr '08

24 Apr '08

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com User-agent: Thunderbird 2.0.0.12 (Macintosh/20080213) The manpage(man 3 strptime) says: Two-digit year values, including formats %y and %D, are now interpreted as beginning at 1969 per POSIX requirements. Years 69-00 are interpreted in the 20th century (1969-2000), years 01-68 in the 21st century (2001-2068). You mean "strptime cannot parse date later than 2038". The famous Y2038 bug. -- Martin _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.app… Surf Chen wrote: If you compile your program with the compiler flag "-arch x86_64" or "-arch ppc64", you get the correct result. This email sent to site_archiver(a)lists.apple.com

1 0

Re: strptime cannot parse date older than 1938
by Steve Checkoway 24 Apr '08

24 Apr '08

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com On Apr 23, 2008, at 10:09 PM, Surf Chen wrote: I really hope you mean 69. The manpage(man 3 strptime) says: -- Steve Checkoway "Anyone who says that the solution is to educate the users hasn't ever met an actual user." -- Bruce Schneier _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.app… This email sent to site_archiver(a)lists.apple.com If the parsing date > certain date,the strptime dose not work like it on linux. On my debian box, the output is 138 but on Mac OSX,output is 70. Two-digit year values, including formats %y and %D, are now interpreted as beginning at 1969 per POSIX requirements. Years 69-00 are interpreted in the 20th century (1969-2000), years 01-68 in the 21st century (2001-2068). Hmm, this seems like a bug. 69 is the number of years since 1969, but that field should be number of years since 1900, according to the man page ctime(3). smime.p7s

1 0

strptime cannot parse date older than 1938
by Surf Chen 24 Apr '08

24 Apr '08

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; bh=mAiVxYaS4ZBOsRAM1QuuuMOWavwLqCF7H92V/r3vAME=; b=fRxRq9aMYdJTPAMa6pyGSYNWOxvuhoWsEEwPVRMmTjr26hIU+3+wvQ4pl3NMdQONOkA+m/aVTxXP1Ps3kr3ONzwbQojHSt+zIEGSJg3s+rJUqozY+1u8+EEIpj8B/uu1oEkxhfmo/3F4wBB2fuC8NHfsFbb2hEs0qAaSOMTpeYE= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=shs/OcLYNn2SpCiqXJ4tF6CSZEeinKXPh7yW9n/HrYQofv1nGUZvZtU2yP0VBfGglRfWHqQ1R4bC5kx1sOMIkOR3eJ/7gjH3Ypf61SD21wjUwNTrXJ/+N1nyqvoEIZU2rP62xf7BaFI5PY7FNBHR+MTd9EHCgquXF8D8j+N6WMY= If the parsing date > certain date,the strptime dose not work like it on linux. date.c: #include <stdio.h> #include <string.h> #include <time.h> int main() { char *date_str="Thu, 24-Apr-38 04:28:16 GMT"; struct tm tm; memset(&tm,0,sizeof(tm)); strptime(date_str,"%a, %d-%b-%y %H:%M:%S %Z",&tm); printf("%d\n",tm.tm_year); return 0; } gcc -o date date.c On my debian box, the output is 138 but on Mac OSX,output is 70. The manpage(man 3 strptime) says: Two-digit year values, including formats %y and %D, are now interpreted as beginning at 1969 per POSIX requirements. Years 69-00 are interpreted in the 20th century (1969-2000), years 01-68 in the 21st century (2001-2068). _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.app… This email sent to site_archiver(a)lists.apple.com

1 0

Re: crash when throwing exception
by Dmitry Markman 24 Apr '08

24 Apr '08

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com stack would help check your destructors On Apr 21, 2008, at 1:47 PM, Daniel Oberhoff wrote: Hi, Has aynone else had this before? Best Daniel Dmitry Markman _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.app… I develop a small machine learning framework for my research on both my linux machine and my osx laptop. Since a while everytime my programs throw exceptions I get a crash, and exclusively on osx. This happens with and without optimizations and the -fexceptions flag. I dont have the exact stack trace right now, but it is always the function unwind_resume_1 that crashes with a bad access to 0x0. I have actually had this before on another project and also only after quite some time of development, so it seems it only happens after the app has a certain complexity. I ignored it then, but currently it really gets annoying, as I use exceptions quite a lot, and the crash makes debugging quite tedious. PS: I hope this is the right list, as I could not find one that suited better. It really seems apple related, as I have never had this on linux (or windows for that matter). _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/dmarkman%40mac.com This email sent to dmarkman(a)mac.com This email sent to site_archiver(a)lists.apple.com

1 0

Re: crash when throwing exception
by Chris Ridd 22 Apr '08

22 Apr '08

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com On 22 Apr 2008, at 09:20, Daniel Oberhoff wrote: yes. If you can provide the code , snippet we will get clear picture of your problem & we can also help you out. I suppose I should begin trimming until I reach something resembling a minimal test case. I just wanted to probe if this sounded familiar to anyone. Otherwise I will begin building the test case when I find the time. Cheers, Chris _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.app… On Tue, 2008-04-22 at 12:18 +0530, JanakiRam wrote: Hmm, that is not straightforward. As I have mentioned before, this problem seems to only occur when an application reaches a certain level of complexity, so the "snippet" atm would be the whole app, which is a) quite large and b) not cleaned up in terms of licensing. It couldn't just be running out of stack, could it? Try increasing the stack and see if that changes anything. This email sent to site_archiver(a)lists.apple.com

1 0

Re: mach-o digital signature segment? (was: Re: mach-o section question)
by Army Research Lab 22 Apr '08

22 Apr '08

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com Thread-index: AcikmfBiLv+3ZxCNEd20BQAdT0T19A== Thread-topic: mach-o digital signature segment? (was: Re: mach-o section question) User-agent: Microsoft-Entourage/11.4.0.080122 Well, nice to know its possible AND its already been done! :D I'll go back to my mach-o parser planning now... Thanks, Cem Karan ------------------------------ Message: 14 Date: Tue, 22 Apr 2008 09:20:56 -0700 From: Andrew Myrick <amyrick(a)apple.com> Subject: Re: mach-o digital signature segment? (was: Re: mach-o section question) To: darwin-dev(a)lists.apple.com Message-ID: <672FF329-FA1C-4C6A-B279-A761CC9535CF(a)apple.com> Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes man codesign http://developer.apple.com/documentation/Security/Conceptual/CodeSigningGuid e/Introduction/chapter_1_section_1.html#//apple_ref/doc/uid/TP40005929-CH1-D ontLinkElementID_13 -Andrew On Apr 22, 2008, at 5:11 AM, Army Research Lab wrote: > A good point, I'll keep it in mind, although I think I'd like to > test both > ways. > > I just had a sudden, sideways thought; mach-o allows us to define new > segments, right? Can we put pure data into a segment? SHA-1, MD5, > etc. got > me to thinking about putting in a segment that contains the digital > signature of the rest of the mach-o data. Is that possible? More > importantly, for signed mach-o files, can the loader be set up to > check the > signature prior to running the program, each time? That might help > cut down > on viruses, etc (which are not a problem on the mac yet, but I like > to think > ahead, to prevent small problems from becoming big problems) > > As for programs that aren't yet signed, the loader could ask the > user if > they want to run the program, and if the user says yes, then the > loader > could add a new segment that signs the mach-o file with the user's > personal > key. From then on, unless the program was modified, the user would > not be > bothered. Other programs (e.g., system libraries, etc.) would ship > with > signatures, and the certs for those signatures would be installed in > the > System keychain (or whatever is the Darwin equivalent). > > Also, I know there is the whole key management problem, etc. I'm not > concerned with that here; I'm only asking, is it possible to embed the > signature in the mach-o file? > > Thanks, > Cem Karan _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.app… This email sent to site_archiver(a)lists.apple.com

1 0

Re: mach-o digital signature segment? (was: Re: mach-o section question)
by Andrew Myrick 22 Apr '08

22 Apr '08

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com man codesign http://developer.apple.com/documentation/Security/Conceptual/CodeSigningGui… -Andrew On Apr 22, 2008, at 5:11 AM, Army Research Lab wrote: Also, I know there is the whole key management problem, etc. I'm not concerned with that here; I'm only asking, is it possible to embed the signature in the mach-o file? Thanks, Cem Karan _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.app… A good point, I'll keep it in mind, although I think I'd like to test both ways. I just had a sudden, sideways thought; mach-o allows us to define new segments, right? Can we put pure data into a segment? SHA-1, MD5, etc. got me to thinking about putting in a segment that contains the digital signature of the rest of the mach-o data. Is that possible? More importantly, for signed mach-o files, can the loader be set up to check the signature prior to running the program, each time? That might help cut down on viruses, etc (which are not a problem on the mac yet, but I like to think ahead, to prevent small problems from becoming big problems) As for programs that aren't yet signed, the loader could ask the user if they want to run the program, and if the user says yes, then the loader could add a new segment that signs the mach-o file with the user's personal key. From then on, unless the program was modified, the user would not be bothered. Other programs (e.g., system libraries, etc.) would ship with signatures, and the certs for those signatures would be installed in the System keychain (or whatever is the Darwin equivalent). This email sent to site_archiver(a)lists.apple.com

1 0