Re: for those who care about GNOME^w glib applications.

2006-03-23 Thread Gustavo Franco
On 3/22/06, Steve Langasek <[EMAIL PROTECTED]> wrote: > On Wed, Mar 22, 2006 at 11:29:01AM -0300, Gustavo Franco wrote: > > > > There's a workaround that is run the application as follows: > > > > $ G_SLICE=always-malloc application > > > > Thanks for the information. Can you explain (or provide a

Re: for those who care about GNOME^w glib applications.

2006-03-22 Thread Steve Langasek
On Wed, Mar 22, 2006 at 11:29:01AM -0300, Gustavo Franco wrote: > > > There's a workaround that is run the application as follows: > > > $ G_SLICE=always-malloc application > > Thanks for the information. Can you explain (or provide a pointer to) why > > these bugs are application bugs rather tha

Re: for those who care about GNOME^w glib applications.

2006-03-22 Thread Gustavo Franco
On 3/22/06, Gabor Gombas <[EMAIL PROTECTED]> wrote: > On Wed, Mar 22, 2006 at 11:29:01AM -0300, Gustavo Franco wrote: > > > FYI, GMemChunk (old and deprecated by the upstream) was reimplemented to > > use GSlice, so no need to change or rebuild code to be affected due to buggy > > code. I don't kno

Re: for those who care about GNOME^w glib applications.

2006-03-22 Thread Gabor Gombas
On Wed, Mar 22, 2006 at 11:29:01AM -0300, Gustavo Franco wrote: > FYI, GMemChunk (old and deprecated by the upstream) was reimplemented to > use GSlice, so no need to change or rebuild code to be affected due to buggy > code. I don't know exactly why asking GSlice to force allocate and free memory

Re: for those who care about GNOME^w glib applications.

2006-03-22 Thread Gustavo Franco
On 3/22/06, Steve Langasek <[EMAIL PROTECTED]> wrote: > Hi Gustavo, > > On Tue, Mar 21, 2006 at 11:42:49AM -0300, Gustavo Franco wrote: > > Well, if you're running your favourite glib application and it seems > > to be broken with the output like: > > (...) > > *** glibc detected *** free(): invali

Re: for those who care about GNOME^w glib applications.

2006-03-21 Thread Steve Langasek
Hi Gustavo, On Tue, Mar 21, 2006 at 11:42:49AM -0300, Gustavo Franco wrote: > Well, if you're running your favourite glib application and it seems > to be broken with the output like: > (...) > *** glibc detected *** free(): invalid pointer: 0x08ced388 *** > It's probably due to the new glib (GSl

Re: for those who care about GNOME^w glib applications.

2006-03-21 Thread Gustavo Franco
On 3/21/06, David Pashley <[EMAIL PROTECTED]> wrote: > On Mar 21, 2006 at 14:42, Gustavo Franco praised the llamas by saying: > > Well, if you're running your favourite glib application and it seems > > to be broken with the output like: > > (...) > > *** glibc detected *** free(): invalid pointer:

for those who care about GNOME^w glib applications.

2006-03-21 Thread Gustavo Franco
Well, if you're running your favourite glib application and it seems to be broken with the output like: (...) *** glibc detected *** free(): invalid pointer: 0x08ced388 *** It's probably due to the new glib (GSlice) memory allocator[0], but it's an application bug. Please first check if it's reall