I just opened and closed (in various ways) MDIndexer.gorm and I can't seem to make this happen even once.
I have no doubt you're seeing it, but it's difficult to reproduce. Am I missing a step to recreate the issue? GC On Sun, Feb 24, 2013 at 6:43 PM, Riccardo Mottola < [email protected]> wrote: > On 02/22/13 21:50, Fred Kiefer wrote: > >> >> The simplest way to find out is to run Gorm with Zombies turned on and >> see which class gets that call. As I need too long to reproduce the issue, >> it would be best if your did those checks. >> After that we will know whether the issue is in Gorm or in gui code and >> maybe we even have an idea on how to fix it. >> >> Indeed, Zombies help. > > 2013-02-25 00:19:24.328 Gorm[3852] *** -[GormWindowEditor > respondsToSelector:]: message sent to deallocated instance 0xba7923f4 > > I somehow remember it should drop into gdb by itself... but it doesn't, > where do I need to put a breakpoint to actually be able to get a stacktrace > and the responder information you ask for? > > Thanks, > Riccardo > > > > > ______________________________**_________________ > Discuss-gnustep mailing list > [email protected] > https://lists.gnu.org/mailman/**listinfo/discuss-gnustep<https://lists.gnu.org/mailman/listinfo/discuss-gnustep> > -- Gregory Casamento Open Logic Corporation, Principal Consultant yahoo/skype: greg_casamento, aol: gjcasa (240)274-9630 (Cell) http://www.gnustep.org http://heronsperch.blogspot.com
_______________________________________________ Discuss-gnustep mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnustep
