Hey Antonio,
2013/12/13 Antonio Mancina <[email protected]>
> Hi all,
>
> I've got this simple test case:
>
>
> ============= wt_app.h ==========================
> #ifndef WTAPP_H_
> #define WTAPP_H_
>
> #include <Wt/WApplication>
> #include <Wt/WTabWidget>
> #include <Wt/WContainerWidget>
>
> class WtApp : public Wt::WApplication {
> public:
> WtApp( const Wt::WEnvironment& env);
> ~WtApp() {}
>
> private: // members
> Wt::WTabWidget theTabWidget;
> Wt::WContainerWidget theCW1;
> Wt::WContainerWidget theCW2;
> };
>
>
> #endif /* WTAPP_H_ */
> ==================================================
>
> ============= wt_app.cpp =========================
> #include "wtapp.h"
>
> #include <Wt/WContainerWidget>
> #include <Wt/WTabWidget>
>
> WtApp::WtApp(const Wt::WEnvironment& env)
> : Wt::WApplication(env),
> theTabWidget(),
> theCW1(),
> theCW2() {
>
> root()->addWidget(&theTabWidget);
>
> theTabWidget.addTab(&theCW1, "ContainerWidget1");
> theTabWidget.addTab(&theCW2, "ContainerWidget2");
> }
> ===================================================
>
>
> As you can see, instead of allocating widgets on the heap, I'm
> trying to deal just with stack allocations.
>
> When I ctrl-C the process, in wt-3.2.1 everything goes fine, while
> in wt-3.3.1 I've a glibc error of double free or corruption.
>
> Here
>
> http://pastebin.com/QVkRRkAv
>
> I pasted the corresponding stacktrace. It might seem that the dealloca-
> tion is not correctly coped with, although the declaration order should
> be ok.
> I did not dig that much into the wt-code for lack of time: maybe
> someone might shed a bit of light upon this?
>
> Thanks all,
> Antonio
>
>
>
>
> ------------------------------------------------------------------------------
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of how application performance
> affects their revenue. With AppDynamics, you get 100% visibility into your
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics
> Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
> _______________________________________________
> witty-interest mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/witty-interest
>
Could you tell please, why do you need to allocate objects in stack?
Almost all of Wt classes has pointer semantic and Wt cares about
ownership.
There is no benefit from stacked-allocated objects from the POV
of performance, because the Wt itself creates objects in heap
almost always.
IMO, you just wasting you time.
--
// Dmitriy.
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
witty-interest mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/witty-interest