Hello,
Run your webserver inside gdb. When you get the crash, enter the
'backtrace' command.
http://httpd.apache.org/dev/debugging.html
You'll need the debuggin symbols. If OpenSuse does not provide them, you'll
need to compile Wt from source. If you recompile Wt, the crash may be gone
forever. I spent a lot of time trying to find out why the wt-homepage
example crashed on Debian 7.0, to no avail: the moment I recompiled, even
with the same compiler and libraries, the problem disappeared. I'm not
saying that'll happen to you but don't be surprised. Some bugs are very
very very tricky. Others simply don't exist.
On Mon, May 25, 2015 at 9:09 PM, Helmar Sgpangenber <hspangenb...@frey.de>
wrote:
> How can I produce a stack trace?
> Helmar
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> witty-interest mailing list
> witty-interest@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/witty-interest
>
--
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
witty-interest mailing list
witty-interest@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/witty-interest
