[erlang-questions] Interesting issue...
Fri Jan 25 19:16:18 CET 2013
On 01/25/2013 05:23 PM, Pierre Fenoll wrote:
> Tried it on R15B03 on my MacBook Air (Indochina Time) and got no
> The issue cannot be reproduced on R15B03.
Great, then I close the issue, as I cannot reproduce it in any timezone
lacking DST in recent releases. It seems to have been fixed by a patch
mending some general issues with time on BSD.
> On 25 January 2013 17:10, Patrik Nyblom <
> <mailto:>> wrote:
> This ought to be fixed already in R15B03, can you please verify
> that it's not present there? I can only reproduce it in R15B01 and
> prior releases.
> On 01/15/2013 05:58 PM, Bryan Hughes wrote:
>> Hi Everyone,
>> I already submitted this to
>> <mailto:>, but figured others might be
>> interested. I found an interesting issue while traveling and
>> working through Thailand. I have been able to reproduce it on my
>> MacBook Pro using R15B01, built from source.
>> 1. Set your date to Indochina Time.
>> 2. In the shell, try executing:
>> Here is the exception that I am getting. Note that the date is a
>> validate datetime.
>> Eshell V5.9.1 (abort with ^G)
>> ** exception error: bad argument
>> in function erlang:localtime_to_universaltime/2
>> called as
>> in call from calendar:local_time_to_universal_time_dst/1
>> (calendar.erl, line 282)
>> When I set my date back to Pacific time, it works without any
>> problem -- you can switch it back and forth while in the shell
>> and either get the exception, or the correct output.
>> I was able to isolate it to function the bif.c function,
>> unfortunately my environment is not really set up to debug the
>> erlang runtime.
>> BIF_RETTYPE localtime_to_universaltime_2(BIF_ALIST_2);
>> Bryan Hughes
>> CTO and Founder / *Go Factory*
>> erlang-questions mailing list
> erlang-questions mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions