https://community.hpe.com/t5/operating-system-hp-ux/mktime-hang/m-p/5514081#M640176 <P>Your application is likely to be illegal and you gambled and lost.&nbsp; ;-)</P><P>You can't call mktime(3) or localtime(3) in a signal handler.&nbsp; I.e. it isn't async signal safe.&nbsp; See thread_safety(5)</P><P>You might be able to call gmtime(3)?</P> Tue, 31 Jan 2012 08:53:19 GMT Dennis Handly 2012-01-31T08:53:19Z https://community.hpe.com/t5/operating-system-hp-ux/mktime-hang/m-p/5513997#M640175 <P>Our system is running on HPUX11.31</P><P>We have some processes that are running forever and very very rarely one is hanging without apparent reason.&nbsp;</P><P>As these process is running on live system it's quite difficult to investiguate : maintenance people just kill then restart the process that is working fine for a long while until the next occurence.</P><P>Yet, recently we had the problem on our integration platform : one developper got the call stack when the process hangs (but it's only a JPG file)</P><P>The call stack is :</P><P>#0 0xc000000000432750:0 in __ksleep<BR />#1 0xc0000000001c51c0:0 in __mnx_sleep<BR />#2 0xc00000000013fce0:0 in __pthread_mutex_lock??<BR />#3 0xc00000000013dc90:0 in __pthread_mutex_lock??<BR />#4 0xc00000000013da20:0 in pthread_mutex_lock??<BR />#5 0xc000000000453e50:0 in __pthread_mutex_lock??<BR />#6 0xc0000000003252a0:0 in getenv+0xfa0 ()<BR />#7 0xc000000000320a90:0 in tzset+0x110 ()<BR />#8 0xc00000000031d550:0 in localtime_r+0x120 ()<BR />#9 0xc00000000031d210:0 in localtime+0x30 ()<BR />#10 0x400000000004a630:0 in fg_cur_date_asc ()<BR />#11 0x4000000000014f30:0 in fl_alarm_rcv_timer_signal ()<BR />#12 &lt;signal handler called&gt;<BR />#13 0xc00000000013db20:0 in __pthread_mutex_lock_ng+0xe0 ()<BR />#14 0xc00000000013da20:0 in pthread_mutex_lock+0x20 ()<BR />#15 0xc000000000453e50:0 in __pthread_mutex_lock+0xb0 ()<BR />#16 0xc0000000003252a0:0 in getenv+0xfa0 ()<BR />#17 0xc000000000320a90:0 in tzset+0x110 ()<BR />#18 0xc000000000328810:0 in mktime+0x150 ()<BR />#19 0x400000000004d2d0:0 in fg_dasc_to_dsec ()<BR />#20 0x4000000000017c70:0 in fl_alarm_fault ()</P><P>&nbsp;</P><P>Has anyone already observed this hang ?</P><P>Please advice,</P><P>&nbsp;</P><P>Bruno</P> Tue, 31 Jan 2012 08:04:19 GMT https://community.hpe.com/t5/operating-system-hp-ux/mktime-hang/m-p/5513997#M640175 BERTRAND_7 2012-01-31T08:04:19Z https://community.hpe.com/t5/operating-system-hp-ux/mktime-hang/m-p/5514081#M640176 <P>Your application is likely to be illegal and you gambled and lost.&nbsp; ;-)</P><P>You can't call mktime(3) or localtime(3) in a signal handler.&nbsp; I.e. it isn't async signal safe.&nbsp; See thread_safety(5)</P><P>You might be able to call gmtime(3)?</P> Tue, 31 Jan 2012 08:53:19 GMT https://community.hpe.com/t5/operating-system-hp-ux/mktime-hang/m-p/5514081#M640176 Dennis Handly 2012-01-31T08:53:19Z