On 2013-12-13 10:19, Antonio Mancina wrote:
>
>
> 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

Not sure if it's version related, but I had a similar issue.

IIRC, the ownership of the contents initially owned by WMenuItems are 
transferred to the WStackedWidget after loading. So you're deleting 
items that will also be deleted by the TabWidget.

You can either allocate the data members and forget about them, or, 
adding a bunch of removeTab calls in your destructor might also do the 
trick.

Hope this helps,
Cheers,

Rutger




------------------------------------------------------------------------------
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

Reply via email to