Hi all,

So I finally got gem compiling via terminal on OSX. Thanks Chris especially for all your time. I think I sent you all any src changes that allowed be to compile. (bgra!)

So now that its compiled I have a few strange issues. Both these issues happen on Jamie's May 8th 2006 build, and my own from last week. (from a CVS update from last week)

Oh and before I forget can someone please change the gem splash screen to say the CVS revision, branch name, or even just "CVS" since I'm tired of seeing "gem 0.90" when its CVS.

The first issue is that pd will crash after I destroy a fullscreen, borderless,menubarless gemwin. The window goes away, there is a pause, then Pd crashes. This is currently happening with pd-extended (stable 0.38-4).

Here is the trace:

$ gdb GNU gdb 5.3-20030128 (Apple version gdb-330.1) (Fri Jul 16 21:42:28 GMT 2004) Copyright 2003 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "powerpc-apple-darwin". (gdb) attach 602 Attaching to process 602. Reading symbols for shared libraries . done Reading symbols for shared libraries ................................................................................................................. done 0x9000b468 in select () (gdb) continue Continuing. Program received signal EXC_BAD_ACCESS, Could not access memory. clock_unset (x=0x79708) at m_sched.c:57 57 m_sched.c: No such file or directory. in m_sched.c (gdb) bt #0 clock_unset (x=0x79708) at m_sched.c:57 #1 0x00039680 in clock_set (x=0x0, setticks=2294439040) at m_sched.c:74 #2 0x02012e74 in dispatchGemWindowMessages() () #3 0x0003a024 in sched_tick (next_sys_time=2294439040) at m_sched.c:357 #4 0x0003a2f0 in m_scheduler () at m_sched.c:453 #5 0x00002240 in _start (argc=530048, argv=0x2d13ad0, envp=0x1388) at /SourceCache/Csu/Csu-47/crt.c:267 #6 0x8fe1a278 in __dyld__dyld_start ()

Looks like a PD problem, but its happening when I'm going a gem operation.

Also I noticed using the test patch (attached), that If I try and create the fullscreen, borderless, menubarless window after opening PD I still get a titlebar on the gemwin. But If I first send "create, 1" and then destroy it, and then create the fullscreen window with the very same message then it works... Seems like the create,1 sets something in the gemwin that is not in the initial load state.

This is not a bug, but its strange, so I'm mentioning it. For some reason each time I attach to the PD process on OSX, gdb stops immediatly with:

(gdb) attach 1018 Attaching to process 1018. Reading symbols for shared libraries . done Reading symbols for shared libraries ................................................................................................................ done 0x9000b468 in select () (gdb) bt #0 0x9000b468 in select () #1 0x0003ee20 in sys_domicrosleep (microsec=4, pollem=-1073743056) at s_inter.c:166 #2 0x0003a380 in m_scheduler () at m_sched.c:481 #3 0x00002240 in _start (argc=503524, argv=0x1, envp=0x0) at /SourceCache/Csu/Csu-47/crt.c:267 #4 0x8fe1a278 in __dyld__dyld_start ()

I have to type "continue" to actually start debugging a Pd crash.

Thanks Jamie for the hints on using "attach" to gdb pd-extended!

Since this only happens when destroying the window its not much of a big deal, but obviously should be fixed for the next release.

Thanks all!

.b.