I cleaned out my tree and started from scratch. The above issue has disappeared. Please ignore. On Wed, Apr 18, 2018 at 11:16 AM, Partha Bagchi <partha1b@xxxxxxxxx> wrote: > I'm getting what would be possibly a kernel panic when I launch RC2. > > lldb gives me the following back trace: > > (lldb) bt > * thread #1, queue = 'com.apple.main-thread', stop reason = signal SIGABRT > * frame #0: 0x00007fff5d2acb6e libsystem_kernel.dylib`__pthread_kill + > 10 > frame #1: 0x00007fff5d477080 libsystem_pthread.dylib`pthread_kill + > 333 > frame #2: 0x00007fff5d2081ae libsystem_c.dylib`abort + 127 > frame #3: 0x00007fff5d306822 libsystem_malloc.dylib`free + 521 > frame #4: 0x0000000100427bab gimp-2.10`gimp_core_config_class_intern_init > + 1099 > frame #5: 0x00000001019548cd libgobject-2.0.0.dylib`g_type_class_ref > + 1197 > frame #6: 0x000000010195453d libgobject-2.0.0.dylib`g_type_class_ref > + 285 > frame #7: 0x000000010195453d libgobject-2.0.0.dylib`g_type_class_ref > + 285 > frame #8: 0x000000010195453d libgobject-2.0.0.dylib`g_type_class_ref > + 285 > frame #9: 0x000000010195453d libgobject-2.0.0.dylib`g_type_class_ref > + 285 > frame #10: 0x000000010195453d libgobject-2.0.0.dylib`g_type_class_ref > + 285 > frame #11: 0x0000000101940dab libgobject-2.0.0.dylib`g_object_new_valist > + 91 > frame #12: 0x0000000101940aba libgobject-2.0.0.dylib`g_object_new + > 154 > frame #13: 0x00000001004307eb gimp-2.10`gimp_rc_new + 187 > frame #14: 0x00000001002e51ad gimp-2.10`gimp_load_config + 349 > frame #15: 0x000000010000f31c gimp-2.10`app_run + 364 > frame #16: 0x000000010001210f gimp-2.10`main + 975 > frame #17: 0x00007fff5d15c015 libdyld.dylib`start + 1 > (lldb) > > Mitch, I cced you. I hope you don't mind. > > Thanks, > Partha > _______________________________________________ gimp-developer-list mailing list List address: gimp-developer-list@xxxxxxxxx List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
