On Sat, 29 Sep 2012, Marcin Cieslak wrote:
>> On Sat, Sep 29, 2012 at 1:27 PM, Marcin Cieslak wrote:
>>> On Sat, 29 Sep 2012, Frederic Koehler wrote:
This is on a 64-bit machine. Opening the help window works fine the
first time [and
>
> On Sat, 29 Sep 2012, Frederic Koehler wrote:
>
>>
On Sat, 29 Sep 2012, Marcin Cieslak wrote:
> On Sat, 29 Sep 2012, Frederic Koehler wrote:
>
>> This is on a 64-bit machine. Opening the help window works fine the
>> first time [and
>> their are no valgrind messages], but after closing it and opening it
>> again the program
>> segfaults, and there
> On Sat, Sep 29, 2012 at 1:27 PM, Marcin Cieslak wrote:
> > On Sat, 29 Sep 2012, Frederic Koehler wrote:
> >> This is on a 64-bit machine. Opening the help window works fine the
> >> first time [and
On Sat, 29 Sep 2012, Frederic Koehler wrote:
> That's weird. On my machine _UxUxParent is also N
That's weird. On my machine _UxUxParent is also NULL
but the program runs fine [no segfaults, I can even browse icons
and create new entries for my deskbar now].
On Sat, Sep 29, 2012 at 1:27 PM, Marcin Cieslak wrote:
> On Sat, 29 Sep 2012, Frederic Koehler wrote:
>
>> This is on a 64-bit machine.
On Sat, 29 Sep 2012, Frederic Koehler wrote:
> This is on a 64-bit machine. Opening the help window works fine the
> first time [and
> their are no valgrind messages], but after closing it and opening it
> again the program
> segfaults, and there are a lot of valgrind messages about using freed
>
