[Bug 588938] Conglomerate crashes when pressing backspace or delete

If you have any questions why you received this email, please see the text =
at
the end of this email. Replies to this email are NOT read, please see the t=
ext
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=3D588938

  conglomerate | general | Ver: 0.9.0




------- Comment #3 from Tom Parker  2009-07-20 19:52 UTC -------
(In reply to comment #2)
> Here is a backtrace from running conglomerate from within gdb.
> The version of conglomerate I have does not have debug symbols available
> (stripped).

We're going to need the debug symbols in order to be able to find out what =
went
wrong. https://wiki.ubuntu.com/DebuggingProgramCrash has detailed instructi=
ons
on how to install debugging symbols for packages on Ubuntu systems.

> #6  0xb72b6126 in IA__g_free (mem=3D0x400) at
> /build/buildd/glib2.0-2.20.1/glib/gmem.c:190
> #7  0x080ab11f in ?? ()
> #8  0x08081eaf in ?? ()
> #9  0xb7a31526 in _gtk_marshal_BOOLEAN__BOXED (closure=3D0x9f2ad18,
> return_value=3D0xbff6a4c0, n_param_values=3D2, =

>     param_values=3D0xa1e3518, invocation_hint=3D0xbff6a4ac, marshal_data=
=3D0x9b510a0)
>     at /build/buildd/gtk+2.0-2.16.1/gtk/gtkmarshalers.c:84

See that bit with the two lines ending in "?? ()"? That's probably what's
causing the crash, but there's basically *zero* information there right now
without the debug symbols, and so we've got no idea what happened. Also, if=
 you
can get the output from "backtrace full", as opposed to just "backtrace", t=
hat
would be very useful. Thanks for your time.


-- =

See http://bugzilla.gnome.org/page.cgi?id=3Demail.html for more info about =
why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?=
id=3D588938.