FS#30469 - [Boost,Wt,GCC?] Boost + Wt + c++11 - segmentation fault

Attached to Project: Arch Linux
Opened by Marco Gulino (GuLinux) - Thursday, 28 June 2012, 06:32 GMT
Last edited by Ionut Biru (wonder) - Tuesday, 24 July 2012, 11:52 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Ionut Biru (wonder)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I'm experiencing segmentation faults using Wt and Boost with c++0x/c++11 code.
Apparently for it to work boost needs to recompiled with c++11 support. I don't know if this could break boost applications not using c++11.
I have this problem both with my code, and with Wt examples.
Steps to reproduce:

Install boost (extra repo) and wt (community).
Download Wt examples source code (for instance, "DialogExample").
Compile without c++11:
g++ DialogExample.C -lwt -lboost_signals -lwthttp
Launch application:
./DialogExample --docroot /usr/share/Wt/ --http-address 0.0.0.0 --http-port 9090
Opening a browser to http://localhost:9090, everything seems to work fine.
Recompile DialogExample with c++11 flag:
g++ DialogExample.C -lwt -lboost_signals -lwthttp -std=c++11
Relaunch the application. Now opening a browser makes it crash.

Some system info:
kernel 3.4.4-2-ARCH #1 SMP PREEMPT; x86_64 system.
boost 1.49.0-2
wt 3.2.1-3
g++ (GCC) 4.7.1

I could provide stacktraces, but apparently segfault does not trigger always on the same spot (with some applications, on a "connect" function, with some others after thread switch).
Thanks
Marco
This task depends upon

Closed by  Ionut Biru (wonder)
Tuesday, 24 July 2012, 11:52 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in gcc 4.7.2.
Comment by Sven-Hendrik Haase (Svenstaro) - Sunday, 08 July 2012, 21:52 GMT
I get *exactly* the same behavior. This is rather annoying. I'm going to report this to upstream.
Comment by Sven-Hendrik Haase (Svenstaro) - Sunday, 08 July 2012, 21:56 GMT
Upstream bug report: http://redmine.webtoolkit.eu/issues/1350

Loading...