After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 670507 - gobject-introspection: g_log_set_handler is not available.
gobject-introspection: g_log_set_handler is not available.
Status: RESOLVED OBSOLETE
Product: gobject-introspection
Classification: Platform
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gobject-introspection Maintainer(s)
gobject-introspection Maintainer(s)
Depends on: 647883
Blocks:
 
 
Reported: 2012-02-21 06:31 UTC by Takao Fujiwara
Modified: 2018-02-08 12:13 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Patch for gir/glib-2.0.c (1003 bytes, patch)
2012-02-21 06:33 UTC, Takao Fujiwara 		rejected Details | Review

Description Takao Fujiwara 2012-02-21 06:31:23 UTC 
Currently g_log_set_handler is not available from GLib-2.0.typelib.
I'm attaching the patch.
Comment 1 Takao Fujiwara 2012-02-21 06:33:59 UTC 
Created attachment 208089 [details] [review]
Patch for gir/glib-2.0.c

Attached the patch to fix the gir annotation.
Comment 2 Emmanuele Bassi (:ebassi) 2012-02-21 08:54:56 UTC 
Review of attachment 208089 [details] [review]:

the scope is not really async, here: the user_data will be leaked, since there's no actual way to remove or unset a log handler. using async is incorrect, and may lead to bugs in the language bindings.

this kind of closures do not have a scope tag yet; see bug 556489.
Comment 3 Emmanuele Bassi (:ebassi) 2012-02-21 09:06:04 UTC 
Review of attachment 208089 [details] [review]:

the scope is not really async, here: the user_data will be leaked, since there's no actual way to remove or unset a log handler. using async is incorrect, and may lead to bugs in the language bindings.

this kind of closures do not have a scope tag yet; see bug 556489.
Comment 4 Johan (not receiving bugmail) Dahlin 2012-04-06 13:20:55 UTC 
It will always leak, but it might make sense to add a (scope forever) or so which would have almost the same behavior as async.
Comment 5 Tony Houghton 2012-12-02 21:00:47 UTC 
Bug 556489 has been closed and there is a binding for g_log_remove_handler, so can this be fixed now?

What I want to do is get a python stack traceback when something internal to glib/gobject causes assertion warnings. Will that work or would the traceback not be able to traverse the python/C interface?
Comment 6 Takao Fujiwara 2012-12-16 09:17:20 UTC 
Since g_log_remove_handler does not have a destroy argument, this problem can not be fixed until glib releases a new function?
I guess the scope is notified.
Comment 7 André Klapper 2015-02-07 17:18:45 UTC 
[Mass-moving gobject-introspection tickets to its own Bugzilla product - see bug 708029. Mass-filter your bugmail for this message: introspection20150207 ]
Comment 8 GNOME Infrastructure Team 2018-02-08 12:13:59 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gobject-introspection/issues/64.