Re: Serious GORM bug

[Fred Kiefer]

On 04.01.2014 12:45, Jamie Ramone wrote:
> On Sat, Jan 4, 2014 at 7:59 AM, Fred Kiefer <address@hidden> wrote:
>> Am 04.01.2014 um 00:17 schrieb Jamie Ramone <address@hidden>:
>>
>> Well $hit! I ran on a VM with Ubuntu 13.10...same problem:
>>
>> Starting program: /SystemApps/Gorm.app/Gorm
>> [Thread debugging using libthread_db enabled]
>> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
>> 2014-01-03 20:09:11.042 Gorm[6849] QueryTree window is 25186477 (root 373
>> cwin root 373)
>> 2014-01-03 20:09:11.102 Gorm[6849] QueryTree window is 25186476 (root 373
>> cwin root 373)
>> 2014-01-03 20:09:11.573 Gorm[6849] QueryTree window is 25186511 (root 373
>> cwin root 373)
>> 2014-01-03 20:09:11.574 Gorm[6849] QueryTree window is 25186510 (root 373
>> cwin root 373)
>>
>>
>> Could you please explain where these messages come from? Are you using
>> unaltered GNUstep code, or if you have changes would you mind telling us
>> about them? This looks a bit like the debugging code I used in the backend
>> to track down the other Gorm bug, which actually turned out to be a Gorm
>> bug.
>> If you want to see more information on what is happening inside of the
>> running Gorm application start it with parameters such as
>> "--GNU-Debug=dflt",  "--GNU-Debug=NSEvent" or  "--GNU-Debug=NSDragging"
>> (typed from memory, better check the correct names in the source code).
>>
> 
> To my knowledge, it's unaltered. I didn't touch any line of Gorm's code,
> just downloaded and compiled it. OK, I'll try those.

I am back at my computer and found the source of this message. You have
a window manager that uses double parent windows and there we had a left
over NSLog call. I turned that into NSDebugLLog.

Sadly this wont help with your real issue.

Fred