When i wrote my plugins i got errors like this when the memory got corrupted. Can you use valgrind and look if there is anything suspicous? (Or attach the output since it normally produces a very long list of errors and it sometimes hard to tell which are real errors)
On Mon, 2004-02-23 at 18:23, NM Lists wrote: > Le Mon 23/02/2004 à 15:47, Tom Foottit a écrit : > > > This looks like a GTK problem and not a Multisync problem. Your 68 level > > deep backtrace leaves Multisync code after level 1 when we call > > bonobo_main() in main(). > > > > Considering you are running Gnome from CVS the possibility that > > something in GTK is broken is rather large. > > I had figured that myself already; you should however keep at mind the > possibility that this is a MultiSync bug which manifests itself only in > later versions of GTK. Nothing else seems to do it. > > I'm going to file a bug report somewhere at gnome.org, I guess, anyway. > > > > ------------------------------------------------------- > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > Build and deploy apps & Web services for Linux with > a free DVD software kit from IBM. Click Now! > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > _______________________________________________ > Multisync-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/multisync-devel ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id56&alloc_id438&op=click _______________________________________________ Multisync-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/multisync-devel
