Hi Henning.<br><br>Thanks a lot for your answer.<br><br>Currently, the machine does not report any hardware problem; Solaris 10 has a service called Fault Manager, which is running on my machine, and it has not reported any error or problem related to it.<br>
<br>At this moment, I am testing a Openser installation compiled using an optimized version of GCC released by Sun to be used on Sparc Systems; this release is based on gcc 4, and at this time, OpenSER has been running for almost 18 hours without crash.<br>
<br>I will inspect the core file again, and I will be posting what I find.<br><br>Best regards, and thanks again.<br><br>Sergio Gutierrez.<br><br><br><br><div class="gmail_quote">On Thu, Feb 28, 2008 at 5:19 AM, Henning Westerholt <<a href="mailto:henning.westerholt@1und1.de">henning.westerholt@1und1.de</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">On Thursday 28 February 2008, Sergio Gutierrez wrote:<br>
> My OpenSER 1.3 installation running on Solaris Sparc is facing random and<br>
> unexpected crashes, in appearance related to timer process.<br>
><br>
> The last core presents the following backtrace<br>
><br>
> #0 0xfe977a04 in get_expired_dlgs (time=4233810208) at dlg_timer.c:194<br>
> #1 0xfe977540 in dlg_timer_routine (ticks=7980, attr=0x0) at<br>
> dlg_timer.c:210<br>
> #2 0x000a839c in timer_ticker (timer_list=0x15ec00) at timer.c:275<br>
> #3 0x000a80ec in run_timer_process (tpl=0x1b8088, do_jiffies=1) at timer.c<br>
><br>
> :357<br>
><br>
> #4 0x000a8668 in start_timer_processes () at timer.c:386<br>
> #5 0x00035ea8 in main_loop () at main.c:873<br>
> #6 0x000397c4 in main (argc=-4195024, argv=0x150e9c) at main.c:1372<br>
><br>
><br>
> Thanks in advance for any hint you can give me.<br>
<br>
</div>Hi Sergio,<br>
<br>
signal 10 is SIGBUS on solaris. This could be caused from an invalid address<br>
alignment, a segmention fault on a physical address and a object hardware<br>
error (wikipedia).<br>
<br>
The first crashes were both caused from a get_all_ucontact, triggered by a<br>
timer. This crash is now another timer, deletion of expired dialogs,<br>
strange.. Is this machine otherwise stable, when (openser release) does this<br>
crashes started?<br>
<br>
Do you have already inspected with the debugger the datastructures in the code<br>
of the get_expired_dlgs functions? Perhaps there is something wrong in<br>
there..<br>
<br>
Cheers,<br>
<font color="#888888"><br>
Henning<br>
</font></blockquote></div><br>