From: Daniel Skarda <0rfelyus@ucw.cz>
To: alto_stan@wanadoo.be
Cc: guile-user <guile-user@gnu.org>,
guile-gtk <guile-gtk@sources.redhat.com>
Subject: Re: guile-gtk: problem in "insert-text" signal handling.
Date: Sun, 16 Mar 2003 09:06:00 -0000 [thread overview]
Message-ID: <m0y93fd85f.fsf@hobitin.ucw.cz> (raw)
In-Reply-To: <20030214163538.12f31385.alto_stan@wanadoo.be> (Stan Pinte's message of "Fri, 14 Feb 2003 16:35:38 +0100")
Hello,
> with the following program, I am getting garbage from the "new-text" variable,
> when introducing the second and following characters...
>
> Is this a bug in guile-gtk-1.2-0.31, or am I only supposed to use the first
> charachter of the string?
I think you found a (design) bug in Gtk+ - string received by signal handler
is not terminated by '\000', the length of the string is passed as an additional
argument. Unfortunately, any other signal does not use "STRING, LENGTH" pattern
for passing string parameters. The bug is also potential source of SIGSEGV (when
no random '\000' is found, which is quite unlikely - but hey, all hideous bugs
have unlikely conditions.... )
Another sad part of the story: sgtk_callback_marshall does not now the signal
name, so all we can do now on guile-gtk part is an ugly hack:
if (n_args == 3 && GTK_FUNDAMENTAL_TYPE (args[0]) == GTK_TYPE_STRING) && ...)
/* let's hope we handle "new-text" signal.... */
Please report the bug to Gtk+ folks.
Have a nice day,
0.
next prev parent reply other threads:[~2003-03-16 9:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-14 15:06 Stan Pinte
2003-03-16 9:06 ` Daniel Skarda [this message]
2003-03-31 22:50 ` Kevin Ryde
2003-04-02 0:05 Daniel Skarda
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=m0y93fd85f.fsf@hobitin.ucw.cz \
--to=0rfelyus@ucw.cz \
--cc=alto_stan@wanadoo.be \
--cc=guile-gtk@sources.redhat.com \
--cc=guile-user@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).