Discussion:
[Wt-interest] WGLWidget and libwtfcgi
Helmar Spangenberg
2015-05-08 14:14:29 UTC
Permalink
Hello,

is there any issue on on the WGLWidget with regards to libwtfcgi?

I wrote a program containing a slightly modified version of the
teapot-example. Using libwthttp everything works fine. However, switching
over to libwtfcgi, wtfcgi crashes - apache says: wtfcgi: connect():
Connection refused

I made some checks - I have the feeling that the crash happens in the
constructor of WGLWidget.

Can anybody give me a hint what I could do to get rid of the crashes?

The underlying system is SuSE-13.2 (64 bit).

Thank you,
Helmar
Wim Dumon
2015-05-14 14:58:04 UTC
Permalink
Not that I know of, I believe it should work. Can you get a stack trace?

Wim.
Post by Helmar Spangenberg
Hello,
is there any issue on on the WGLWidget with regards to libwtfcgi?
I wrote a program containing a slightly modified version of the
teapot-example. Using libwthttp everything works fine. However, switching
Connection refused
I made some checks - I have the feeling that the crash happens in the
constructor of WGLWidget.
Can anybody give me a hint what I could do to get rid of the crashes?
The underlying system is SuSE-13.2 (64 bit).
Thank you,
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
https://lists.sourceforge.net/lists/listinfo/witty-interest
Helmar Sgpangenber
2015-05-25 19:09:38 UTC
Permalink
How can I produce a stack trace?
Helmar
Pau Garcia i Quiles
2015-05-25 21:16:14 UTC
Permalink
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.
Post by Helmar Sgpangenber
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
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)
Helmar Sgpangenber
2015-05-26 10:18:48 UTC
Permalink
Helmar Spangenberg <***@...> writes:

Seems it was all my fault - sorry. The permissions of /var/run/wt were
somwewhat screwed up, thus no communication was possible between the
different fcgi-instances.

Anyway, thanks a lot for your help!! :-)
Helmar

Loading...