Looks like it's happening, surprise, during global destruction. My practical knowledge ends here :) But generally I suppose what you want is to mark all your variables so that when you trip the warning you know who it is who's freeing 0x08610b28 (and what 0x08610b28 is). (Obvisouly it can be a different value next time round!)

I know GTK has a switch to make warnings fatal, so that if you run a process in gdb you are dropped into the debugger and have a stack trace at your disposal. Probably glibc has something similar? You'll likely need the debug version of your libraries for this.