Abdelrazak Younes wrote:
> Peter Kümmel wrote:
>> Abdelrazak Younes wrote:
>>> Edwin Leuven wrote:
>>>> Abdelrazak Younes wrote:
>>>>> This patch solves it. Committing now.
>>>> i still see a crash...
>>> Could you set a breakpoint at breakpoint at the beginning of
>>> Dialogs::disconnect(string const & name) in frontends/Dialogs.C and
>>> continue step by step until you see the crash?
>>>
>>> Abdel.
>>>
>>>
>>
>> This hack avoids the crash:
>>
>> Index: frontends/controllers/Dialog.C
>> ===================================================================
>> --- frontends/controllers/Dialog.C (revision 14889)
>> +++ frontends/controllers/Dialog.C (working copy)
>> @@ -115,7 +115,7 @@
>> if (!view().isVisible())
>> return;
>>
>> - controller().clearParams();
>> +// controller().clearParams();
>
> That means that controller() points to nothing real. That's quite weird
> considering that it is a boost::scoped_ptr and that it is set in
> Dialog::setController(Controller * i) and never release after that.
>
> Could you put a breakpoint in this method (setController) before opening
> the dialog in order to verify that controller_ptr_ is correctly reset?
>
I've tested this and it does not crash at the new line
void Dialog::setController(Controller * i)
{
BOOST_ASSERT(i && !controller_ptr_.get());
controller_ptr_.reset(i);
controller().clearParams(); //<- new
}
so somethings happens with the parameters until I click the close button.
> Georg, Lars, did you do the BOOST upgrade to 1.34RC at the end? This
> problem might be related to that.
>
> Abdel.
>
>
--
Peter Kümmel
