> Please could you get a backtrace to see where this happens? You will
> have to build gitg from source and run the binary and make sure you
> have the GLib dbg package installed, then simply run gitg in gdb and
> ask for a backtrace when it aborts.
OK, it took a while for it to happen again. I've
Please don't forget to CC the bug (584...@bdo) when replying to my
emails.
On Tue, Jun 08, 07:32:17 -0400, Eric Cooper wrote:
> I have it running under gdb now and will let you know what I find.
Great, thanks!
--
Jonny Lamb, UK
jo...@debian.org
--
To UNSUBSCRIBE, email to debian-bugs-dist-r
On Mon, Jun 07, 21:14:30 -0400, Eric Cooper wrote:
> Do you know if there is a simple way to build the debugging version
> with pbuilder? I prefer to use that so I don't need all the -dev and -dbg
> packages installed in my main system.
I guess if you remove the call to dh_strip in debian/rules a
On Mon, Jun 07, 15:13:43 -0400, Eric Cooper wrote:
> I got this crash:
>
> ***MEMORY-ERROR***: gitg[9783]: GSlice: assertion failed:
> sinfo->n_allocated > 0
> [1]+ Aborted gitg
>
> I had been using a gitg window with "view all branches", and had
> recently typed control
Package: gitg
Version: 0.0.6-3
Severity: normal
I got this crash:
***MEMORY-ERROR***: gitg[9783]: GSlice: assertion failed:
sinfo->n_allocated > 0
[1]+ Aborted gitg
I had been using a gitg window with "view all branches", and had
recently typed control-R to refresh the
5 matches
Mail list logo
