From: Daniel Skarda <0rfelyus@ucw.cz>
To: alto_stan@wanadoo.be
Cc: Neil Jerram <neil@ossau.uklinux.net>,
guile-gtk@sources.redhat.com, guile-user@gnu.org
Subject: Re: general debugging question + Segfault in guile-gtk
Date: Thu, 28 Nov 2002 14:37:00 -0000 [thread overview]
Message-ID: <m01y55nx0s.fsf@hobitin.ucw.cz> (raw)
In-Reply-To: <20021128184234.5c3bc15b.alto_stan@wanadoo.be> (Stan Pinte's message of "Thu, 28 Nov 2002 18:42:34 +0100")
Stan Pinte <alto_stan@wanadoo.be> writes:
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 1024 (LWP 1112)]
> 0x4039c174 in sgtk_arg_cleanup (a=0xbfffe64c, obj=0x2174) at guile-gtk.c:2026
> 2026 if (BOXED_INFO (obj)->cleanup)
> (gdb) bt
> #0 0x4039c174 in sgtk_arg_cleanup (a=0xbfffe64c, obj=0x2174) at guile-gtk.c:2026
Oops, thats my code, fresh new code.... Mea culpa.
Aha! 0x2174 is #f (SCM_BOOL_F) (no, I am not a wizard, I am using gdb.... :-)
GuileGtk converts callbacks parameters to scheme types (according to
information from Gtk). Than it tries to clean-up data - and I forgot that
structures can also be converted to #f (which is not a boxed type).
if (BOXED_INFO (obj)->cleanup)
should be replaced by
if (BOXED_P (obj) && BOXED_INFO(obj)->cleanup)
Hope that this stops your problems. I am going to commit the fix to CVS ASAP.
Thank you for bug report,
0.
next prev parent reply other threads:[~2002-11-28 22:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-21 0:01 compilation problem in guile-gtk CVS Stan Pinte
2002-11-22 12:44 ` Marius Vollmer
2002-11-28 0:18 ` general debugging question Stan Pinte
2002-11-28 2:32 ` Neil Jerram
2002-11-28 9:23 ` general debugging question + Segfault in guile-gtk Stan Pinte
2002-11-28 14:37 ` Daniel Skarda [this message]
2002-11-28 23:53 ` guile-gtk-1.2 CVS % gtk-pixmap-new Stan Pinte
2002-11-29 11:56 ` Daniel Skarda
2002-12-01 2:48 ` Stan Pinte
2002-11-28 23:53 ` general debugging question + Segfault in guile-gtk Stan Pinte
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m01y55nx0s.fsf@hobitin.ucw.cz \
--to=0rfelyus@ucw.cz \
--cc=alto_stan@wanadoo.be \
--cc=guile-gtk@sources.redhat.com \
--cc=guile-user@gnu.org \
--cc=neil@ossau.uklinux.net \
/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).