Hi Antoine, First of all, sorry for the late reply.
As Phil already pointed out from the stacktrace alone it's hard to figure out what actually went wrong. It might help if you have a coredump of the crash. In gdb, run the command "generate-core-file" to create it. Then it would be good to have the core dump as well as the exact binaries (gobby and libinfinity shared libraries) that you use, with debug information. I can then dig in the state of the crashed program to see what might have gone wrong. Would it be possible for you to provide this? Thanks and cheers, Armin On Fri, 2012-06-08 at 10:44 -0400, Antoine Beaupré wrote: > On Thu, 7 Jun 2012 21:11:56 +0200, Philipp Kern <pk...@debian.org> wrote: > > Hi, > > > > On Thu, Jun 07, 2012 at 03:09:39PM -0300, Antoine Beaupré wrote: > > > After a while, gobby crashes: > > > (gobby-0.5:14500): GLib-GObject-WARNING **: instance of invalid > > > non-instantiatable type `-g-type-private--GTypeFlags' > > > > it's not immediately obvious to us. Could you be more specific in what > > you're > > doing? Given that it's a network application it's also possible that > > something > > a collaborator sends is upsetting it. > > Yes, it is quite difficult to replicate. First off, I can't seem to get > a backtrace with gdb, even with the libinfinoty-gdb package. > > Second, this is while editing a fairly large file (32K) amongst a large > number of people (~20). There were also around 10 other documents in the > session. > > Finally, this is using the backport in squeeze, not sure I got the > version right here. I tried to build a backport of 0.5.2, but failed > because of the gtk3 dependency. > > A. > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
