From: Andy Wingo <wingo@pobox.com>
To: David Pirotte <david@altosw.be>
Cc: guile-devel@gnu.org
Subject: Re: guile-gnome-0 - guile-1.6-latest - corrupted double-linked
Date: Wed, 14 Apr 2010 20:55:58 +0200 [thread overview]
Message-ID: <m3633tkgn5.fsf@pobox.com> (raw)
In-Reply-To: <20100413110943.313e3d2c@rascar> (David Pirotte's message of "Tue, 13 Apr 2010 11:09:43 -0300")
On Tue 13 Apr 2010 16:09, David Pirotte <david@altosw.be> writes:
> Le Thu, 08 Apr 2010 20:53:17 +0200,
> Andy Wingo <wingo@pobox.com> a écrit :
>
>> Hi David,
>
>> > But I have had another type of bug, which I beleive is not related to the one
>> > you looked at, which rarely appears and occurred today, so here it is:
>> >
>> > *** glibc detected *** guile: corrupted double-linked list:
>> > 0x08a1ca60 ***
>>
>> I couldn't tell from your backtraces what went on. Be sure to install
>> the debug packages so that gdb can give symbols.
>
> Done!
>
> Is this any better? [I have no more 'no debugging symbols found' messages
> in gdb, but still have '??' at the end of the trace]
Unfortunately I don't see the problem. All of the bt is in GTK+ code.
But surely it was a case that we freed something that was supposed to be
freed in some other way (the g_slice thing again).
Try valgrind perhaps?
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2010-04-14 18:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100317170918.0a21c8be@rascar>
[not found] ` <m3bpegw0y9.fsf@pobox.com>
2010-04-08 18:06 ` guile-gnome-0 - guile-1.6.8-6.3 - random crash David Pirotte
2010-04-08 18:53 ` Andy Wingo
2010-04-08 20:06 ` Thien-Thi Nguyen
2010-04-08 22:13 ` Andy Wingo
2010-04-09 7:08 ` Thien-Thi Nguyen
2010-04-09 8:40 ` Andy Wingo
2010-04-10 14:23 ` David Pirotte
2010-04-11 20:24 ` Andy Wingo
2010-04-10 14:36 ` David Pirotte
2010-04-13 14:09 ` guile-gnome-0 - guile-1.6-latest - corrupted double-linked David Pirotte
2010-04-14 18:55 ` Andy Wingo [this message]
2010-04-15 19:46 ` David Pirotte
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3633tkgn5.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=david@altosw.be \
--cc=guile-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).