31 Aug
2011
31 Aug
'11
1:15 p.m.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
maybe an idea where to start?
der.brandt
at least we now know that it is not the plugins that are problematic.
i fear that you really have to trim down the patch to a minimal set of objects that trigger the crash.
fmsdr IOhannes
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk5dGsAACgkQkX2Xpv6ydvQ5yQCdE2e1/JJ6TQEGp9jFnZ1rJXDt
MBMAmwXH/c7BzFRGfjqLmkMI1/WDHxiQ
=WQaQ
-----END PGP SIGNATURE-----
Zitat von brandt@subnet.at:
> sorry first...i was out of office...lets start
>
>
> Zitat von "IOhannes m zmoelnig" zmoelnig@iem.at:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On 2011-08-30 13:16, brandt@subnet.at wrote:
>>> now we are dealing with GEM: ver: 0.93.1
>>
>> cool, thanks
>>
>>>>>>
>>>>>> therefore:
>>>>>> could you try to move the "gem_imageMAGICK.dll" out of the way?
>>>>>> (effectively disabling this plugin).
>>>>>>
>>
>> so could we try that again?
>> for simplicity, could you move _all_ plugins into a disabled/ folder (or
>> rename all of them; or delete all of them),
>
>
> i put everything into disabled folder except Gem.dll
>
>
>
>
> and then post the verbose2
>> logs (and -noprefs -lib Gem ...)
>
> as attached
>>
>> gmasdr
>> IOhannes
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.11 (GNU/Linux)
>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>>
>> iEYEARECAAYFAk5c0M8ACgkQkX2Xpv6ydvS/8gCg7NJ4ywqa5dDStauFj5iKO8Qj
>> Zx0AoNKgldy53r+XT6u6H04cJy9w7Uqv
>> =Q3MS
>> -----END PGP SIGNATURE-----