Discussion:
tzset crash in 64-bit Cygwin
Ken Brown
2013-03-25 21:52:59 UTC
Permalink
$ uname -a
CYGWIN_NT-6.1 fiona 1.7.18(0.263/5/3) 2013-03-22 15:00 x86_64 Cygwin

$ tzset

[no output]

$ cat tzset.exe.stackdump
Exception: STATUS_ACCESS_VIOLATION at rip=00100401B13
rax=00000001004071B0 rbx=000000000022A490 rcx=00000001004071B0
rdx=0000000000000020 rsi=0000000100402C08 rdi=000000000000007B
r8 =0000000000000000 r9 =0000000000000053 r10=00000000002B084C
r11=0000000000000000 r12=000000000022A470 r13=0000000100402080
r14=0000000000000000 r15=0000000000000000
rbp=000000000000007B rsp=000000000022A400
program=C:\cygwin64a\bin\tzset.exe, pid 16124, thread main
cs=0033 ds=002B es=002B fs=0053 gs=002B ss=002B

Ken
Corinna Vinschen
2013-03-26 09:13:47 UTC
Permalink
Post by Ken Brown
$ uname -a
CYGWIN_NT-6.1 fiona 1.7.18(0.263/5/3) 2013-03-22 15:00 x86_64 Cygwin
$ tzset
[no output]
$ cat tzset.exe.stackdump
Exception: STATUS_ACCESS_VIOLATION at rip=00100401B13
rax=00000001004071B0 rbx=000000000022A490 rcx=00000001004071B0
rdx=0000000000000020 rsi=0000000100402C08 rdi=000000000000007B
r8 =0000000000000000 r9 =0000000000000053 r10=00000000002B084C
r11=0000000000000000 r12=000000000022A470 r13=0000000100402080
r14=0000000000000000 r15=0000000000000000
rbp=000000000000007B rsp=000000000022A400
program=C:\cygwin64a\bin\tzset.exe, pid 16124, thread main
cs=0033 ds=002B es=002B fs=0053 gs=002B ss=002B
Ken
Hmm. Tzset works fine for me on Windows 7 and Windows 8:

$ uname -a
CYGWIN_NT-6.1 vmbert764 1.7.18(0.263/5/3) 2013-03-22 15:00 x86_64 Cygwin
$ tzset
Europe/Berlin
$

$ uname -a
CYGWIN_NT-6.2 VMBERT864 1.7.18(0.263/5/3) 2013-03-22 15:00 x86_64 Cygwin
$ tzset
Europe/Berlin
$

Can you try to step through tzset and see what happens?


Thanks,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
Corinna Vinschen
2013-03-26 10:39:39 UTC
Permalink
Post by Ken Brown
Post by Ken Brown
$ uname -a
CYGWIN_NT-6.1 fiona 1.7.18(0.263/5/3) 2013-03-22 15:00 x86_64 Cygwin
$ tzset
[no output]
$ cat tzset.exe.stackdump
Exception: STATUS_ACCESS_VIOLATION at rip=00100401B13
rax=00000001004071B0 rbx=000000000022A490 rcx=00000001004071B0
rdx=0000000000000020 rsi=0000000100402C08 rdi=000000000000007B
r8 =0000000000000000 r9 =0000000000000053 r10=00000000002B084C
r11=0000000000000000 r12=000000000022A470 r13=0000000100402080
r14=0000000000000000 r15=0000000000000000
rbp=000000000000007B rsp=000000000022A400
program=C:\cygwin64a\bin\tzset.exe, pid 16124, thread main
cs=0033 ds=002B es=002B fs=0053 gs=002B ss=002B
Ken
$ uname -a
CYGWIN_NT-6.1 vmbert764 1.7.18(0.263/5/3) 2013-03-22 15:00 x86_64 Cygwin
$ tzset
Europe/Berlin
$
$ uname -a
CYGWIN_NT-6.2 VMBERT864 1.7.18(0.263/5/3) 2013-03-22 15:00 x86_64 Cygwin
$ tzset
Europe/Berlin
$
Can you try to step through tzset and see what happens?
Never mind. I can reproduce it with certain timezones. Stay tuned.


Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
Corinna Vinschen
2013-03-26 10:52:49 UTC
Permalink
Post by Corinna Vinschen
Post by Ken Brown
Post by Ken Brown
$ uname -a
CYGWIN_NT-6.1 fiona 1.7.18(0.263/5/3) 2013-03-22 15:00 x86_64 Cygwin
$ tzset
[no output]
$ cat tzset.exe.stackdump
Exception: STATUS_ACCESS_VIOLATION at rip=00100401B13
rax=00000001004071B0 rbx=000000000022A490 rcx=00000001004071B0
rdx=0000000000000020 rsi=0000000100402C08 rdi=000000000000007B
r8 =0000000000000000 r9 =0000000000000053 r10=00000000002B084C
r11=0000000000000000 r12=000000000022A470 r13=0000000100402080
r14=0000000000000000 r15=0000000000000000
rbp=000000000000007B rsp=000000000022A400
program=C:\cygwin64a\bin\tzset.exe, pid 16124, thread main
cs=0033 ds=002B es=002B fs=0053 gs=002B ss=002B
Ken
$ uname -a
CYGWIN_NT-6.1 vmbert764 1.7.18(0.263/5/3) 2013-03-22 15:00 x86_64 Cygwin
$ tzset
Europe/Berlin
$
$ uname -a
CYGWIN_NT-6.2 VMBERT864 1.7.18(0.263/5/3) 2013-03-22 15:00 x86_64 Cygwin
$ tzset
Europe/Berlin
$
Can you try to step through tzset and see what happens?
Never mind. I can reproduce it with certain timezones. Stay tuned.
Fixed in CVS. I create a new 64 bit Cygwin release later today.


Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
Corinna Vinschen
2013-03-26 14:53:49 UTC
Permalink
Post by Corinna Vinschen
Post by Corinna Vinschen
Post by Ken Brown
Post by Ken Brown
$ uname -a
CYGWIN_NT-6.1 fiona 1.7.18(0.263/5/3) 2013-03-22 15:00 x86_64 Cygwin
$ tzset
[no output]
$ cat tzset.exe.stackdump
Exception: STATUS_ACCESS_VIOLATION at rip=00100401B13
rax=00000001004071B0 rbx=000000000022A490 rcx=00000001004071B0
rdx=0000000000000020 rsi=0000000100402C08 rdi=000000000000007B
r8 =0000000000000000 r9 =0000000000000053 r10=00000000002B084C
r11=0000000000000000 r12=000000000022A470 r13=0000000100402080
r14=0000000000000000 r15=0000000000000000
rbp=000000000000007B rsp=000000000022A400
program=C:\cygwin64a\bin\tzset.exe, pid 16124, thread main
cs=0033 ds=002B es=002B fs=0053 gs=002B ss=002B
Ken
$ uname -a
CYGWIN_NT-6.1 vmbert764 1.7.18(0.263/5/3) 2013-03-22 15:00 x86_64 Cygwin
$ tzset
Europe/Berlin
$
$ uname -a
CYGWIN_NT-6.2 VMBERT864 1.7.18(0.263/5/3) 2013-03-22 15:00 x86_64 Cygwin
$ tzset
Europe/Berlin
$
Can you try to step through tzset and see what happens?
Never mind. I can reproduce it with certain timezones. Stay tuned.
Fixed in CVS. I create a new 64 bit Cygwin release later today.
I uploaded a 1.7.18-11 version and regenerated setup64.ini. Please
give it a try.


Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
Ken Brown
2013-03-26 17:14:51 UTC
Permalink
Post by Corinna Vinschen
Post by Corinna Vinschen
Post by Corinna Vinschen
Post by Ken Brown
Post by Ken Brown
$ uname -a
CYGWIN_NT-6.1 fiona 1.7.18(0.263/5/3) 2013-03-22 15:00 x86_64 Cygwin
$ tzset
[no output]
$ cat tzset.exe.stackdump
Exception: STATUS_ACCESS_VIOLATION at rip=00100401B13
rax=00000001004071B0 rbx=000000000022A490 rcx=00000001004071B0
rdx=0000000000000020 rsi=0000000100402C08 rdi=000000000000007B
r8 =0000000000000000 r9 =0000000000000053 r10=00000000002B084C
r11=0000000000000000 r12=000000000022A470 r13=0000000100402080
r14=0000000000000000 r15=0000000000000000
rbp=000000000000007B rsp=000000000022A400
program=C:\cygwin64a\bin\tzset.exe, pid 16124, thread main
cs=0033 ds=002B es=002B fs=0053 gs=002B ss=002B
Ken
$ uname -a
CYGWIN_NT-6.1 vmbert764 1.7.18(0.263/5/3) 2013-03-22 15:00 x86_64 Cygwin
$ tzset
Europe/Berlin
$
$ uname -a
CYGWIN_NT-6.2 VMBERT864 1.7.18(0.263/5/3) 2013-03-22 15:00 x86_64 Cygwin
$ tzset
Europe/Berlin
$
Can you try to step through tzset and see what happens?
Never mind. I can reproduce it with certain timezones. Stay tuned.
Fixed in CVS. I create a new 64 bit Cygwin release later today.
I uploaded a 1.7.18-11 version and regenerated setup64.ini. Please
give it a try.
Works for me. Thanks.

Ken

Loading...